[GitHub] nifi issue #534: Fix for NIFI-1838 & NIFI-1152

Github user PuspenduBanerjee commented on the issue: https://github.com/apache/nifi/pull/534 @pvillard31 @mattyb149 Do we still need more discussion on this or will you be able to check it in? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi issue #543: NIFI-1834 Create PutTCP Processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/543 I agree with @joewitt --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 @taftster thanks for taking another look, yup I can merge this when I get a chance. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user taftster commented on the issue: https://github.com/apache/nifi/pull/272 I'm happy with this PR. Thanks @pvillard31 for all the effort and seeing this through many changes and discussions. @JPercivall can you still merge this? I'm in between environments right

[GitHub] nifi issue #543: NIFI-1834 Create PutTCP Processor

Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/543 In my view the demarcator is a good start. A header and footer could be added later or even just a header could be added and the demarcator could be considered the footer. Something like that.

[GitHub] nifi issue #543: NIFI-1834 Create PutTCP Processor

Github user bbende commented on the issue: https://github.com/apache/nifi/pull/543 I think the intent behind this processor was to send data over a connection, but not to read anything back. Essentially doing what PutSyslog and PutSplunk are doing when in TCP mode. That

[GitHub] nifi issue #543: NIFI-1834 Create PutTCP Processor

Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/543 I think of it a bit like netcat... So silmple examples Finger queries whois queries Begin Blah blah blah blah blah End And get the results back as

[GitHub] nifi issue #543: NIFI-1834 Create PutTCP Processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/543 @trixpan of course you can suggest it. I don't have experience using TCP in production so I don't know exactly what a user would want. Can you provide a use-case? --- If your project is set up

[GitHub] nifi pull request #544: Nifi 1958

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/544 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi issue #544: Nifi 1958

Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/544 Thanks for adding `wks`. I built locally and verified the checkstyle. Please rebase and squash all the commits and push, and I will merge into `master` and `0.x`. --- If your project is set up

[GitHub] nifi pull request #544: Nifi 1958

Github user Mistasong39 commented on a diff in the pull request: https://github.com/apache/nifi/pull/544#discussion_r67589936 --- Diff: nifi-commons/nifi-utils/src/main/java/org/apache/nifi/util/FormatUtils.java --- @@ -176,6 +177,12 @@ public static long getTimeDuration(final

[GitHub] nifi issue #543: NIFI-1834 Create PutTCP Processor

Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/543 @jPercival can I suggest the delimiter to be changed to a header and footer ? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] nifi pull request #544: Nifi 1958

Github user Mistasong39 commented on a diff in the pull request: https://github.com/apache/nifi/pull/544#discussion_r67588724 --- Diff: nifi-commons/nifi-utils/src/main/java/org/apache/nifi/util/FormatUtils.java --- @@ -41,8 +41,9 @@ private static final String MINS =

[GitHub] nifi pull request #544: Nifi 1958

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/544#discussion_r67587861 --- Diff: nifi-commons/nifi-utils/src/main/java/org/apache/nifi/util/FormatUtils.java --- @@ -41,8 +41,9 @@ private static final String MINS =

[GitHub] nifi pull request #544: Nifi 1958

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/544#discussion_r67587884 --- Diff: nifi-commons/nifi-utils/src/main/java/org/apache/nifi/util/FormatUtils.java --- @@ -176,6 +177,12 @@ public static long getTimeDuration(final

[GitHub] nifi issue #544: Nifi 1958

Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/544 Reviewing... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[GitHub] nifi pull request #544: Nifi 1958

GitHub user Mistasong39 opened a pull request: https://github.com/apache/nifi/pull/544 Nifi 1958 Added Functionality to convert weeks to an existing `TimeUnit`. Did not add weeks as a destination `TimeUnit`. You can merge this pull request into a Git repository by running: $

[GitHub] nifi pull request #543: NIFI-1834 Create PutTCP Processor

GitHub user JPercivall opened a pull request: https://github.com/apache/nifi/pull/543 NIFI-1834 Create PutTCP Processor Took Matt Brown's patch and applied my comments. You can merge this pull request into a Git repository by running: $ git pull

Re: Target version for new procesors

