[jira] [Commented] (NIFI-4139) Refactor KeyProvider interface from provenance module to framework-level service

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115197#comment-16115197 ] ASF GitHub Bot commented on NIFI-4139: -- Github user alopresto commented on the issue:

[GitHub] nifi issue #2044: NIFI-4139 Extract key provider to framework-level service

2017-08-04 Thread alopresto
Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/2044 I also considered passing a supplier rather than the master key to the `KeyProviderFactory`, but the `EncryptedWriteAheadProvenanceRepository` already has access to the master key retrieval code,

[jira] [Commented] (NIFI-4139) Refactor KeyProvider interface from provenance module to framework-level service

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16115193#comment-16115193 ] ASF GitHub Bot commented on NIFI-4139: -- Github user alopresto commented on the issue:

[GitHub] nifi issue #2044: NIFI-4139 Extract key provider to framework-level service

2017-08-04 Thread alopresto
Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/2044 Thanks @mcgilman. I have moved the master key extraction out to `EncryptedWriteAheadProvenanceRepository` and removed the `nifi-security-utils` dependency on `nifi-properties-loader`. That module

[GitHub] nifi issue #2020: [NiFi-3973] Add PutKudu Processor for ingesting data to Ku...

2017-08-04 Thread cammachusa
Github user cammachusa commented on the issue: https://github.com/apache/nifi/pull/2020 Hi @rickysaltzer , switching to ConfigurationContext still doesn't work, all still null. As I noticed that none of Put/Getxxx processors (e.g. PutHBase, PutParquet, PutCassandra) uses OnEnable,

[jira] [Updated] (NIFI-3686) EOFException on swap in causes tight loop in polling for flowfiles

