[GitHub] nifi issue #2999: NIFI-5589 : Clarify PutMongo documentation

2018-09-12 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/2999 Thanks for helping with this @MikeThomsen, Our dev team spent a long time trying to understand exactly how to use the processor and so we hope these clarifications will save someone else

[GitHub] nifi issue #2999: NIFI-5589 : Clarify PutMongo documentation

2018-09-12 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/2999 @alopresto Thanks Andy :) nice to hear that changed, I always thought it was tedious to squash things. ---

[GitHub] nifi issue #2999: NIFI-5589 : Clarify PutMongo documentation

2018-09-12 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/2999 Thanks for submitting this documentation change. Can you please squash all 3 of your commits into 1? https://github.com/todotxt/todo.txt-android/wiki/Squash-All-Commits-Related

[GitHub] nifi issue #1800: NIFI-3681 - Controller Service for Processor Leader Electi...

2017-05-24 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1800 1) I'll look into taking the inner classes out but will need to look at how the permissions scopes are working between them first. 2) Will look into applying the KeeperException recommendation

[GitHub] nifi pull request #1800: NIFI-3681 - Controller Service for Processor Leader...

2017-05-15 Thread josephxsxn
GitHub user josephxsxn opened a pull request: https://github.com/apache/nifi/pull/1800 NIFI-3681 - Controller Service for Processor Leader Elections Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you

[GitHub] nifi issue #1796: NIFI-3894: Call Inflater/Deflater.end to free up memory

2017-05-15 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1796 Using today and is preventing the errors as expected. --- 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

[GitHub] nifi pull request #1583: NIFI-1131 renamed relationships

2017-05-14 Thread josephxsxn
Github user josephxsxn closed the pull request at: https://github.com/apache/nifi/pull/1583 --- 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

[GitHub] nifi issue #1583: NIFI-1131 renamed relationships

2017-05-14 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1583 Closed in light of Joes comments. --- 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 issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-10 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 Builds fine passed check-style. Tests pass. License headers exist. Tested on my custom workflow with success. Please rebase master from upstream and squash your 11 commits into 1

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-10 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 I think you just need a entry in your pom in the toolkit-assembly now and ull be all done :D Looks like it works well. Will test on some other clusters just to validate diversity

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-09 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 works great now on multiple differing flow.xml.gz's... I am thinking that perhaps we should include the min/max/avg flow files per queue as well just in case some users decides to set

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-08 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 Test fails when building Looks trivial see below. Also built it with skipTests anyway just to run it again, on 1 Cluster I am getting a null

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-04 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 ignore my java -cp // java jar comments.. Can you mimic what the other existing tools do here with .bin and .sh scripts ? https://github.com/apache/nifi/tree/master/nifi-toolkit

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-04 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 Also would it be possible to change the packaging so that it builds its in a 'java jar' manor so the admin doesnt have to go lookup the entire classname to run the utility? --- If your project

[GitHub] nifi issue #1747: [NIFI-3716] Flowfile analyzer tool created

2017-05-04 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1747 I went and built this, you have alot of checkstyle issues - [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:2.15:check (check-style) on project nifi

[GitHub] nifi pull request #1617: NIFI-3640 uri eventhub changes

2017-03-23 Thread josephxsxn
GitHub user josephxsxn opened a pull request: https://github.com/apache/nifi/pull/1617 NIFI-3640 uri eventhub changes Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the following steps

[GitHub] nifi issue #1583: NIFI-1131 renamed relationships

2017-03-10 Thread josephxsxn
Github user josephxsxn commented on the issue: https://github.com/apache/nifi/pull/1583 Trival change in names didnt impact tests. --- 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

[GitHub] nifi pull request #1583: NIFI-1131 renamed relationships

2017-03-10 Thread josephxsxn
GitHub user josephxsxn opened a pull request: https://github.com/apache/nifi/pull/1583 NIFI-1131 renamed relationships Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the following steps

[GitHub] nifi pull request #1556: NIFI-3547 Wait Processor should not WARN for expect...

2017-03-02 Thread josephxsxn
GitHub user josephxsxn opened a pull request: https://github.com/apache/nifi/pull/1556 NIFI-3547 Wait Processor should not WARN for expected behavior Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you