Andrew, If you plan to submit it as a PR I would say go with 1.0 (I have been doing that). The wrapping up of 0.7 is at full steam and I think targeting it would just add to the stress. On the the other hand, targeting 1.x gives the reviewers the small courtesy of extra time to go through your

[GitHub] nifi-minifi pull request #19: MINIFI-40 - Defaulting to empty string for key...

GitHub user brosander opened a pull request: https://github.com/apache/nifi-minifi/pull/19 MINIFI-40 - Defaulting to empty string for keystore, truststore, sslP… …rotocol You can merge this pull request into a Git repository by running: $ git pull

[GitHub] nifi pull request #541: NIFI-2032 fixed 'enableControllerServices' logic

Github user olegz commented on a diff in the pull request: https://github.com/apache/nifi/pull/541#discussion_r67582485 --- Diff:

[GitHub] nifi pull request #541: NIFI-2032 fixed 'enableControllerServices' logic

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/541#discussion_r67581551 --- Diff:

[GitHub] nifi pull request #541: NIFI-2032 fixed 'enableControllerServices' logic

Github user alopresto commented on a diff in the pull request: https://github.com/apache/nifi/pull/541#discussion_r67581275 --- Diff:

[GitHub] nifi issue #513: PutHBaseJSON processor treats all values as Strings

Github user bbende commented on the issue: https://github.com/apache/nifi/pull/513 @rtempleton please take a look at https://github.com/apache/nifi/pull/542 I've incorporated your work there with some additional changes which I explained in the PR description. Let me know if

[GitHub] nifi pull request #542: NIFI-1895 for 0.x

GitHub user bbende opened a pull request: https://github.com/apache/nifi/pull/542 NIFI-1895 for 0.x This pull request contains @rtempleton 's work from PR 513, but rebased for the 0.x branch. In addition, there is another commit by me which adds a new property to

[GitHub] nifi pull request #538: NIFI-1774: AbstractControllerService deprecated anno...

Github user rekhajoshm closed the pull request at: https://github.com/apache/nifi/pull/538 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #507: NIFI-1804 Adding ability for FileAuthorizer to autom...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/507 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi issue #507: NIFI-1804 Adding ability for FileAuthorizer to automaticall...

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/507 Looks great @bbende Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and

[GitHub] nifi issue #517: NIFI-1994: Fixed issues with controller services and templa...

Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/517 @mcgilman I have updated the PR to address this. Please try it out again. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] nifi pull request #256: NIFI-1578: Create PutSlack processor

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/256 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Travis CI

Devs, The configuration for Travis CI has had the contrib-check profile turned off. Recent contributions that include additional unit tests have pushed the length of the build over Travis's allowed limit. We should be able to turn this back on as we more towards our extensions registry when we

[GitHub] nifi pull request #256: NIFI-1578: Create PutSlack processor

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/256#discussion_r67562782 --- Diff: nifi-nar-bundles/nifi-slack-bundle/nifi-slack-processors/src/main/java/org/apache/nifi/processors/slack/PutSlack.java --- @@ -0,0 +1,245 @@

Re: Target version for new procesors

Andrew, I'd say try to get a PR in play and hopefully the review-then-commit process can kick-in. We have quite a few PRs in holding status in Github/JIRA so it is not always easy to get through that. Depends on if how complicated the contrib is to test, licensing issues, etc.. Whomever merges

Target version for new procesors

All, With the what appears to be a soon cut of 0.7.0 and 1.0.0 just around the corner, if one were to start on developing a new processor what version(s) should be targeted? -- Thanks, Andrew

[GitHub] nifi pull request #256: NIFI-1578: Create PutSlack processor

Github user adamonduty commented on a diff in the pull request: https://github.com/apache/nifi/pull/256#discussion_r67559978 --- Diff: nifi-nar-bundles/nifi-slack-bundle/nifi-slack-processors/src/main/java/org/apache/nifi/processors/slack/PutSlack.java --- @@ -0,0 +1,245 @@

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

2009 is all done (including 0.x) Sent from my iPhone > On Jun 17, 2016, at 14:16, Joe Percivall > wrote: > > Team, > > We are continuing to have good progress towards the 0.7.0 release. Tagged as > "0.7.0" in Jira and still pending, we currently have 9

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