2017-08-04 Thread Michael Moser (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Moser updated NIFI-3686: Issue Type: Improvement (was: Bug) > EOFException on swap in causes tight loop in polling for

[jira] [Updated] (NIFI-3686) EOFException on swap in causes tight loop in polling for flowfiles

2017-08-04 Thread Michael Moser (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Moser updated NIFI-3686: Priority: Minor (was: Major) > EOFException on swap in causes tight loop in polling for flowfiles >

[jira] [Commented] (NIFI-4152) Create ListenTCPRecord Processor

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114973#comment-16114973 ] ASF GitHub Bot commented on NIFI-4152: -- Github user pvillard31 commented on the issue:

[GitHub] nifi issue #1987: NIFI-4152 Initial commit of ListenTCPRecord

2017-08-04 Thread pvillard31
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/1987 Hey @bbende, just built this PR and did some tests. The template I used is here: https://gist.github.com/pvillard31/5ecea5932bf70fc622e30be8512601b6 Then I send messages using

[jira] [Updated] (NIFI-4265) Build fails on clean git clone at in org.apache.nifi.processors.standard.TestGetFile

2017-08-04 Thread Martin Voigt (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Voigt updated NIFI-4265: --- Description: After a git clone from https://github.com/apache/nifi of the current project state, the

[jira] [Created] (NIFI-4265) Build fails on clean git clone at in org.apache.nifi.processors.standard.TestGetFile

2017-08-04 Thread Martin Voigt (JIRA)
Martin Voigt created NIFI-4265: -- Summary: Build fails on clean git clone at in org.apache.nifi.processors.standard.TestGetFile Key: NIFI-4265 URL: https://issues.apache.org/jira/browse/NIFI-4265

[GitHub] nifi issue #2020: [NiFi-3973] Add PutKudu Processor for ingesting data to Ku...

2017-08-04 Thread rickysaltzer
Github user rickysaltzer commented on the issue: https://github.com/apache/nifi/pull/2020 @cammachusa thanks! I think maybe you need to change the arguments given to your method once you use `OnEnabled`. I think it switches to `ConfigurationContext` instead of `ProcessContext` (or

[GitHub] nifi issue #2020: [NiFi-3973] Add PutKudu Processor for ingesting data to Ku...

2017-08-04 Thread cammachusa
Github user cammachusa commented on the issue: https://github.com/apache/nifi/pull/2020 sorry @rickysaltzer , I was rush, so didn't run the test when switch to onEnabled. Interestingly!, the OnEnabled is not being called, so objects defined in it are all null when running test cases.

[jira] [Resolved] (NIFI-4264) Implement PutHBaseRecord

2017-08-04 Thread Bryan Bende (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende resolved NIFI-4264. --- Resolution: Fixed > Implement PutHBaseRecord > > > Key:

[jira] [Created] (NIFI-4264) Implement PutHBaseRecord

2017-08-04 Thread Bryan Bende (JIRA)
Bryan Bende created NIFI-4264: - Summary: Implement PutHBaseRecord Key: NIFI-4264 URL: https://issues.apache.org/jira/browse/NIFI-4264 Project: Apache NiFi Issue Type: Improvement

[GitHub] nifi issue #1961: NIFI-4024 Added org.apache.nifi.hbase.PutHBaseRecord

2017-08-04 Thread bbende
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/1961 Merged to master, 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 wishes

[jira] [Commented] (NIFI-4024) Create EvaluateRecordPath processor

2017-08-04 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114822#comment-16114822 ] ASF subversion and git services commented on NIFI-4024: --- Commit

[GitHub] nifi pull request #1961: NIFI-4024 Added org.apache.nifi.hbase.PutHBaseRecor...

2017-08-04 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1961 --- 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

[jira] [Commented] (NIFI-4024) Create EvaluateRecordPath processor

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114824#comment-16114824 ] ASF GitHub Bot commented on NIFI-4024: -- Github user asfgit closed the pull request at:

[GitHub] nifi issue #2020: [NiFi-3973] Add PutKudu Processor for ingesting data to Ku...

2017-08-04 Thread rickysaltzer
Github user rickysaltzer commented on the issue: https://github.com/apache/nifi/pull/2020 @cammach @cammachusa Still seeing this error - what did you do to fix it? testSkipHeadLineTrue(org.apache.nifi.processors.kudu.TestPutKudu) Time elapsed: 0.001 sec

[GitHub] nifi issue #2046: NIFI-4022 - Enabled SASL auth scheme/ACL support for Curat...

2017-08-04 Thread YolandaMDavis
Github user YolandaMDavis commented on the issue: https://github.com/apache/nifi/pull/2046 @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 wishes so,

[jira] [Commented] (NIFI-4022) Use SASL Auth Scheme For Secured Zookeeper Client Interaction

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114792#comment-16114792 ] ASF GitHub Bot commented on NIFI-4022: -- Github user YolandaMDavis commented on the issue:

[jira] [Updated] (NIFI-4022) Use SASL Auth Scheme For Secured Zookeeper Client Interaction

2017-08-04 Thread Bryan Bende (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-4022: -- Fix Version/s: 1.4.0 > Use SASL Auth Scheme For Secured Zookeeper Client Interaction >

[jira] [Commented] (NIFI-4022) Use SASL Auth Scheme For Secured Zookeeper Client Interaction

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114763#comment-16114763 ] ASF GitHub Bot commented on NIFI-4022: -- Github user asfgit closed the pull request at:

[GitHub] nifi pull request #2046: NIFI-4022 - Enabled SASL auth scheme/ACL support fo...

2017-08-04 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2046 --- 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

[jira] [Commented] (NIFI-4022) Use SASL Auth Scheme For Secured Zookeeper Client Interaction

2017-08-04 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114761#comment-16114761 ] ASF subversion and git services commented on NIFI-4022: --- Commit

[GitHub] nifi issue #2046: NIFI-4022 - Enabled SASL auth scheme/ACL support for Curat...

2017-08-04 Thread bbende
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/2046 +1 Finally got my environment setup correctly and was able to verify the ACLs get created appropriately with this change, will merge to master, thanks! --- If your project is set up for it, you can

[jira] [Commented] (NIFI-4022) Use SASL Auth Scheme For Secured Zookeeper Client Interaction

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114755#comment-16114755 ] ASF GitHub Bot commented on NIFI-4022: -- Github user bbende commented on the issue:

[GitHub] nifi issue #2020: [NiFi-3973] Add PutKudu Processor for ingesting data to Ku...

2017-08-04 Thread rickysaltzer
Github user rickysaltzer commented on the issue: https://github.com/apache/nifi/pull/2020 I've got your changes locally to do some testing, 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

[jira] [Created] (NIFI-4263) Schema validation error parsing Flow Configuration, Back Pressure Data Size Threshold value

2017-08-04 Thread Wynner (JIRA)
Wynner created NIFI-4263: Summary: Schema validation error parsing Flow Configuration, Back Pressure Data Size Threshold value Key: NIFI-4263 URL: https://issues.apache.org/jira/browse/NIFI-4263 Project:

[jira] [Updated] (NIFI-2167) Disabled state not including in a Processor that was copy/paste

2017-08-04 Thread Pierre Villard (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-2167: - Assignee: Pierre Villard Status: Patch Available (was: Open) > Disabled state not including

[jira] [Commented] (NIFI-2167) Disabled state not including in a Processor that was copy/paste

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114460#comment-16114460 ] ASF GitHub Bot commented on NIFI-2167: -- GitHub user pvillard31 opened a pull request:

[GitHub] nifi pull request #2057: NIFI-2167 - include disabled state for processors w...

2017-08-04 Thread pvillard31
GitHub user pvillard31 opened a pull request: https://github.com/apache/nifi/pull/2057 NIFI-2167 - include disabled state for processors when copy/paste/templates Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution

[jira] [Updated] (NIFI-4051) QueryRecord uses a different Lexical policy for validation than it does for running

2017-08-04 Thread Pierre Villard (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4051: - Resolution: Fixed Status: Resolved (was: Patch Available) > QueryRecord uses a different

[jira] [Commented] (NIFI-4051) QueryRecord uses a different Lexical policy for validation than it does for running

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114440#comment-16114440 ] ASF GitHub Bot commented on NIFI-4051: -- Github user asfgit closed the pull request at:

[jira] [Commented] (NIFI-4051) QueryRecord uses a different Lexical policy for validation than it does for running

2017-08-04 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114438#comment-16114438 ] ASF subversion and git services commented on NIFI-4051: --- Commit

[GitHub] nifi pull request #2054: NIFI-4051: Ensure that we use the appropriate Lexic...

2017-08-04 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2054 --- 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

[jira] [Commented] (NIFI-4139) Refactor KeyProvider interface from provenance module to framework-level service

2017-08-04 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114401#comment-16114401 ] ASF GitHub Bot commented on NIFI-4139: -- Github user mcgilman commented on the issue:

[GitHub] nifi issue #2044: NIFI-4139 Extract key provider to framework-level service

2017-08-04 Thread mcgilman
Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/2044 @alopresto These refactorings look good. The backward compatibility support for legacy configurations is also solid. One minor thing I'd like to investigate further if we can remove the dependency