...
- As a Hydrator Product Team, I want to better plan the Hydrator real-estate so it is not statically allocated for configurations/views that are not commonly used/mandatory to be updated for creating pipelines
- e.g. Pipeline configurations like post run actions, engine, schedule
- As a Hydrator Product Team, I want to better design the Hydrator UI to lay more emphasis on the DAG
- As a Hydrator user, I want to be able to build my pipeline incrementally. I want mandatory information to be more obvious.
- Build the pipeline with mandatory fields only to start off
- Incrementally add schedule, post run actions, etc
- As a Hydrator Product Team, I want remove the disparity between the pipeline detail view and the studio view. This will facilitate the move towards being able to edit a pipeline after publishing
- e.g. Reference is unavailable in the pipeline details view
- e.g. Reference is unavailable in the pipeline details view
- As a Hydrator user, I want the messaging regarding multiple runs from the Hydrator UI to be clearer.
- Does Hydrator only always show the last run?
- If so, what is the "History" view for
- As a Hydrator Product Team, I want to reduce duplication
- The console is not very useful today, it just shows messages. Can it be reconciled with the notification center?
- As a Hydrator user, I want related actions to appear together.
- e.g. "Export" is available in the bottom panel, but other pipeline controls are in the top bar.
- As a Hydrator Product team, I want to bring Jump buttons to Hydrator to make them the primary method of viewing entities in different contexts across CDAP, Hydrator and Tracker
- Jump from pipeline details view in Hydrator to program details view in CDAP
- Jump from source/sink in Hydrator to entity page in Tracker
Use Case 2: Debuggability/Testing
...