Team, We are continuing to have good progress towards the 0.7.0 release. Tagged as "0.7.0" in Jira and still pending, we currently have 9 tickets that are all patch available. As a note, there seem to be a number of unversioned "patch available" tickets in Jira. I am going to take a look at

[GitHub] nifi pull request #526: NIFI-1952 Create REST endpoints for user/group/polic...

Github user mcgilman commented on a diff in the pull request: https://github.com/apache/nifi/pull/526#discussion_r67553151 --- Diff: nifi-api/src/main/java/org/apache/nifi/authorization/Group.java --- @@ -24,7 +24,7 @@ /** * A group that users can belong to. */

[GitHub] nifi issue #540: NIFI-2033: Allow Controller Services to be scoped at Contro...

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/540 Looks good! Thanks for knocking this out! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] nifi pull request #540: NIFI-2033: Allow Controller Services to be scoped at...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/540 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #531: NIFI-2007: Restoring bulletin functionality

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/531 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi issue #531: NIFI-2007: Restoring bulletin functionality

Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/531 @mcgilman only thing that i found wrong was that the bulletins do not render the bulletin's 'category'. I created a separate ticket for this -- NIFI-2049. Otherwise, all looks good. Pushed to master.

[GitHub] nifi issue #513: PutHBaseJSON processor treats all values as Strings

Github user bbende commented on the issue: https://github.com/apache/nifi/pull/513 Reviewing and going to merge into 0.x and master if all looks good... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] nifi issue #540: NIFI-2033: Allow Controller Services to be scoped at Contro...

Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/540 Reviewing... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

assigning tasks/updating certain fields in Apache NiFi JIRA

All, Just FYI i think permissions have gotten a bit more strict or maybe it was this way all along but am noticing some confusion. If you're listed as a 'contributor' role for Apache NiFi JIRA you can more easily assign things to yourself and jira among a couple other things. If you're finding

Re: MergeContent to group related files

Sure thing Sumo. Also if you're interested there are some really well thought out and articulated 'enterprise integration patterns' that much of this stuff aligns to. This correlation concept I'm referring to relates to this

[GitHub] nifi issue #257: NIFI-1537 Added SNMP processors

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/257 Ok, finally I am in this PR and no distractions ;) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] nifi pull request #537: NIFI-1955: Deprecate IntegerHolder, LongHolder, Bool...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/537 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi issue #537: NIFI-1955: Deprecate IntegerHolder, LongHolder, BooleanHold...

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/537 Merging --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: MergeContent to group related files

Hi Joe, Thanks a lot helping with the solution. I don’t understand before on how correlation-identifier works. I guess MergeContent may be pulling flowFiles with same correlation-identifier from queue in a batch. I don’t really need 1_N in the file name , this solution should work for my

[GitHub] nifi issue #538: NIFI-1774: AbstractControllerService deprecated annotation

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/538 @rekhajoshm this has been discussed (see NIFI-1774 JIRA comments) based on the same change done and then un-done by @pvillard31. Basically changing OnConfigured to OnEnabled is wrong and in itself will

[GitHub] nifi issue #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

Github user YolandaMDavis commented on the issue: https://github.com/apache/nifi/pull/511 @mcgilman Thank you for reviewing! The PR has been updated based on your comments, including the corrections in the path segment for StandardNiFiWebConfigurationContext. I also found that same

[GitHub] nifi pull request #539: NIFI-1549: Fix JMSConsumer exception

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/539 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

Github user YolandaMDavis commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67536160 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java ---

[GitHub] nifi issue #539: NIFI-1549: Fix JMSConsumer exception

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/539 Thanks you Chris! Merging! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes

[GitHub] nifi pull request #533: Nifi 1690 0.x

Github user olegz closed the pull request at: https://github.com/apache/nifi/pull/533 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #536: NIFI-1037 Ported processor for HDFS' inotify events ...

Github user jjmeyer0 closed the pull request at: https://github.com/apache/nifi/pull/536 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #255: NIFI-1594: Add option to bulk using Index or Update.

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/255 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #511: NIFI-1850 - JSON-to-JSON Schema Converter Editor

