...

Goals:

Improve operability in the Hydrator Studio (Improvements to logs, metrics, debuggability)
Improve usability in the Hydrator Studio (Redesign of bottom panel, etc)

Checklist

User stories documented (Bhooshan)
User stories reviewed (Nitin/Jon)
Design documented (Bhooshan/Brady)
Design reviewed (Nitin/Jon)
Implementation review (Bhooshan)

Use Cases:

Use Case 1: Improve Log Viewer

Problems with current Log Viewer:

...

Timeline:
1. Starts at the program/service start time. Ends at the program/service end time (past) or current.
2. Time range indicated by two sliders on each side. Time range can be selected by sliding these sliders.
3. Updating slider position causes a refresh of the log viewer to show logs in the selected range with the selected filters
4. If program/service is still running, the right/bottom end of the slider indicates current time, and if the slider is at this position, logs are updated live. The timeline keeps updating to reflect that.
5. Sliders must not cross each other
6. Label on the selected time range indicates the selected time range
7. The timeline is marked with time range with granularity that depends on the duration of the log (which is the duration of the program run).
8. In the selected (or default time range), there should be symbols on the time line for the errors and warnings, as well as for events that match the filter in the search box. Clicking on such a symbol should navigate you to the corresponding event in the table. The graph may look like so:
Filters:
1. Filter by lowest log level:
  1. If ERROR is selected, then we show only ERROR
  2. If WARN is selected, then we show ERROR and WARN
  3. If INFO is selected, then we show ERROR, WARN and INFO
  4. If DEBUG is selected, then we show ERROR, WARN, INFO and DEBUG
  5. If TRACE is selected, then we show ERROR, WARN, INFO, DEBUG and TRACE
2. Filter by search keywords:
  1. Search box that filters logs by the search text.
  2. This is a simple filter that applies on the message column
Log viewer Table:
1. Columns:
  1. Timestamp
  2. Lowest Log Level
  3. Source - Only in CDAP - This column should not be shown in Hydrator
  4. Message (also contains stack trace).
2. Default view shows single line messages, with / buttons to expand individual messages if they have more content
3. Ability to suppress/show stack trace with a similar / buttons.
4. Ability to expand all messages
5. Ability to only view the message column
Top Bar:
1. Shows information/summary of the log
2. Indicates program/service name
3. Summary of total messages with number of warnings and errors
4. Download button to download entire log
5. Search box for filtering.

Required Backend support:

Jira Legacy

server	Cask Community Issue Tracker
serverId	45b48dee-c8d6-34f0-9990-e6367dc2fe4b
key	CDAP-5893

Use Case 2: Bottom Panel

Problems with bottom panel:

...

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 do not want to switch back-and-forth between the DAG and the bottom panel repeatedly for building my pipeline
- I should be able to provide node-level details right near the node
- I should be able to simultaneously view details for multiple nodes both while editing a pipeline as well as viewing it.
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 to reduce 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
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 actions for source/sink in Hydrator:
  - View in Dataset Details page in CDAP
  - View in entity details page in Tracker
  - Explore Dataset (if possible) in CDAP

...

Make DAG the hero
Not have widgets that occupy real-estate but only show messages like "No XXX for this XXX"
Not occupy real-estate statically with capabilities that are add-ons but not requirements for creating pipelines
Support incremental pipeline development:

Basics first: Configure nodes and get the pipeline working
Add-ons later: Adding a schedule, adding post-run actions, etc

Clearly demarcate Studio/Detail page into two sections:

Canvas: Has the DAG, and capabilities to modify/view/update/reference node level information
Pipeline section: Configure/update/view pipeline level information
Canvas occupies majority real-estate by default. If you want to view/modify pipeline details, that reduces canvas size

For pipeline section, there are two views for most capabilities:

Compact view: Shows the selected pipeline capability (logs, metrics, pipeline configuration) in a smaller drawer, but also shows the canvas (and the DAG).
Full-screen view: Hides the canvas, and only contains the header, footer and the selected capability.
Switching between these two views is supported

Reduce the disparity between the pipeline details view and the studio
- This will help to add the capability to edit a pipeline after publishing

Use Case 3: Debuggability/Testing/Preview

User Stories:

As a Hydrator user, I want to preview my pipeline with a specified set of input records fetched directly from the source for validating my pipeline configuration and behavior before I publish the pipeline.
(Advanced) As a Hydrator user, I want to be able to save snapshots of data previously fetched during preview, and use them later, so I don't have to connect to the source every time I want to preview my pipeline.
As a Hydrator user, I want to test individual plugins in my pipeline by sending in sample input records and viewing the resultant output.
(Advanced) As a Hydrator user, I want to be able to smoke test my pipeline from the UI

Provided with a golden set of input and output, the pipeline should be able to validate itself

(Advanced) As a Hydrator user, I want to be able to smoke test a single plugin from the UI

Provided with a golden set of input and output, the plugin should be able to validate itself

(Advanced) As a Hydrator user, I want to be able to store smoke test data for later use
As a Hydrator user, I want to be able to validate my pipeline more effectively
- If clicking on a 'Validate' button returns successful, then publishing the pipeline should not fail.

Design:

Use Case 4: Complex schema management

User Stories:

As a Hydrator user, I want to be able to set complex schemas for my pipeline
- I would like to have fields with enum, array, map, record and union types and would like an efficient method to create/manage them from the UI
As a Hydrator user, I would like to be able to view complex schemas for my pipeline

