[GitHub] nifi issue #1201: NIFI-2890 Provenance Repository Corruption

2017-02-14 Thread jskora
Github user jskora commented on the issue: https://github.com/apache/nifi/pull/1201 Replaced by #1484. --- 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

[GitHub] nifi issue #1201: NIFI-2890 Provenance Repository Corruption

2017-01-06 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/1201 Hey @jskora, it appears you have check style issues. I'm not entirely sure how you pulled in the commits but are you able to rebase instead? This throws off how I normally squash/sign-off

[GitHub] nifi issue #1201: NIFI-2890 Provenance Repository Corruption

2017-01-06 Thread jskora
Github user jskora commented on the issue: https://github.com/apache/nifi/pull/1201 @JPercivall this has been updated to align with other changes in Master. I couldn't squash without creating a new branch, but a diff with Master only shows the PersistentProvenanceRepository and

[GitHub] nifi issue #1201: NIFI-2890 Provenance Repository Corruption

2017-01-03 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/1201 Hey @jskora, sorry this has sat for so long, this PR review should have been prioritized. That said, there appear to be merge conflicts and checkstyle issues. I could resolve them for you if you

[GitHub] nifi issue #1201: NIFI-2890 Provenance Repository Corruption

2017-01-03 Thread JPercivall
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/1201 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