Github user YolandaMDavis commented on a diff in the pull request: https://github.com/apache/nifi/pull/511#discussion_r67527428 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/pom.xml --- @@ -355,10 +355,5 @@ spock-core

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67525744 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67525476 --- Diff:

[GitHub] nifi issue #255: NIFI-1594: Add option to bulk using Index or Update.

Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/255 +1 LGTM, built and ran tests, also ran a few sample documents through the flow to exercise the index, update, and upsert logic. Thanks for the contribution! will merge to 0.x and master --- If

[GitHub] nifi issue #349: NIFI-1767 AWS IoT processors

Github user KayLerch commented on the issue: https://github.com/apache/nifi/pull/349 @JPercivall : I started to work on the issues but did not finish. Have a lot of going on at the moment and no time in the next three weeks to finish my work :-( --- If your project is set up for

[GitHub] nifi issue #349: NIFI-1767 AWS IoT processors

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/349 @KayLerch unfortunate you won't be able to finish it for 0.7.0 but I'm looking forward to having it in 1.0.0! I'm going to change the status of the ticket from "Patch Available" to "In Progress".

[GitHub] nifi issue #536: NIFI-1037 Ported processor for HDFS' inotify events to 0.x.

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/536 Thanks @JPercivall! I didn't realize that... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] nifi issue #536: NIFI-1037 Ported processor for HDFS' inotify events to 0.x.

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/536 @jjmeyer0 this was committed to 0.x but unfortunately the magic "This closes #536." commit line only works for the master branch. Could you manually close this PR? --- If your project is set up

[GitHub] nifi issue #349: NIFI-1767 AWS IoT processors

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/349 Hey @KayLerch we're starting to wrap up the 0.7.0 release, did you get a chance to address these concerns? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi issue #518: NIFI-1901: Component based access control tests

Github user bbende commented on the issue: https://github.com/apache/nifi/pull/518 +1 looks good, verified a full build with contrib-check passes locally --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] nifi pull request #518: NIFI-1901: Component based access control tests

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/518 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67515113 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67514815 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67514549 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67514326 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67514060 --- Diff:

[GitHub] nifi pull request #540: NIFI-2033: Allow Controller Services to be scoped at...

GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/540 NIFI-2033: Allow Controller Services to be scoped at Controller level… … instead of just group level You can merge this pull request into a Git repository by running: $ git pull

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67513710 --- Diff:

Re: rest api and json

Jim, What you're seeing definitely sounds strange. I'm not exactly sure what to suggest other than removing various parts until you able to track down which is causing the weirdness. Assuming I'm understanding your jq command, one thing that doesn't look right though is the endpoint and what

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67511428 --- Diff:

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67511182 --- Diff:

Re: MergeContent to group related files

Sumo, Should be doable. The only part that may be tricky is the filename showing 1_N if that means the whole thing has to retain sequential ordering from source through destination. Otherwise... When merging flowfiles together you need to decide 'how should content be merged' and 'how should

[GitHub] nifi pull request #525: NIFI-1976 - Windows Event Log native processor

Github user brosander commented on a diff in the pull request: https://github.com/apache/nifi/pull/525#discussion_r67509411 --- Diff: nifi-nar-bundles/nifi-windows-event-log-bundle/nifi-windows-event-log-nar/src/main/resources/META-INF/LICENSE --- @@ -0,0 +1,239 @@ + +

[GitHub] nifi pull request #255: NIFI-1594: Add option to bulk using Index or Update.

Github user joaohf commented on a diff in the pull request: https://github.com/apache/nifi/pull/255#discussion_r67496113 --- Diff: nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearch.java ---

rest api and json

I have a strange problem. I tried to access the cluster master via the rest api with curl in a bash shell script. In the previous version, it works fine. I make the request, pipe it to JQ and filter out the elements that I want. I do the exact same command as in the shell script and it works

[GitHub] nifi issue #536: NIFI-1037 Ported processor for HDFS' inotify events to 0.x.

Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/536 @jjmeyer0 Thanks! I just merged it in 0.x branch. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] nifi pull request #401: NIFI-1832 Allowing expression language in properties...

Github user pvillard31 closed the pull request at: https://github.com/apache/nifi/pull/401 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is