Page Comparison

...

Doesn't cater to usual developer interactions with logs - tail'ing (with log file monitoring -f) or less'ing (viewing the log) or downloading
Hard to distinguish between two log lines
Exception stack traces are virtually un-readable
Virtually no formatting in the UI - almost rendered as the logs appear from the backend, which is not ideal to an end-user
No search (even at the UI level)
Jira Legacy
server Cask Community Issue Tracker
serverId 45b48dee-c8d6-34f0-9990-e6367dc2fe4b
key CDAP-5733

Possible solutions

Tabular view: Columns for date, Class Name/Thread Name, Log Level, Log Line
Alternate row background colors
Vertically expandable with scrolling
Searchable (Filter-able) columns
Clear demarcation of rows
Horizontally scrollable rows
Snippet with expand - especially for stack traces
Picking only 1 or more log level -INFO, DEBUG, WARN, ERROR, ALL
Ability to view and download raw logs if required
Ability to view and expand only the "content" column of a log line
Time range picker
Ability to show the hostname where the logfile came from (Probably only makes sense if we ever show logs for services that run on fixed hosts, not for programs that run in YARN containers).
Ability to show the path to the log file on the host (Probably only makes sense if we ever show logs for services that run on fixed hosts, not for programs that run in YARN containers).

Use Case 2: Bottom Panel

Problems with current Bottom Panel

Constant back-and forth between DAG and bottom panel - click on a node, then view the bottom panel - not very intuitive
Reserved real-estate for configurations that are not commonly updated
Schema available in both bottom panel as well as the DAG
Reduced "prominance" for both the DAG as well as the bottom panel, since you're not using the full available space ever
Restricted space in the bottom panel for logs, pipeline configuration, node configuration, etc
Association between a DAG and its bottom panel is not always clear enough

...

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

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.

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
As a Hydrator user, I want the messaging regarding multiple runs from the Hydrator UI to be clearer.

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 actions for source/sink in Hydrator to entity :
  - View in Dataset Details page in CDAP
  - View in entity details page in Tracker
  - Explore Dataset (if possible) in CDAP

Use Case 2: Debuggability/Testing

...