Design:

Design Principles:

No static real-estate allocation. Users can add rows with a button.
Breadcrumbs as a primary means of creating/viewing complex schemas.

Design

Use a combination of dedicated screens with breadcrumbs for complex types
Main screen should show the top level data type: Use tabs with customized expansions for complex fields.
Simple types string, int, long, float, double, boolean, bytes , enum, array, map, record and union
Simple types string, int, long, float, double, boolean, bytes can be defined in the main screen itself, which is represented in breadcrumbs by the name of the stage for which schema is being defined
Enum: When an enum is selected, a sub-screen should accept enum values. Breadcrumb: <field-name> (enum)
Array: When an array is selected, a sub-screen should accept a data type (which in can be defined as today
Enum: When an enum is selected, the field name becomes clickable. Expansion allows you to enter enum values.
Array: When an array is selected, the field name becomes clickable. Expansion accepts a data type (which in turn could be a complex type as well, in which case the same flow rules defined here would apply, and breadcrumbs would be updated). Breadcrumb: <field-name> (array)).
Map: When a map is selected, a sub-screen should accept a key-the field name becomes clickable. Expansion accepts a key type and a value -type (which in turn could be complex types as well, in which case the same flow rules defined here would apply for each, and breadcrumbs would be updated). Breadcrumb: <field-name> (map).
- Simple types for map key and value can be configured on the same map subscreen.
- Breadcrumb for complex map key: key (<selected complex type>)
- Breadcrumb for complex map key: value (<selected complex type>)
Record: When a record is selected, a sub-screen identical to the main screen shows up which accepts a nested record. Breadcrumb: <field-name> (record).
Union: When a union is selected, a sub-screen should accept the two schemas whose union is needed. Breadcrumb: <field-name> (record)
- Simple types for both schema1 and schema2 can be selected on the same subscreen
- Complex types for schema1 takes you to a sub-screen identical to the record sub-screen. Breadcrumb: schema1 (<selected complex type>)
- Complex types for schema2 takes you to a sub-screen identical to the record sub-screen. Breadcrumb: schema2 (<selected complex type>)
For viewing, main screen only shows first level (string, int, long, float, double, boolean, bytes, enum, array, map, record and union) data types. Complex types are clickable, and take you to view-only views described above with breadcrumbs for navigation.type.
Record: When a record is selected, the field name becomes clickable. Expansion allows you to specify a nested record
Union: When a union is selected, the field name becomes clickable. On clicking, you can add schemas. Each schema is of type record.
For viewing, main screen only shows first level (string, int, long, float, double, boolean, bytes, enum, array, map, record and union) data types. For complex types, field names are clickable, and expand to read-only views of the expansions described above.

Use Case 5: Pipelines Listing or Pipelines Dashboard

User Stories:

As a Hydrator operations team member, I would like to view all the pipelines running across multiple namespaces that I am authorized for
- Would also like to be view only the pipelines that I have access for.
As a Hydrator operations team member, I would like to see following fields for each pipeline
- Pipeline Fields
  - Namespace
  - Pipeline Name
  - Status (RUNNING | SUCESS | FAILED)
  - Number of Active Runs
  - Total Number of Runs
  - Last Start Time
  - Last Run Finish Time
  - User
As a Hydrator operations team member, I should be able to filter on above specified fields to get to the pipeline status
As a Hydrator operations team member, I should be able to filter all the pipelines (including pipelines across namespace) based on Start date, End date and Status
As a Hydrator operations team member, I should be able to filter on a specified field and continue to filter the results using other fields. (nested filtering)

Use Case 6: System Mode

User Stories:

As a Hydrator user, I want to know if I'm working in distributed or stand-alone mode at all times.
As a Hydrator user, I want to know if I'm working in secure or secure mode at all times.

Design:

Use Case 7: Join Node

Jira Legacy

server	Cask Community Issue Tracker
serverId	45b48dee-c8d6-34f0-9990-e6367dc2fe4b
key	CDAP-6371

Use Case 8: Run Configuration

Jira Legacy

server	Cask Community Issue Tracker
serverId	45b48dee-c8d6-34f0-9990-e6367dc2fe4b
key	CDAP-6370

Scratch Pad:

Work Streams:

Tech Debt

Simplify Config Store
Simplify DAG component ~ Ajai's hack

...

Versions Compared

Old Version 41

New Version Current

Key

Table of Contents

Goals:

Checklist

Use Cases:

Use Case 1: Improve Log Viewer

Use Case 2: Bottom Panel

Use Case 3: Debuggability/Testing/Preview

Use Case 4: Complex schema management

Use Case 5: Pipelines Listing or Pipelines Dashboard

Use Case 6: System Mode

Use Case 7: Join Node

Use Case 8: Run Configuration

Scratch Pad:

Work Streams:

Page Comparison

Versions Compared

Old Version 41

New Version Current

Key

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-0">[data-colorid=</span>

Goals:

Checklist

Use Cases:

Use Case 1: Improve Log Viewer

Use Case 2: Bottom Panel

Use Case 3: Debuggability/Testing/Preview

Use Case 4: Complex schema management

Use Case 5: Pipelines Listing or Pipelines Dashboard

Use Case 6: System Mode

Use Case 7: Join Node

Use Case 8: Run Configuration

Scratch Pad:

Work Streams: