apache / apache/hop

[Bug]: Duplication of Run Configurations

Open
#4,248 2 comments 0 reactions 0 assignees View on GitHub
awaiting triage Hop Gui P3
Dominant language
Java
Stars
1.5k
Forks
476
Avg merge
18h 32m
Merged PRs (30d)
216

Description

### Apache Hop version?

2.9.0

### Java version?

openjdk 21.0.2 2024-01-16

### Operating system

Linux

### What happened?

If you create a new Pipeline or Workflow Run Configuration via the "Duplicate" command in Hop GUI (Metadata perspective), the associated JSON is created in the same folder the original one resides.

When creating a new Run Configuration (RC) from scratch, instead, the file is saved in the metadata folder related to the active project. This should be a better choice even for duplicates, since you probably don't want a new RC to be available to various projects (*all* projects, if the original RC belongs to the "default" project).

A workaround consists in moving (manually via OS) the JSON file associated to the new RC to the designed folder. The new RC would be still available on inherited projects, too.

### Issue Priority

Priority: 3

### Issue Component

Component: Hop Gui

Contributor guide

Open the contributing guide

Research direction

Start in the Hop GUI Metadata perspective and trace the Duplicate command for Pipeline and Workflow Run Configurations, comparing it with creating a Run Configuration from scratch. Verify that duplication saves the JSON in the active project's metadata folder and that the new configuration is not unintentionally shared across projects.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.