[jira] [Assigned] (NIFI-4704) get a view of the process as a list of directories
[ https://issues.apache.org/jira/browse/NIFI-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri reassigned NIFI-4704: -- Assignee: Yuri > get a view of the process as a list of directories > -- > > Key: NIFI-4704 > URL: https://issues.apache.org/jira/browse/NIFI-4704 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Alexandre Côté >Assignee: Yuri >Priority: Minor > > Hello, > It's very long to move around all our componend of Nifi (nvagiation in the > group). > It could be very usefull to get something like a directory view as we can get > one in eclipse for exemple. > We can imagine in the next step to have some information about the process in > that view (state, error, number of flow, ...), and start and stop the process > directly in the view for exemple. > Thank's, > Alex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-3711) Change default size of provenance details dialog to show Replay button by default
[
https://issues.apache.org/jira/browse/NIFI-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342722#comment-16342722
]
Yuri commented on NIFI-3711:
[~sivaprasanna] Simply moving the replay button to make it permanently visible
is easy. However, it seems a bit misplaced, isn't it? [^Screenshot from
2018-01-28 21-14-07.png]
> Change default size of provenance details dialog to show Replay button by
> default
> -
>
> Key: NIFI-3711
> URL: https://issues.apache.org/jira/browse/NIFI-3711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Priority: Minor
> Labels: beginner, dialog, provenance, replay, ui
> Attachments: Screen Shot 2017-04-18 at 11.19.12 AM.png, Screen Shot
> 2017-04-18 at 11.19.46 AM.png, Screenshot from 2017-09-10 20-56-41.png,
> Screenshot from 2018-01-28 21-14-07.png
>
>
> The provenance details dialog is sized such that the "Replay" button on the
> "Content" tab is not visible by default and there is no visible scroll bar
> indicating that the panel has additional content. Some users have reported
> being unaware of the replay feature because of this. I propose changing the
> default dialog size to ensure the panel is fully displayed ({{min-height}}?).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-3711) Change default size of provenance details dialog to show Replay button by default
[
https://issues.apache.org/jira/browse/NIFI-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuri updated NIFI-3711:
---
Attachment: Screenshot from 2018-01-28 21-14-07.png
> Change default size of provenance details dialog to show Replay button by
> default
> -
>
> Key: NIFI-3711
> URL: https://issues.apache.org/jira/browse/NIFI-3711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Priority: Minor
> Labels: beginner, dialog, provenance, replay, ui
> Attachments: Screen Shot 2017-04-18 at 11.19.12 AM.png, Screen Shot
> 2017-04-18 at 11.19.46 AM.png, Screenshot from 2017-09-10 20-56-41.png,
> Screenshot from 2018-01-28 21-14-07.png
>
>
> The provenance details dialog is sized such that the "Replay" button on the
> "Content" tab is not visible by default and there is no visible scroll bar
> indicating that the panel has additional content. Some users have reported
> being unaware of the replay feature because of this. I propose changing the
> default dialog size to ensure the panel is fully displayed ({{min-height}}?).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-4400) Advanced UI with code editor for scripted processors
[ https://issues.apache.org/jira/browse/NIFI-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313617#comment-16313617 ] Yuri commented on NIFI-4400: OK, [~joewitt] I'll try to resolve the remaining open points. [~scottyaslan], the current Advanced UI version, based on the nifi-jolt-transform-json-ui, reuses assets (eg. angular.js, nf-storage.js, CodeMirror.js, NiFi stylesheets) from nifi-web-ui. It simply links those resources from the web UI in the main JSP. I guess, all those resources should be somehow separated to the Advanced UI in order to implement the unit test suite and minification properly. Is this correct? > Advanced UI with code editor for scripted processors > > > Key: NIFI-4400 > URL: https://issues.apache.org/jira/browse/NIFI-4400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI, Extensions >Reporter: Pierre Villard >Assignee: Yuri > > For the scripted processors it would nice to add an advanced UI with a "code > editor mode" that would provide some very useful features when typing code: > - indentation > - code highlighting > - do not close the window when hitting enter > etc > The use of codemirror.js (as already done for EL auto-completion) sounds like > a good option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (NIFI-4538) Add Process Group information to Search results
[ https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302579#comment-16302579 ] Yuri edited comment on NIFI-4538 at 12/23/17 8:59 PM: -- The parent and top level PGs' names (or IDs) could be relatively long. It seems they wouldn't fit on query match header line together with the component's name. This design also doesn't look really clean - [^Screenshot from 2017-12-23 21-08-45.png] Moving both PGs below the query match header line seems to be confusing a bit - [^Screenshot from 2017-12-23 21-42-24.png]. Maybe to embolden some parts would help. Does anybody have any ideas on this? was (Author: yuri1969): The parent and top level PGs' names (or IDs) could be relatively long. It seems they wouldn't fit on query match header line together with the component's name. This design also doesn't look really clean - !Screenshot from 2017-12-23 21-08-45.png!. Moving both PGs below the query match header line seems to be confusing a bit - !Screenshot from 2017-12-23 21-42-24.png|thumbnail!. Maybe to embolden some parts would help. Does anybody have any ideas on this? > Add Process Group information to Search results > --- > > Key: NIFI-4538 > URL: https://issues.apache.org/jira/browse/NIFI-4538 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Burgess >Assignee: Yuri > Attachments: Screenshot from 2017-12-23 21-08-45.png, Screenshot from > 2017-12-23 21-42-24.png > > > When querying for components in the Search bar, no Process Group (PG) > information is displayed. When copies of PGs are made on the canvas, the > search results can be hard to navigate, as you may jump into a different PG > than what you're looking for. > I propose adding (conditionally, based on user permissions) the immediate > parent PG name and/or ID, as well as the top-level PG. In this case I mean > top-level being the highest parent PG except root, unless the component's > immediate parent PG is root, in which case it wouldn't need to be displayed > (or could be displayed as the root PG, albeit a duplicate of the immediate). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (NIFI-4538) Add Process Group information to Search results
[ https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302579#comment-16302579 ] Yuri edited comment on NIFI-4538 at 12/23/17 8:58 PM: -- The parent and top level PGs' names (or IDs) could be relatively long. It seems they wouldn't fit on query match header line together with the component's name. This design also doesn't look really clean - !Screenshot from 2017-12-23 21-08-45.png!. Moving both PGs below the query match header line seems to be confusing a bit - !Screenshot from 2017-12-23 21-42-24.png|thumbnail!. Maybe to embolden some parts would help. Does anybody have any ideas on this? was (Author: yuri1969): The parent and top level PGs' names (or IDs) could be relatively long. It seems they wouldn't fit on query match header line together with the component's name. This design also doesn't look really clean - !Screenshot from 2017-12-23 21-08-45.png|thumbnail!. Moving both PGs below the query match header line seems to be confusing a bit - !Screenshot from 2017-12-23 21-42-24.png|thumbnail!. Maybe to embolden some parts would help. Does anybody have any ideas on this? > Add Process Group information to Search results > --- > > Key: NIFI-4538 > URL: https://issues.apache.org/jira/browse/NIFI-4538 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Burgess >Assignee: Yuri > Attachments: Screenshot from 2017-12-23 21-08-45.png, Screenshot from > 2017-12-23 21-42-24.png > > > When querying for components in the Search bar, no Process Group (PG) > information is displayed. When copies of PGs are made on the canvas, the > search results can be hard to navigate, as you may jump into a different PG > than what you're looking for. > I propose adding (conditionally, based on user permissions) the immediate > parent PG name and/or ID, as well as the top-level PG. In this case I mean > top-level being the highest parent PG except root, unless the component's > immediate parent PG is root, in which case it wouldn't need to be displayed > (or could be displayed as the root PG, albeit a duplicate of the immediate). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4538) Add Process Group information to Search results
[ https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16302579#comment-16302579 ] Yuri commented on NIFI-4538: The parent and top level PGs' names (or IDs) could be relatively long. It seems they wouldn't fit on query match header line together with the component's name. This design also doesn't look really clean - !Screenshot from 2017-12-23 21-08-45.png|thumbnail!. Moving both PGs below the query match header line seems to be confusing a bit - !Screenshot from 2017-12-23 21-42-24.png|thumbnail!. Maybe to embolden some parts would help. Does anybody have any ideas on this? > Add Process Group information to Search results > --- > > Key: NIFI-4538 > URL: https://issues.apache.org/jira/browse/NIFI-4538 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Burgess >Assignee: Yuri > Attachments: Screenshot from 2017-12-23 21-08-45.png, Screenshot from > 2017-12-23 21-42-24.png > > > When querying for components in the Search bar, no Process Group (PG) > information is displayed. When copies of PGs are made on the canvas, the > search results can be hard to navigate, as you may jump into a different PG > than what you're looking for. > I propose adding (conditionally, based on user permissions) the immediate > parent PG name and/or ID, as well as the top-level PG. In this case I mean > top-level being the highest parent PG except root, unless the component's > immediate parent PG is root, in which case it wouldn't need to be displayed > (or could be displayed as the root PG, albeit a duplicate of the immediate). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-4538) Add Process Group information to Search results
[ https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri updated NIFI-4538: --- Attachment: Screenshot from 2017-12-23 21-08-45.png Screenshot from 2017-12-23 21-42-24.png > Add Process Group information to Search results > --- > > Key: NIFI-4538 > URL: https://issues.apache.org/jira/browse/NIFI-4538 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Burgess >Assignee: Yuri > Attachments: Screenshot from 2017-12-23 21-08-45.png, Screenshot from > 2017-12-23 21-42-24.png > > > When querying for components in the Search bar, no Process Group (PG) > information is displayed. When copies of PGs are made on the canvas, the > search results can be hard to navigate, as you may jump into a different PG > than what you're looking for. > I propose adding (conditionally, based on user permissions) the immediate > parent PG name and/or ID, as well as the top-level PG. In this case I mean > top-level being the highest parent PG except root, unless the component's > immediate parent PG is root, in which case it wouldn't need to be displayed > (or could be displayed as the root PG, albeit a duplicate of the immediate). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-4538) Add Process Group information to Search results
[ https://issues.apache.org/jira/browse/NIFI-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri reassigned NIFI-4538: -- Assignee: Yuri > Add Process Group information to Search results > --- > > Key: NIFI-4538 > URL: https://issues.apache.org/jira/browse/NIFI-4538 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Burgess >Assignee: Yuri > > When querying for components in the Search bar, no Process Group (PG) > information is displayed. When copies of PGs are made on the canvas, the > search results can be hard to navigate, as you may jump into a different PG > than what you're looking for. > I propose adding (conditionally, based on user permissions) the immediate > parent PG name and/or ID, as well as the top-level PG. In this case I mean > top-level being the highest parent PG except root, unless the component's > immediate parent PG is root, in which case it wouldn't need to be displayed > (or could be displayed as the root PG, albeit a duplicate of the immediate). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4704) get a view of the process as a list of directories
[ https://issues.apache.org/jira/browse/NIFI-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16295648#comment-16295648 ] Yuri commented on NIFI-4704: There seems to be a need for a more hierarchical style of interaction with PGs and/or components within PGs (eg. NIFI-4402 or NIFI-4538). A treeview described here could help. Personally, I don't know whether other components, such as processors, should be included in the tree (acting as leaves). What comes to mind is a correlation to current breadcrumb "level" and maybe also to search results. I mean using different highlights for current "level", etc. > get a view of the process as a list of directories > -- > > Key: NIFI-4704 > URL: https://issues.apache.org/jira/browse/NIFI-4704 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Alexandre Côté >Priority: Minor > > Hello, > It's very long to move around all our componend of Nifi (nvagiation in the > group). > It could be very usefull to get something like a directory view as we can get > one in eclipse for exemple. > We can imagine in the next step to have some information about the process in > that view (state, error, number of flow, ...), and start and stop the process > directly in the view for exemple. > Thank's, > Alex -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4554) Allow multiple element selection when enabling/disabling controller services
[
https://issues.apache.org/jira/browse/NIFI-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254204#comment-16254204
]
Yuri commented on NIFI-4554:
It seems this issue has already been covered by NIFI-4033. [~alopresto] unlink
if it hasn't, please.
> Allow multiple element selection when enabling/disabling controller services
>
>
> Key: NIFI-4554
> URL: https://issues.apache.org/jira/browse/NIFI-4554
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
>Affects Versions: 1.4.0
>Reporter: Andy LoPresto
> Labels: controller_services, ui, ux
>
> When enabling or disabling controller services, because of the hierarchical
> relationship that can exist between them, it is sometimes necessary to
> disable multiple services in order to edit the configuration values of one
> (example: {{RecordReader}}/{{RecordSetWriter}} and {{SchemaRegistry}}). I
> propose enhancing this functionality with some form of multiple row selection
> (checkboxes, clicking in the row & highlighting, etc.) and providing "Enable
> Selected" and "Disable Selected" action buttons.
> I understand there may be some cascading issues, but as each service has a
> reference to its dependents, the ordering should not be too difficult.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (NIFI-4569) Brief summary of a newbie journey into NiFi
[ https://issues.apache.org/jira/browse/NIFI-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248438#comment-16248438 ] Yuri commented on NIFI-4569: Hello Eric, concerning your points under the *Development workflow* section. The [NiFi Registry|https://nifi.apache.org/registry.html] subproject aims to deal with the workflow management. You can check [the current efforts|https://issues.apache.org/jira/projects/NIFIREG]. > Brief summary of a newbie journey into NiFi > --- > > Key: NIFI-4569 > URL: https://issues.apache.org/jira/browse/NIFI-4569 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Docker >Affects Versions: 1.4.0 >Reporter: Eric Chaves >Priority: Minor > > Hi folks, > As requested at Nifi's User mailing list, I'm compiling a small briefing of > my experience as a new user working with NiFi. This report includes some > feedback while I was learning NiFi following some tutorial and articles found > on the internet. > In particular, after scouting the internet and reading NiFi's docs, I first > tried to write some custom flows using scripted processors and scripted > services. > Most of the troubles I've faced I attribute to my lack of expertise with > Java/Groovy plus my small knowledge with NiFi's architecture. I did faced > some inconsistencies however that may be eased for newcomers like me in > future releases. > *Development workflow* > To write my flows I'm using the official docker image (apache/nifi:1.4.0) > together with other images like mysql, mongodb and localstack (to simulate > AWS services). > It took me a while to properly setup a working folder using docker. When I > simple run the container without any volume binded to my local host, NiFi > started properly because all the required files are already present in conf > dir. This setup works fine for trying NiFi out but is not good as development > starting point because changes may be lost due to container rebuilt. > To address this I first attempted to bind volumes for ./conf and ./logs > folder but this didn't worked as expected because this produced and empty > ./conf folder that prevents nifi from starting. To get this right was a > little hard and I only did it after looking at some github's projects to > compare they're ./conf dir with NiFi's default configuration inside the > docker image. > _- *Suggestion #1*: NiFi shoud created default configuration files when no > file is present in ./conf_ > After getting my docker right I started creating some flows following some > Hortonworks tutorials and others website (like Matt's blog) and the first > thing that confused me was the lack of a simple to get a new blank canvas. In > order to do so I need to stop all components, delete processors and groups, > ports and etc. > _- *Suggestion #2*: Add an "new canvas" button to the operations pallete (or > somewhere else)._ > At this point I started writing some flows that I would like to keep under > version control and there is no simple way for that. NiFi's canvas is kept in > a gzip file which is not ideal for version control and the current way of > exporting a canvas requires us to save it as template and then export the > template. This process seems ok when we have finished a flow and want to > export it for future use as an actual template but is not good for small > commits while working in the flow (WIP commits). A better approach would be > to have the flowfile as xml directly under source control. > _- *Suggestion #3*: Enable a configuration mode to kept the current canva as > pure xml instead of GZipped file._ > *Writing Custom Processors* > Not much to be said here. The experience was awesome. The developers guide is > very good and Matt's 3 post 'nifi scripting cookbooks' are priceless. Those > cookbooks should be added to the default documentation. > Two things hit me here: I assumed that all JAR used by NiFi's default > processors were available for use by a script processor (requiring it only to > be imported) but that is not the case and I needed to re-add some JAR's (like > javax.mail or AWS java sdk) to the script's modules folder. That was not > intuitive for me but maybe because I'm not a Java developer. I also had a > trouble with java loading proper handlers for mime types (something related > to javax.mail) that blocked me to use Groovy for a custom script write > multipart mime messages (I ended writing it in python). > - *Suggestion #4*: Make clear which JAR files are available by default inside > a script processor and which are not and how to properly configure the system > class loader. > *Writing Custom Services* > I'm working on a custom flow that needs to enrich some data records. Since I > had successfully wrote some processors
[jira] [Assigned] (NIFI-4400) Advanced UI with code editor for scripted processors
[ https://issues.apache.org/jira/browse/NIFI-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri reassigned NIFI-4400: -- Assignee: Yuri > Advanced UI with code editor for scripted processors > > > Key: NIFI-4400 > URL: https://issues.apache.org/jira/browse/NIFI-4400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI, Extensions >Reporter: Pierre Villard >Assignee: Yuri > > For the scripted processors it would nice to add an advanced UI with a "code > editor mode" that would provide some very useful features when typing code: > - indentation > - code highlighting > - do not close the window when hitting enter > etc > The use of codemirror.js (as already done for EL auto-completion) sounds like > a good option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-3926) Edit Template information
[ https://issues.apache.org/jira/browse/NIFI-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri updated NIFI-3926: --- Description: Request the addition of an "edit" icon to each template in the list of NiFi Templates (Global Menu > Templates.) The edit would allow the user to modify the template name or description. Arguably, it may also allow the Process Group Id to be editable, but that seems far less likely to be desired. -Another option which is much more substantial and may require a separate ticket is to be able to edit the Template contents itself. That is, editing brings up the template on a fresh graph where components can be added, removed or modified.- Extracted to NIFI-4512. was: Request the addition of an "edit" icon to each template in the list of NiFi Templates (Global Menu > Templates.) The edit would allow the user to modify the template name or description. Arguably, it may also allow the Process Group Id to be editable, but that seems far less likely to be desired. Another option which is much more substantial and may require a separate ticket is to be able to edit the Template contents itself. That is, editing brings up the template on a fresh graph where components can be added, removed or modified. > Edit Template information > - > > Key: NIFI-3926 > URL: https://issues.apache.org/jira/browse/NIFI-3926 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.2.0 >Reporter: Mark Bean >Assignee: Yuri >Priority: Minor > > Request the addition of an "edit" icon to each template in the list of NiFi > Templates (Global Menu > Templates.) The edit would allow the user to modify > the template name or description. Arguably, it may also allow the Process > Group Id to be editable, but that seems far less likely to be desired. > -Another option which is much more substantial and may require a separate > ticket is to be able to edit the Template contents itself. That is, editing > brings up the template on a fresh graph where components can be added, > removed or modified.- Extracted to NIFI-4512. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4512) Edit Template content
Yuri created NIFI-4512: -- Summary: Edit Template content Key: NIFI-4512 URL: https://issues.apache.org/jira/browse/NIFI-4512 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.4.0 Reporter: Yuri Priority: Minor This issue covers advanced editing functionality mentioned in NIFI-3926. It should be possible to be able to edit the Template contents itself. That is, editing brings up the template on a fresh graph where components can be added, removed or modified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (NIFI-3926) Edit Template information
[ https://issues.apache.org/jira/browse/NIFI-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri reassigned NIFI-3926: -- Assignee: Yuri > Edit Template information > - > > Key: NIFI-3926 > URL: https://issues.apache.org/jira/browse/NIFI-3926 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.2.0 >Reporter: Mark Bean >Assignee: Yuri >Priority: Minor > > Request the addition of an "edit" icon to each template in the list of NiFi > Templates (Global Menu > Templates.) The edit would allow the user to modify > the template name or description. Arguably, it may also allow the Process > Group Id to be editable, but that seems far less likely to be desired. > Another option which is much more substantial and may require a separate > ticket is to be able to edit the Template contents itself. That is, editing > brings up the template on a fresh graph where components can be added, > removed or modified. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4400) Advanced UI with code editor for scripted processors
[ https://issues.apache.org/jira/browse/NIFI-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197501#comment-16197501 ] Yuri commented on NIFI-4400: Oh, now I see. The Jolt Transform UI could definitely serve as an inspiration for the "code editor's" one. > Advanced UI with code editor for scripted processors > > > Key: NIFI-4400 > URL: https://issues.apache.org/jira/browse/NIFI-4400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI, Extensions >Reporter: Pierre Villard > > For the scripted processors it would nice to add an advanced UI with a "code > editor mode" that would provide some very useful features when typing code: > - indentation > - code highlighting > - do not close the window when hitting enter > etc > The use of codemirror.js (as already done for EL auto-completion) sounds like > a good option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4400) Advanced UI with code editor for scripted processors
[ https://issues.apache.org/jira/browse/NIFI-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197437#comment-16197437 ] Yuri commented on NIFI-4400: Currently Processor's Properties doesn't contain a specialized way of hinting UI editor style. Adding an editor type attribute to the Property would be suitable for the "script body editor" use case. I guess it would be useful for other classes of Properties, such as file path or JSONPath. > Advanced UI with code editor for scripted processors > > > Key: NIFI-4400 > URL: https://issues.apache.org/jira/browse/NIFI-4400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI, Extensions >Reporter: Pierre Villard > > For the scripted processors it would nice to add an advanced UI with a "code > editor mode" that would provide some very useful features when typing code: > - indentation > - code highlighting > - do not close the window when hitting enter > etc > The use of codemirror.js (as already done for EL auto-completion) sounds like > a good option. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4390) Add a keyboard shortcut for Connection related dialogs
[ https://issues.apache.org/jira/browse/NIFI-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184399#comment-16184399 ] Yuri commented on NIFI-4390: [~scottyaslan] I have been thinking about the grouping but it seems I am unable to sort all of them. So far I gathered the dialogs and listed them in the attached spreadsheet. My guess is the ones labeled as 'read-only info' could be treated in the same way as for instance the 'yes-no-dialog'. I am sure the current list doesn't include all relevant dialogs. So please add any missing ones. > Add a keyboard shortcut for Connection related dialogs > -- > > Key: NIFI-4390 > URL: https://issues.apache.org/jira/browse/NIFI-4390 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.3.0 >Reporter: Yuri >Priority: Minor > Labels: dialogs, shortcuts, ui, ux > Attachments: nifi_dialogs_v1.ods > > > Current dialogs don't allow to bound a keyboard shortcut to an action. This > hinders the UX, since there are many dialogs involved in the most common > interactions. > For instance, adding a new connection with a single relationship still > requires a click at the confirm button. Instead, it should be possible to > confirm the dialog simply by hitting the Enter key. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (NIFI-4390) Add a keyboard shortcut for Connection related dialogs
[ https://issues.apache.org/jira/browse/NIFI-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuri updated NIFI-4390: --- Attachment: nifi_dialogs_v1.ods Initial version of gathered application dialogs > Add a keyboard shortcut for Connection related dialogs > -- > > Key: NIFI-4390 > URL: https://issues.apache.org/jira/browse/NIFI-4390 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.3.0 >Reporter: Yuri >Priority: Minor > Labels: dialogs, shortcuts, ui, ux > Attachments: nifi_dialogs_v1.ods > > > Current dialogs don't allow to bound a keyboard shortcut to an action. This > hinders the UX, since there are many dialogs involved in the most common > interactions. > For instance, adding a new connection with a single relationship still > requires a click at the confirm button. Instead, it should be possible to > confirm the dialog simply by hitting the Enter key. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4423) Add a confirmation of a Counter reset action
Yuri created NIFI-4423: -- Summary: Add a confirmation of a Counter reset action Key: NIFI-4423 URL: https://issues.apache.org/jira/browse/NIFI-4423 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.3.0 Reporter: Yuri Priority: Minor User can reset value of a defined counter in the Counteres view. The action is triggered by clicking on a reset button. No confirmation is present. A simple missclick may result in a counter reset. This might be a serious problem for use cases relying on a counters (message ID, request ID, etc.). A Yes/No confirmation dialog should prevent the counter data loss. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4390) Add a keyboard shortcut for Connection related dialogs
[ https://issues.apache.org/jira/browse/NIFI-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16174735#comment-16174735 ] Yuri commented on NIFI-4390: [~rmoran] [~scottyaslan] I support adding more keyboard shortcuts. I think it deserves its own story/epic. Currently the application features 'Enter' shortcut for dialogs which contain a text input. For instance: 'Add Processor/CS' (filter input), 'Add Input/Output Port' (port name) or 'Add Group' (group name). However, many simple confirmation dialogs don't feature any shortcut. Those cases can IMO hurt the UX significantly. The NIFI-1592 is nice but I guess the dialog accept/cancel functionality should be a priority. > Add a keyboard shortcut for Connection related dialogs > -- > > Key: NIFI-4390 > URL: https://issues.apache.org/jira/browse/NIFI-4390 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.3.0 >Reporter: Yuri >Priority: Minor > Labels: dialogs, shortcuts, ui, ux > > Current dialogs don't allow to bound a keyboard shortcut to an action. This > hinders the UX, since there are many dialogs involved in the most common > interactions. > For instance, adding a new connection with a single relationship still > requires a click at the confirm button. Instead, it should be possible to > confirm the dialog simply by hitting the Enter key. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4390) Add a keyboard shortcut for Connection related dialogs
Yuri created NIFI-4390: -- Summary: Add a keyboard shortcut for Connection related dialogs Key: NIFI-4390 URL: https://issues.apache.org/jira/browse/NIFI-4390 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.3.0 Reporter: Yuri Priority: Minor Current dialogs don't allow to bound a keyboard shortcut to an action. This hinders the UX, since there are many dialogs involved in the most common interactions. For instance, adding a new connection with a single relationship still requires a click at the confirm button. Instead, it should be possible to confirm the dialog simply by hitting the Enter key. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-3711) Change default size of provenance details dialog to show Replay button by default
[
https://issues.apache.org/jira/browse/NIFI-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161513#comment-16161513
]
Yuri commented on NIFI-3711:
[~mcgilman] Interesting. Just for the record, my testing was done on
Gentoo/GNOME3.
> Change default size of provenance details dialog to show Replay button by
> default
> -
>
> Key: NIFI-3711
> URL: https://issues.apache.org/jira/browse/NIFI-3711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Priority: Minor
> Labels: beginner, dialog, provenance, replay, ui
> Attachments: Screen Shot 2017-04-18 at 11.19.12 AM.png, Screen Shot
> 2017-04-18 at 11.19.46 AM.png, Screenshot from 2017-09-10 20-56-41.png
>
>
> The provenance details dialog is sized such that the "Replay" button on the
> "Content" tab is not visible by default and there is no visible scroll bar
> indicating that the panel has additional content. Some users have reported
> being unaware of the replay feature because of this. I propose changing the
> default dialog size to ensure the panel is fully displayed ({{min-height}}?).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (NIFI-3711) Change default size of provenance details dialog to show Replay button by default
[
https://issues.apache.org/jira/browse/NIFI-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160440#comment-16160440
]
Yuri edited comment on NIFI-3711 at 9/10/17 7:01 PM:
-
Using _NiFi 1.3.0_ and _FF 55_, the Content tab's overflow seems to work OK. It
displays a scroll bar when the replay feature is available. [^Screenshot from
2017-09-10 20-56-41.png]
was (Author: yuri1969):
Using _NiFi 1.3.0_ and _FF 55_, the tab's overflow seems to work. It displays a
scroll bar when the replay feature is available. [^Screenshot from 2017-09-10
20-56-41.png]
> Change default size of provenance details dialog to show Replay button by
> default
> -
>
> Key: NIFI-3711
> URL: https://issues.apache.org/jira/browse/NIFI-3711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Priority: Minor
> Labels: beginner, dialog, provenance, replay, ui
> Attachments: Screen Shot 2017-04-18 at 11.19.12 AM.png, Screen Shot
> 2017-04-18 at 11.19.46 AM.png, Screenshot from 2017-09-10 20-56-41.png
>
>
> The provenance details dialog is sized such that the "Replay" button on the
> "Content" tab is not visible by default and there is no visible scroll bar
> indicating that the panel has additional content. Some users have reported
> being unaware of the replay feature because of this. I propose changing the
> default dialog size to ensure the panel is fully displayed ({{min-height}}?).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (NIFI-3711) Change default size of provenance details dialog to show Replay button by default
[
https://issues.apache.org/jira/browse/NIFI-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuri updated NIFI-3711:
---
Attachment: Screenshot from 2017-09-10 20-56-41.png
> Change default size of provenance details dialog to show Replay button by
> default
> -
>
> Key: NIFI-3711
> URL: https://issues.apache.org/jira/browse/NIFI-3711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Priority: Minor
> Labels: beginner, dialog, provenance, replay, ui
> Attachments: Screen Shot 2017-04-18 at 11.19.12 AM.png, Screen Shot
> 2017-04-18 at 11.19.46 AM.png, Screenshot from 2017-09-10 20-56-41.png
>
>
> The provenance details dialog is sized such that the "Replay" button on the
> "Content" tab is not visible by default and there is no visible scroll bar
> indicating that the panel has additional content. Some users have reported
> being unaware of the replay feature because of this. I propose changing the
> default dialog size to ensure the panel is fully displayed ({{min-height}}?).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (NIFI-3711) Change default size of provenance details dialog to show Replay button by default
[
https://issues.apache.org/jira/browse/NIFI-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16160440#comment-16160440
]
Yuri commented on NIFI-3711:
Using _NiFi 1.3.0_ and _FF 55_, the tab's overflow seems to work. It displays a
scroll bar when the replay feature is available. [^Screenshot from 2017-09-10
20-56-41.png]
> Change default size of provenance details dialog to show Replay button by
> default
> -
>
> Key: NIFI-3711
> URL: https://issues.apache.org/jira/browse/NIFI-3711
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Affects Versions: 1.1.1
>Reporter: Andy LoPresto
>Priority: Minor
> Labels: beginner, dialog, provenance, replay, ui
> Attachments: Screen Shot 2017-04-18 at 11.19.12 AM.png, Screen Shot
> 2017-04-18 at 11.19.46 AM.png, Screenshot from 2017-09-10 20-56-41.png
>
>
> The provenance details dialog is sized such that the "Replay" button on the
> "Content" tab is not visible by default and there is no visible scroll bar
> indicating that the panel has additional content. Some users have reported
> being unaware of the replay feature because of this. I propose changing the
> default dialog size to ensure the panel is fully displayed ({{min-height}}?).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (NIFI-4347) Extend documentation with double-click shortcuts info
Yuri created NIFI-4347: -- Summary: Extend documentation with double-click shortcuts info Key: NIFI-4347 URL: https://issues.apache.org/jira/browse/NIFI-4347 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Yuri Priority: Trivial Recent additions of double-click triggered shortcuts should be included in the documentation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4033) Allow multiple Controller Services to be enabled or disabled
[ https://issues.apache.org/jira/browse/NIFI-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134152#comment-16134152 ] Yuri commented on NIFI-4033: Enabling a CS involves setting its scope. How should the multi-select behave? > Allow multiple Controller Services to be enabled or disabled > > > Key: NIFI-4033 > URL: https://issues.apache.org/jira/browse/NIFI-4033 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne > > It would be nice to select multiple controller services (via checkbox or just > shift-click or whatever) and then click a button to enable or disable all of > them. It would be particularly useful when importing a new template, for > example. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4271) Revert double-click behavior back to delete a bend point
Yuri created NIFI-4271: -- Summary: Revert double-click behavior back to delete a bend point Key: NIFI-4271 URL: https://issues.apache.org/jira/browse/NIFI-4271 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Yuri Priority: Minor Revert processor connection's bend point double-click behavior introduced in NIFI-1580. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (NIFI-4234) The Filter in the Add Processor window should return valid results even if search terms do not exactly match tags
[
https://issues.apache.org/jira/browse/NIFI-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115501#comment-16115501
]
Yuri edited comment on NIFI-4234 at 8/5/17 7:56 PM:
It seems the current simple regex match on processor tags doesn't fit for a bit
more complex use cases.
Queries containing the tag separator char ({{,}}) should be treated separately.
In this particular case the query would be tokenized and behave like:
"_database && rdbms_". This way it makes sense to me, since you are being more
specific by adding tags.
In this case the "_database rdbms_" query wouldn't work. Since tags like "_data
science_" exist, the space char can't be treated like a token separator.
I'm not sure an actual query language is needed.
was (Author: yuri1969):
It seems the current simple regex match on processor tags doesn't fit for a bit
more complex use cases.
Queries containing the tag separator char ({{,}}) should be treated separately.
In this particular case the query would be tokenized and behave like:
"_database && rdbms_". This way it makes sense to me, since you are being more
specific by adding tags.
In this case the "_database rdbms_" query wouldn't work. Since tags like "_data
science_" exist, the {{ }} can't be treated like a token separator.
I'm not sure an actual query language is needed.
> The Filter in the Add Processor window should return valid results even if
> search terms do not exactly match tags
> -
>
> Key: NIFI-4234
> URL: https://issues.apache.org/jira/browse/NIFI-4234
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
>Reporter: Andrew Lim
>Priority: Minor
>
> The filter field should be more forgiving. For example, if you enter
> "database, rdbms" you get 2 results (ConvertJSONToSQL and PutSQL processors).
> I would think the following would also return the same results, but you get
> none:
> "database,rdbms"
> "database rdbms"
> "rdbms, database"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (NIFI-4266) Allow double-click to display Event details
Yuri created NIFI-4266: -- Summary: Allow double-click to display Event details Key: NIFI-4266 URL: https://issues.apache.org/jira/browse/NIFI-4266 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Yuri Priority: Minor A user frequently has to open the "View details" dialog when inspecting data in NiFi Provenance. Each time the user has to right-click the event node and then select "View details" from the menu. It would be quicker to double-click an event node to display the "details" dialog. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-3747) Add link to context sensitive Help within configuration dialogs
[ https://issues.apache.org/jira/browse/NIFI-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113229#comment-16113229 ] Yuri commented on NIFI-3747: >From my point of view, this can be solved by adding existing _Usage_ button + >link also to processor/service/task _Configure_ dialog. > Add link to context sensitive Help within configuration dialogs > --- > > Key: NIFI-3747 > URL: https://issues.apache.org/jira/browse/NIFI-3747 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Andrew Lim >Priority: Minor > > When the user is in the middle of configuring a processor, a controller > service, a reporting task, etc. it is done within a dialog. But that dialog > does not provide any way for the user to get to the context specific help for > that processor, controller service, or reporting task while within that > dialog. The user has to close the dialog to access that help. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4219) Describe partial builds in Quickstart guide
Yuri created NIFI-4219: -- Summary: Describe partial builds in Quickstart guide Key: NIFI-4219 URL: https://issues.apache.org/jira/browse/NIFI-4219 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Yuri Priority: Trivial During development you probably do not opt for lengthy entire code base builds. It might be helpful to add a note describing how to perform partial builds. This info seems to fit the Quickstart guide best since it describes the build process. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4125) Add basic security settings to TransformXml
Yuri created NIFI-4125: -- Summary: Add basic security settings to TransformXml Key: NIFI-4125 URL: https://issues.apache.org/jira/browse/NIFI-4125 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.3.0 Reporter: Yuri Priority: Minor Since data flows can generally deal with non-trusted data, the processors should handle it in a secure manner. In case of XML there are various known vulnerabilities - [OWASP|https://www.owasp.org/index.php/XML_External_Entity_%28XXE%29_Processing]. Some can be mitigated via XML parser/XSLT Processor features. The TransformXml processor should have a setting enabling these secure settings. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NIFI-4119) Improve UX of canvas label configuration
Yuri created NIFI-4119: -- Summary: Improve UX of canvas label configuration Key: NIFI-4119 URL: https://issues.apache.org/jira/browse/NIFI-4119 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.3.0 Reporter: Yuri Priority: Trivial The single most used field of a canvas label's configuration dialog is it's text value. Naturally, it should be in focus as soon as you open the dialog. Current UX seems to be tedious when dealing with multiple labels. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
