Re: Creating no argument record path functions
I was thinking about that, but is that generally safe? Are there are any
known gotchas with mixing the two in the same field?
On Fri, Jul 26, 2019 at 6:52 PM Bryan Bende wrote:
> I know this doesn’t really answer the question, but in most cases couldn’t
> you use EL ${now()} in the record path statement and it would get evaluated
> before the record path?
>
> On Fri, Jul 26, 2019 at 6:42 PM Mike Thomsen
> wrote:
>
> > I tried to creating a simple now() timestamp function and got this:
> >
> > org.apache.nifi.record.path.exception.RecordPathException:
> > org.antlr.runtime.tree.RewriteEmptyStreamException: rule optionalArgument
> >
> > at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:105)
> > at
> >
> >
> org.apache.nifi.record.path.TestRecordPath.testNowFunction(TestRecordPath.java:1284)
> >
> > Caused by: org.antlr.runtime.tree.RewriteEmptyStreamException: rule
> > optionalArgument
> > at
> >
> >
> org.antlr.runtime.tree.RewriteRuleElementStream._next(RewriteRuleElementStream.java:158)
> > at
> >
> >
> org.antlr.runtime.tree.RewriteRuleElementStream.nextTree(RewriteRuleElementStream.java:145)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.argumentList(RecordPathParser.java:1633)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.function(RecordPathParser.java:1708)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.expression(RecordPathParser.java:1169)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.argument(RecordPathParser.java:1461)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.optionalArgument(RecordPathParser.java:1523)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.argumentList(RecordPathParser.java:1583)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.function(RecordPathParser.java:1708)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.pathOrFunction(RecordPathParser.java:4312)
> > at
> >
> >
> org.apache.nifi.record.path.RecordPathParser.pathExpression(RecordPathParser.java:4367)
> > at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:84)
> > ... 23 more
> >
> > Am I trying to do something that the RecordPath grammar doesn't accept?
> >
> > Thanks,
> >
> > Mike
> >
> --
> Sent from Gmail Mobile
>
Re: Creating no argument record path functions
I know this doesn’t really answer the question, but in most cases couldn’t
you use EL ${now()} in the record path statement and it would get evaluated
before the record path?
On Fri, Jul 26, 2019 at 6:42 PM Mike Thomsen wrote:
> I tried to creating a simple now() timestamp function and got this:
>
> org.apache.nifi.record.path.exception.RecordPathException:
> org.antlr.runtime.tree.RewriteEmptyStreamException: rule optionalArgument
>
> at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:105)
> at
>
> org.apache.nifi.record.path.TestRecordPath.testNowFunction(TestRecordPath.java:1284)
>
> Caused by: org.antlr.runtime.tree.RewriteEmptyStreamException: rule
> optionalArgument
> at
>
> org.antlr.runtime.tree.RewriteRuleElementStream._next(RewriteRuleElementStream.java:158)
> at
>
> org.antlr.runtime.tree.RewriteRuleElementStream.nextTree(RewriteRuleElementStream.java:145)
> at
>
> org.apache.nifi.record.path.RecordPathParser.argumentList(RecordPathParser.java:1633)
> at
>
> org.apache.nifi.record.path.RecordPathParser.function(RecordPathParser.java:1708)
> at
>
> org.apache.nifi.record.path.RecordPathParser.expression(RecordPathParser.java:1169)
> at
>
> org.apache.nifi.record.path.RecordPathParser.argument(RecordPathParser.java:1461)
> at
>
> org.apache.nifi.record.path.RecordPathParser.optionalArgument(RecordPathParser.java:1523)
> at
>
> org.apache.nifi.record.path.RecordPathParser.argumentList(RecordPathParser.java:1583)
> at
>
> org.apache.nifi.record.path.RecordPathParser.function(RecordPathParser.java:1708)
> at
>
> org.apache.nifi.record.path.RecordPathParser.pathOrFunction(RecordPathParser.java:4312)
> at
>
> org.apache.nifi.record.path.RecordPathParser.pathExpression(RecordPathParser.java:4367)
> at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:84)
> ... 23 more
>
> Am I trying to do something that the RecordPath grammar doesn't accept?
>
> Thanks,
>
> Mike
>
--
Sent from Gmail Mobile
Creating no argument record path functions
I tried to creating a simple now() timestamp function and got this: org.apache.nifi.record.path.exception.RecordPathException: org.antlr.runtime.tree.RewriteEmptyStreamException: rule optionalArgument at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:105) at org.apache.nifi.record.path.TestRecordPath.testNowFunction(TestRecordPath.java:1284) Caused by: org.antlr.runtime.tree.RewriteEmptyStreamException: rule optionalArgument at org.antlr.runtime.tree.RewriteRuleElementStream._next(RewriteRuleElementStream.java:158) at org.antlr.runtime.tree.RewriteRuleElementStream.nextTree(RewriteRuleElementStream.java:145) at org.apache.nifi.record.path.RecordPathParser.argumentList(RecordPathParser.java:1633) at org.apache.nifi.record.path.RecordPathParser.function(RecordPathParser.java:1708) at org.apache.nifi.record.path.RecordPathParser.expression(RecordPathParser.java:1169) at org.apache.nifi.record.path.RecordPathParser.argument(RecordPathParser.java:1461) at org.apache.nifi.record.path.RecordPathParser.optionalArgument(RecordPathParser.java:1523) at org.apache.nifi.record.path.RecordPathParser.argumentList(RecordPathParser.java:1583) at org.apache.nifi.record.path.RecordPathParser.function(RecordPathParser.java:1708) at org.apache.nifi.record.path.RecordPathParser.pathOrFunction(RecordPathParser.java:4312) at org.apache.nifi.record.path.RecordPathParser.pathExpression(RecordPathParser.java:4367) at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:84) ... 23 more Am I trying to do something that the RecordPath grammar doesn't accept? Thanks, Mike
Re: svn commit: r35033 - /dev/nifi/nifi-fds/nifi-fds-0.2.0/ /release/nifi/nifi-fds/nifi-fds-0.2.0/
Please send the instructions to be removed from this alias. Zaminah D Williams Onyx Consulting Services, LLC President/CEO (410) 814-7651 (o) (301) 467-6680 (c) From: scottyas...@apache.org Sent: Friday, July 26, 2019 4:22:04 PM To: comm...@nifi.apache.org Subject: svn commit: r35033 - /dev/nifi/nifi-fds/nifi-fds-0.2.0/ /release/nifi/nifi-fds/nifi-fds-0.2.0/ Author: scottyaslan Date: Fri Jul 26 20:22:04 2019 New Revision: 35033 Log: NIFI-FDS-6469 Added: release/nifi/nifi-fds/nifi-fds-0.2.0/ - copied from r35032, dev/nifi/nifi-fds/nifi-fds-0.2.0/ Removed: dev/nifi/nifi-fds/nifi-fds-0.2.0/
[RESULT][VOTE] Release Apache NiFi Flow Design System 0.2.0
Apache NiFi Community, I am pleased to announce that including my +1 (binding) vote the 0.2.0 release of Apache NiFi Flow Design System passes with 4 +1 (binding) votes 4 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the PMC vote thread: http://apache-nifi-developer-list.39713.n7.nabble.com/VOTE-Release-Apache-NiFi-Flow-Design-System-0-2-0-RC2-td20938.html
Re: UI Features
Thanks for sharing your thoughts, Raymond. Some of the items you call out have tickets already or there may be similar/related ones. I will plan to go through each and reply back with my findings. Thanks again! On Fri, Jul 26, 2019 at 9:46 AM ski n wrote: > I was creating a flow and I noticed some things of the GUI that were > missing. Don’t know if there already plans/tickets for these items, but I > would like your opinion first. > > If you think it’s a good idea and there is no ticket yet than I will create > one: > > 1) It’s already possible to align flows, but sometimes it takes a lot > of time to make a flow look clean. I like if an automatically ordering > option of a flow (which calculate the best view). Ordering a flow from left > to right or ordering a flow from top to bottom. > > 2) Double-click on the canvas to zoom in. > > 3) Add possibility to use keyboard to move elements (for example > processors) > > 4) Select multiple items with mouse (like MS Visio). Now you need the > shift key to do this. > > 5) Moving step/flows into a process group. “Right-Click” on a flow step > (Move step to process group / Move flow to process group / Create process > group for this flow) > > 6) Possibility to add links in labels (for example link to a process > group) > > 7) Search box (to find and navigate to a process group/flow/flow step) > > 8) Queues are highlighted yellow, while processors are highlight black > (Better both yellow, black is hard to see) > > 9) Add Ctrl X / Cut > > 10) Add Ctrl Z / Revert last change > > 11) Sometimes the "apply" button navigates you directly back to the canvas > (for example with configuration), sometimes not (process group). Like to > have a 'save' button which means apply change and leave the popup, while > apply applies the change. > > 12) Export canvas to image (jpeg/png) > > 13) Links to file resources --> open the resource in an online editor > > 14) Option to edit the processor as XML (sometimes this goes faster). Now > you need to export/import the processor as a template. > > > > Best regards, > > > Raymond >
Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)
+1 Release this package as nifi-fds-0.2.0 Thanks for putting this together, Scott! On Fri, Jul 26, 2019 at 2:10 PM Joe Witt wrote: > +1 (binding) > > Full clean build following readme and testapp check out. L looks good. > Sigs/Commit checks out. > > I would recommend ditching the sha1 entry. 256 and 512 are good. > > Thanks > > On Fri, Jul 26, 2019 at 1:33 PM Marc Parisi wrote: > > > +1 (binding). I built and tested according to the release helper guide. > > Demo app, hashes, readmes, and notices all look good. > > > > Thanks Scott! > > > > On Fri, Jul 26, 2019 at 10:09 AM Matt Gilman > > wrote: > > > > > +1 (binding) Release this package as nifi-fds-0.2.0 > > > > > > Ran through release helper. Checked out demo app and all looks good. > > > > > > Thanks for RMing Scott! > > > > > > Matt > > > > > > On Wed, Jul 24, 2019 at 7:15 AM Kovacs Andras > > > > > > > > wrote: > > > > > > > * Verified the signature > > > > * Verified the hashes > > > > * Verified README > > > > * Verified the demo app works as expected > > > > > > > > Unfortunately majority of npm scripts are broken on windows, however > I > > > > could make them run and test the app with some minor changes. JIRA > > issue: > > > > https://issues.apache.org/jira/browse/NIFI-6481 > > > > > > > > + 1 (non-binding) > > > > > > > > András > > > > > > > > On Wed, Jul 24, 2019 at 11:41 AM Adam Kocsis > > > > > > > > > > > wrote: > > > > > > > > > * Verified the git commit > > > > > * Verified the signature > > > > > * Verified the hashes > > > > > * Verified the build > > > > > * Verified README > > > > > * Verified the demo app works as expected > > > > > > > > > > + 1 (non-binding) > > > > > > > > > > Cheers, > > > > > Adam > > > > > > > > > > On Wed, Jul 24, 2019 at 3:33 AM Robert Fellows < > > rob.fell...@gmail.com> > > > > > wrote: > > > > > > > > > > > * Verified the signature > > > > > > * Verified the hashes > > > > > > * Verified the build > > > > > > * Verified README > > > > > > * Verified the demo app works as expected > > > > > > * Successfully npm link'd @nifi-fds/core in nifi-registry, worked > > > with > > > > > > documented updates. > > > > > > > > > > > > + 1 (non-binding) > > > > > > > > > > > > > > > > > > -- Rob Fellows > > > > > > > > > > > > On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan < > scottyas...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > > > Apache > > > > > > > > > > > > > > NiFi Flow Design System 0.2.0. > > > > > > > > > > > > > > > > > > > > > The source zip, including signatures, etc. can be found at: > > > > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/ > > > > > > > > > > > > > > > > > > > > > The Git tag is NIFI-FDS-0.2.0-RC2 > > > > > > > > > > > > > > The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17 > > > > > > > > > > > > > > > > > > > > > Checksums of nifi-fds-0.2.0-source-release.zip: > > > > > > > > > > > > > > SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d > > > > > > > > > > > > > > SHA256: > > > > > 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f > > > > > > > > > > > > > > SHA512: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1 > > > > > > > > > > > > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > > > > > > > https://people.apache.org/keys/committer/scottyaslan.asc > > > > > > > > > > > > > > > > > > > > > KEYS file available here: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > > > > > > > > > > > > 36 issues were closed/resolved for this release: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453=12316020 > > > > > > > > > > > > > > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0 > > > > > > > > > > > > > > > > > > > > > The vote will be open for 72 hours. > > > > > > > > > > > > > > > > > > > > > Please download the release candidate and evaluate the > necessary > > > > items > > > > > > > > > > > > > > including checking hashes, signatures, build from source, and > > test. > > > > > > > > > > > > > > > > > > > > > The please vote: > > > > > > > > > > > > > > > > > > > > > [ ] +1 Release this package as nifi-fds-0.2.0 > > > > > > > > > > > > > > [ ] +0 no opinion > > >
Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)
+1 (binding) Full clean build following readme and testapp check out. L looks good. Sigs/Commit checks out. I would recommend ditching the sha1 entry. 256 and 512 are good. Thanks On Fri, Jul 26, 2019 at 1:33 PM Marc Parisi wrote: > +1 (binding). I built and tested according to the release helper guide. > Demo app, hashes, readmes, and notices all look good. > > Thanks Scott! > > On Fri, Jul 26, 2019 at 10:09 AM Matt Gilman > wrote: > > > +1 (binding) Release this package as nifi-fds-0.2.0 > > > > Ran through release helper. Checked out demo app and all looks good. > > > > Thanks for RMing Scott! > > > > Matt > > > > On Wed, Jul 24, 2019 at 7:15 AM Kovacs Andras > > > > > wrote: > > > > > * Verified the signature > > > * Verified the hashes > > > * Verified README > > > * Verified the demo app works as expected > > > > > > Unfortunately majority of npm scripts are broken on windows, however I > > > could make them run and test the app with some minor changes. JIRA > issue: > > > https://issues.apache.org/jira/browse/NIFI-6481 > > > > > > + 1 (non-binding) > > > > > > András > > > > > > On Wed, Jul 24, 2019 at 11:41 AM Adam Kocsis > > > > > > > > wrote: > > > > > > > * Verified the git commit > > > > * Verified the signature > > > > * Verified the hashes > > > > * Verified the build > > > > * Verified README > > > > * Verified the demo app works as expected > > > > > > > > + 1 (non-binding) > > > > > > > > Cheers, > > > > Adam > > > > > > > > On Wed, Jul 24, 2019 at 3:33 AM Robert Fellows < > rob.fell...@gmail.com> > > > > wrote: > > > > > > > > > * Verified the signature > > > > > * Verified the hashes > > > > > * Verified the build > > > > > * Verified README > > > > > * Verified the demo app works as expected > > > > > * Successfully npm link'd @nifi-fds/core in nifi-registry, worked > > with > > > > > documented updates. > > > > > > > > > > + 1 (non-binding) > > > > > > > > > > > > > > > -- Rob Fellows > > > > > > > > > > On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan > > > > > wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > > Apache > > > > > > > > > > > > NiFi Flow Design System 0.2.0. > > > > > > > > > > > > > > > > > > The source zip, including signatures, etc. can be found at: > > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/ > > > > > > > > > > > > > > > > > > The Git tag is NIFI-FDS-0.2.0-RC2 > > > > > > > > > > > > The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17 > > > > > > > > > > > > > > > > > > Checksums of nifi-fds-0.2.0-source-release.zip: > > > > > > > > > > > > SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d > > > > > > > > > > > > SHA256: > > > > 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f > > > > > > > > > > > > SHA512: > > > > > > > > > > > > > > > > > > > > > > > > > > > 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1 > > > > > > > > > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > > > > > https://people.apache.org/keys/committer/scottyaslan.asc > > > > > > > > > > > > > > > > > > KEYS file available here: > > > > > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > > > > > > > > > 36 issues were closed/resolved for this release: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453=12316020 > > > > > > > > > > > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0 > > > > > > > > > > > > > > > > > > The vote will be open for 72 hours. > > > > > > > > > > > > > > > > > > Please download the release candidate and evaluate the necessary > > > items > > > > > > > > > > > > including checking hashes, signatures, build from source, and > test. > > > > > > > > > > > > > > > > > > The please vote: > > > > > > > > > > > > > > > > > > [ ] +1 Release this package as nifi-fds-0.2.0 > > > > > > > > > > > > [ ] +0 no opinion > > > > > > > > > > > > [ ] -1 Do not release this package because... > > > > > > > > > > > > > > > > > > > > > -- > > > > > --- > > > > > Rob Fellows > > > > > > > > > > > > > > >
Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)
+1 (binding). I built and tested according to the release helper guide. Demo app, hashes, readmes, and notices all look good. Thanks Scott! On Fri, Jul 26, 2019 at 10:09 AM Matt Gilman wrote: > +1 (binding) Release this package as nifi-fds-0.2.0 > > Ran through release helper. Checked out demo app and all looks good. > > Thanks for RMing Scott! > > Matt > > On Wed, Jul 24, 2019 at 7:15 AM Kovacs Andras > > wrote: > > > * Verified the signature > > * Verified the hashes > > * Verified README > > * Verified the demo app works as expected > > > > Unfortunately majority of npm scripts are broken on windows, however I > > could make them run and test the app with some minor changes. JIRA issue: > > https://issues.apache.org/jira/browse/NIFI-6481 > > > > + 1 (non-binding) > > > > András > > > > On Wed, Jul 24, 2019 at 11:41 AM Adam Kocsis > > > > > wrote: > > > > > * Verified the git commit > > > * Verified the signature > > > * Verified the hashes > > > * Verified the build > > > * Verified README > > > * Verified the demo app works as expected > > > > > > + 1 (non-binding) > > > > > > Cheers, > > > Adam > > > > > > On Wed, Jul 24, 2019 at 3:33 AM Robert Fellows > > > wrote: > > > > > > > * Verified the signature > > > > * Verified the hashes > > > > * Verified the build > > > > * Verified README > > > > * Verified the demo app works as expected > > > > * Successfully npm link'd @nifi-fds/core in nifi-registry, worked > with > > > > documented updates. > > > > > > > > + 1 (non-binding) > > > > > > > > > > > > -- Rob Fellows > > > > > > > > On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan > > > wrote: > > > > > > > > > Hello, > > > > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > Apache > > > > > > > > > > NiFi Flow Design System 0.2.0. > > > > > > > > > > > > > > > The source zip, including signatures, etc. can be found at: > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/ > > > > > > > > > > > > > > > The Git tag is NIFI-FDS-0.2.0-RC2 > > > > > > > > > > The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17 > > > > > > > > > > > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17 > > > > > > > > > > > > > > > Checksums of nifi-fds-0.2.0-source-release.zip: > > > > > > > > > > SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d > > > > > > > > > > SHA256: > > > 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f > > > > > > > > > > SHA512: > > > > > > > > > > > > > > > > > > > > 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1 > > > > > > > > > > > > > > > Release artifacts are signed with the following key: > > > > > > > > > > https://people.apache.org/keys/committer/scottyaslan.asc > > > > > > > > > > > > > > > KEYS file available here: > > > > > > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > > > > > > 36 issues were closed/resolved for this release: > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453=12316020 > > > > > > > > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0 > > > > > > > > > > > > > > > The vote will be open for 72 hours. > > > > > > > > > > > > > > > Please download the release candidate and evaluate the necessary > > items > > > > > > > > > > including checking hashes, signatures, build from source, and test. > > > > > > > > > > > > > > > The please vote: > > > > > > > > > > > > > > > [ ] +1 Release this package as nifi-fds-0.2.0 > > > > > > > > > > [ ] +0 no opinion > > > > > > > > > > [ ] -1 Do not release this package because... > > > > > > > > > > > > > > > > > -- > > > > --- > > > > Rob Fellows > > > > > > > > > >
UI Features
I was creating a flow and I noticed some things of the GUI that were missing. Don’t know if there already plans/tickets for these items, but I would like your opinion first. If you think it’s a good idea and there is no ticket yet than I will create one: 1) It’s already possible to align flows, but sometimes it takes a lot of time to make a flow look clean. I like if an automatically ordering option of a flow (which calculate the best view). Ordering a flow from left to right or ordering a flow from top to bottom. 2) Double-click on the canvas to zoom in. 3) Add possibility to use keyboard to move elements (for example processors) 4) Select multiple items with mouse (like MS Visio). Now you need the shift key to do this. 5) Moving step/flows into a process group. “Right-Click” on a flow step (Move step to process group / Move flow to process group / Create process group for this flow) 6) Possibility to add links in labels (for example link to a process group) 7) Search box (to find and navigate to a process group/flow/flow step) 8) Queues are highlighted yellow, while processors are highlight black (Better both yellow, black is hard to see) 9) Add Ctrl X / Cut 10) Add Ctrl Z / Revert last change 11) Sometimes the "apply" button navigates you directly back to the canvas (for example with configuration), sometimes not (process group). Like to have a 'save' button which means apply change and leave the popup, while apply applies the change. 12) Export canvas to image (jpeg/png) 13) Links to file resources --> open the resource in an online editor 14) Option to edit the processor as XML (sometimes this goes faster). Now you need to export/import the processor as a template. Best regards, Raymond
