You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Parav Patel (Jira)" <ji...@apache.org> on 2021/11/02 07:33:00 UTC
[jira] [Updated] (NIFI-9359) Improve Usability of NiFi Data
Provenance Grid
[ https://issues.apache.org/jira/browse/NIFI-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parav Patel updated NIFI-9359:
------------------------------
Description:
*As per the discussion which came up in Pierre Villard's - Apache NiFi Monitoring Stream*
Improve Usability of NiFi Data Provenance Grid
# Indexed attributes (i.e. nifi.provenance.repository.indexed.attributes) should be in the provenance grid and configurable so user can select which indexed attributes to display on the grid and also which ones to omit (if needed).
# Allow filtering of values directly from the grid UI. Slack Grid provides a header row to achieve this which can be incorporated in existing NiFi Provenance Grid. See: [https://mleibman.github.io/SlickGrid/examples/example-header-row.html]
# Shortcuts to view both the Flow File Content (Input and Output Claim) directly from grid. Columns with a provided icon can save a few clicks when viewing flow file content.
# Give button/shortcut to auto resize column and reshuffle column order. It may be possible to accomplish this by leveraging the idenxed.attributes to reshuffle column order.
*Reference Discussion Stream:*
Pierre Villard - Apache NiFi Monitoring Stream (Starting @1:59:10):
[https://youtu.be/QqFgWh3xhuQ]
was:
*As per the discussion which came up in Pierre Villard's - Apache NiFi Monitoring Stream*
Improve Usability of NiFi Data Provenance Grid
# Indexed attributes (i.e. nifi.provenance.repository.indexed.attributes) should be in the provenance grid and configurable so user can select which indexed attributes to display on the grid and also which ones to omit (if needed).
# Allow filtering of values directly from the grid UI. Slack Grid provides a header row to achieve this which can be incorporated in existing NiFi Provenance Grid. See: [https://mleibman.github.io/SlickGrid/examples/example-header-row.html]
# Shortcuts to view both the Flow File Content (Input and Output Claim) directly from grid. Columns with a provided icon can save a few clicks when viewing flow file content.
# Give button/shortcut to auto resize column and reshuffle column order. It may be possible to accomplish this by leveraging the idenxed.attributes to reshuffle column order.
*Reference Discussion Stream:*
Pierre Villard - Apache NiFi Monitoring Stream (Starting @1:59:10):
[https://youtu.be/QqFgWh3xhuQ]
> Improve Usability of NiFi Data Provenance Grid
> ----------------------------------------------
>
> Key: NIFI-9359
> URL: https://issues.apache.org/jira/browse/NIFI-9359
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Parav Patel
> Priority: Major
> Attachments: NiFi Provenance Data Page 1.png
>
>
> *As per the discussion which came up in Pierre Villard's - Apache NiFi Monitoring Stream*
>
> Improve Usability of NiFi Data Provenance Grid
> # Indexed attributes (i.e. nifi.provenance.repository.indexed.attributes) should be in the provenance grid and configurable so user can select which indexed attributes to display on the grid and also which ones to omit (if needed).
> # Allow filtering of values directly from the grid UI. Slack Grid provides a header row to achieve this which can be incorporated in existing NiFi Provenance Grid. See: [https://mleibman.github.io/SlickGrid/examples/example-header-row.html]
> # Shortcuts to view both the Flow File Content (Input and Output Claim) directly from grid. Columns with a provided icon can save a few clicks when viewing flow file content.
> # Give button/shortcut to auto resize column and reshuffle column order. It may be possible to accomplish this by leveraging the idenxed.attributes to reshuffle column order.
>
> *Reference Discussion Stream:*
> Pierre Villard - Apache NiFi Monitoring Stream (Starting @1:59:10):
> [https://youtu.be/QqFgWh3xhuQ]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)