GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/2890
NIFI-5427: Updating ScrollElasticsearchHttp to use POST, supporting ES6
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2133#discussion_r137839524
--- Diff:
nifi-commons/nifi-write-ahead-log/src/main/java/org/wali/MinimalLockingWriteAheadLog.java
---
@@ -474,8 +474,15 @@ private void recoverFromEdits
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1887
NIFI-4014: Correcting Event Type text in S2S provenance reporting task
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1872
If you think it's appropriate to include in this ticket, you could also
update the SiteToSiteStatusReportingTask to include the counters in the
serialized JSON.
---
If your project is set up
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1786
Salt is easy to set up with this
[walkthrough](https://docs.saltstack.com/en/latest/topics/tutorials/walkthrough.html).
You can run salt-master and salt-minion on the same nifi box if you want
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1786
I tried this out, and it does appear to work when I run ssh
user@remote-host "sudo service nifi restart". However, when I do the same with
a salt command, it still hangs:
salt ni
Github user gresockj closed the pull request at:
https://github.com/apache/nifi/pull/1671
---
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 user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1671
NIFI-3703: Adding 'Allow Anonymous Credentials' property to AWS processors
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1659#discussion_r110865211
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-canvas-utils.js
---
@@ -412,9 +412,9
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1659#discussion_r110516800
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-canvas-utils.js
---
@@ -412,9 +412,9
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1659#discussion_r110516478
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-canvas-utils.js
---
@@ -412,9 +412,9
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1660
NIFI-3674: Implementing SiteToSiteStatusReportingTask
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1592
NIFI-3582: Fixing PersistentMapCache bug that skipped persistent evictions
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1454
NIFI-3419: Routing flow files causing ZipException to failure in
MergeContent
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1398
NIFI-3275: Correcting SocketChannelSender log warning message
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1359
NIFI-3253: Correcting documentation in Notify processor
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1358
NIFI-3127: Fixing NPE for empty flow files in SplitText
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1329
I like the idea about waiting for N signals. I think it can be done by
adding a getKeys(Pattern) method to the distributed cache, so maybe it's best
captured in a separate ticket.
---
If your
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1329#discussion_r92813543
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/Notify.java
---
@@ -0,0 +1,191
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/1329
NIFI-190: Initial commit of Wait and Notify processors
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1317
This has been running for a day with lots of flow files and several
restarts, and I have not encountered the issue yet.
---
If your project is set up for it, you can reply to this email and have
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1317
It looks like it should fix the issue. I have deployed it to my cluster,
and I'll monitor it today and let you know tomorrow if I have anymore problems.
---
If your project is set up for it, you
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/1245
Hi @markap14 , thanks for submitting this patch. I tested it out on my
cluster and it does not appear to resolve the MergeContent problem in my case.
I'm hoping I deployed the fix correctly: I
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/
I tested this patch on a NiFi 1.0.0 instance and it resolves NIFI-2848!
Thanks Pierre.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/
Yes, I will take a look today
---
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
Github user gresockj closed the pull request at:
https://github.com/apache/nifi/pull/733
---
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 user gresockj commented on the issue:
https://github.com/apache/nifi/pull/733
Thanks for the help!
---
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
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/733#discussion_r80111838
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/733#discussion_r80111550
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/733#discussion_r79914319
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/733#discussion_r79913709
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/733
Thanks @mattyb149 ! Good comments, I'll see if I can work on these this
week.
---
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 user gresockj commented on the issue:
https://github.com/apache/nifi/pull/917
Thanks for checking that out, gives me some more confidence that it's
unrelated to this. For now I'll proceed with the ITListS3 tests when I get a
chance.
---
If your project is set up for it, you
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/917
Yes, it's requesting this:
https://localhost:8443/nifi-api/controller/process-groups/66ef7ae5-4bdb-4c50-9811-429be759f6fb/processors/7738f82e-d185-3931-a98e-c1156cd21cbc/state
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/917
Hmm, so this is strange. I was testing ListS3 out in NiFi today and I
noticed that I cannot see the state in the View State window. However, the
processor behaves as if the state is being persisted
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/917
NIFI-2631: Adding 'Commit Mode' and 'Use Versions' to ListS3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gresockj/nifi NIFI-2631-master
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/916
NIFI-2631: Adding 'Commit Mode' and 'Use Versions' to ListS3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gresockj/nifi NIFI-2631
Github user gresockj commented on the issue:
https://github.com/apache/nifi/pull/905
@mosermw Go ahead and squash away!
---
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
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/905#discussion_r75700388
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/UnpackContent.java
---
@@ -182,15
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/905#discussion_r75703219
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/UnpackContent.java
---
@@ -536,7
Github user gresockj commented on a diff in the pull request:
https://github.com/apache/nifi/pull/905#discussion_r75703161
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/test/java/org/apache/nifi/processors/standard/TestUnpackContent.java
GitHub user gresockj opened a pull request:
https://github.com/apache/nifi/pull/733
NIFI-2417: Implementing QueryElasticsearchHttp and ScrollElasticsearchHttp
I have implemented these processors for my own project, and thought it
might be useful to submit them to NiFi
42 matches
Mail list logo
