[GitHub] nifi issue #3033: NIFI-5629 GetFile vast listing performance

2018-12-10 Thread adyoun2
Github user adyoun2 commented on the issue: https://github.com/apache/nifi/pull/3033 Could someone take a look at this? Cheers ---

[GitHub] nifi issue #3033: NIFI-5629 GetFile vast listing performance

2018-10-16 Thread adyoun2
Github user adyoun2 commented on the issue: https://github.com/apache/nifi/pull/3033 Backed out the squashed commit ---

[GitHub] nifi issue #3033: NIFI-5629 GetFile vast listing performance

2018-10-16 Thread adyoun2
Github user adyoun2 commented on the issue: https://github.com/apache/nifi/pull/3033 Doh. How do I resolve the situation now, can I just back out the squashed commit? ---

[GitHub] nifi issue #3033: NIFI-5629 GetFile vast listing performance

2018-10-16 Thread patricker
Github user patricker commented on the issue: https://github.com/apache/nifi/pull/3033 @adyoun2 Looks like you are having some issues with your Git, I've been there many times... But I'm sure we can get it working. Make sure that after you rebase your Github fork you push the

[GitHub] nifi issue #3033: NIFI-5629 GetFile vast listing performance

2018-10-12 Thread patricker
Github user patricker commented on the issue: https://github.com/apache/nifi/pull/3033 @adyoun2 Also, to retrigger the build, I found online that you can close and re-open your PR (no need for a new PR, just re-open). That _should_ re-trigger the checks. ---

[GitHub] nifi issue #3033: NIFI-5629 GetFile vast listing performance

2018-09-27 Thread adyoun2
Github user adyoun2 commented on the issue: https://github.com/apache/nifi/pull/3033 How do I trigger a re-build without dummy commits? The build failure appears to be a timeout unrelated to the changes. ---