[jira] [Created] (NIFI-4023) WriteAheadProvenanceRepository indexing and query failure under high rate stress testing

2017-06-05 Thread Joseph Witt (JIRA)
Joseph Witt created NIFI-4023: - Summary: WriteAheadProvenanceRepository indexing and query failure under high rate stress testing Key: NIFI-4023 URL: https://issues.apache.org/jira/browse/NIFI-4023

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

2017-06-05 Thread Yolanda M. Davis (JIRA)
Yolanda M. Davis created NIFI-4022: -- Summary: Use SASL Auth Scheme For Secured Zookeeper Client Interaction Key: NIFI-4022 URL: https://issues.apache.org/jira/browse/NIFI-4022 Project: Apache NiFi

[jira] [Commented] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

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

[jira] [Updated] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

2017-06-05 Thread Andy LoPresto (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy LoPresto updated NIFI-4021: Resolution: Fixed Status: Resolved (was: Patch Available) > StandardFlowSynchronizerSpec

[GitHub] nifi issue #1892: NIFI-4021: Fix StandardFlowSynchronizerSpec to pass indepe...

2017-06-05 Thread alopresto
Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/1892 +1. As pointed out by @jtstorck , this fix resolves the immediate test issue, but there are still existing concerns with parallel test execution given shared access to the

[jira] [Commented] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

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

[jira] [Commented] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

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

[GitHub] nifi pull request #1892: NIFI-4021: Fix StandardFlowSynchronizerSpec to pass...

2017-06-05 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1892 --- 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-4021) StandardFlowSynchronizerSpec relies on other test

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

[GitHub] nifi issue #1892: NIFI-4021: Fix StandardFlowSynchronizerSpec to pass indepe...

2017-06-05 Thread alopresto
Github user alopresto commented on the issue: https://github.com/apache/nifi/pull/1892 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

[jira] [Updated] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

2017-06-05 Thread Koji Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-4021: Priority: Minor (was: Major) > StandardFlowSynchronizerSpec relies on other test >

[jira] [Updated] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

2017-06-05 Thread Koji Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-4021: Status: Patch Available (was: Open) > StandardFlowSynchronizerSpec relies on other test >

[jira] [Commented] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037992#comment-16037992 ] ASF GitHub Bot commented on NIFI-4021: -- GitHub user ijokarumawak opened a pull request:

[GitHub] nifi pull request #1892: NIFI-4021: Fix StandardFlowSynchronizerSpec to pass...

2017-06-05 Thread ijokarumawak
GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/1892 NIFI-4021: Fix StandardFlowSynchronizerSpec to pass independently. Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask

[jira] [Created] (NIFI-4021) StandardFlowSynchronizerSpec relies on other test

2017-06-05 Thread Koji Kawamura (JIRA)
Koji Kawamura created NIFI-4021: --- Summary: StandardFlowSynchronizerSpec relies on other test Key: NIFI-4021 URL: https://issues.apache.org/jira/browse/NIFI-4021 Project: Apache NiFi Issue

[jira] [Updated] (NIFI-3836) CryptoUtilsTest testShouldNotValidateUnreadableFileBasedKeyProvider test failure on Docker maven:latest

2017-06-05 Thread Andy LoPresto (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy LoPresto updated NIFI-3836: Resolution: Fixed Status: Resolved (was: Patch Available) > CryptoUtilsTest

[GitHub] nifi pull request #1865: NIFI-3836 Added check for root user in test that de...

2017-06-05 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1865 --- 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-3836) CryptoUtilsTest testShouldNotValidateUnreadableFileBasedKeyProvider test failure on Docker maven:latest

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

[jira] [Commented] (NIFI-3836) CryptoUtilsTest testShouldNotValidateUnreadableFileBasedKeyProvider test failure on Docker maven:latest

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

[jira] [Commented] (NIFI-3836) CryptoUtilsTest testShouldNotValidateUnreadableFileBasedKeyProvider test failure on Docker maven:latest

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037876#comment-16037876 ] ASF GitHub Bot commented on NIFI-3836: -- Github user jfrazee commented on the issue:

[GitHub] nifi issue #1865: NIFI-3836 Added check for root user in test that depends o...

2017-06-05 Thread jfrazee
Github user jfrazee commented on the issue: https://github.com/apache/nifi/pull/1865 @alopresto +1 will open another JIRA for covering the rest of the problems. --- 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] nifi-minifi-cpp pull request #107: MINIFI-262: Configuration listener

2017-06-05 Thread phrocker
Github user phrocker commented on a diff in the pull request: https://github.com/apache/nifi-minifi-cpp/pull/107#discussion_r120235144 --- Diff: libminifi/src/FlowController.cpp --- @@ -163,6 +174,31 @@ FlowController::~FlowController() { provenance_repo_ = nullptr; }

[GitHub] nifi-minifi-cpp pull request #107: MINIFI-262: Configuration listener

2017-06-05 Thread phrocker
Github user phrocker commented on a diff in the pull request: https://github.com/apache/nifi-minifi-cpp/pull/107#discussion_r120234911 --- Diff: libminifi/src/FlowController.cpp --- @@ -163,6 +174,31 @@ FlowController::~FlowController() { provenance_repo_ = nullptr; }

[GitHub] nifi-minifi-cpp pull request #107: MINIFI-262: Configuration listener

2017-06-05 Thread phrocker
Github user phrocker commented on a diff in the pull request: https://github.com/apache/nifi-minifi-cpp/pull/107#discussion_r120234097 --- Diff: libminifi/src/FlowController.cpp --- @@ -163,6 +174,31 @@ FlowController::~FlowController() { provenance_repo_ = nullptr; }

[GitHub] nifi-minifi-cpp pull request #107: MINIFI-262: Configuration listener

2017-06-05 Thread phrocker
Github user phrocker commented on a diff in the pull request: https://github.com/apache/nifi-minifi-cpp/pull/107#discussion_r120233311 --- Diff: libminifi/src/ConfigurationListener.cpp --- @@ -0,0 +1,130 @@ +/** + * + * Licensed to the Apache Software Foundation (ASF)

[GitHub] nifi-minifi-cpp pull request #107: MINIFI-262: Configuration listener

2017-06-05 Thread phrocker
Github user phrocker commented on a diff in the pull request: https://github.com/apache/nifi-minifi-cpp/pull/107#discussion_r120232599 --- Diff: libminifi/src/FlowController.cpp --- @@ -175,7 +211,7 @@ void FlowController::stop(bool force) { this->flow_file_repo_->stop();

[jira] [Created] (NIFI-4020) Consolidate HadoopValidators/HiveUtil property validators StandardValidators

2017-06-05 Thread Jeff Storck (JIRA)
Jeff Storck created NIFI-4020: - Summary: Consolidate HadoopValidators/HiveUtil property validators StandardValidators Key: NIFI-4020 URL: https://issues.apache.org/jira/browse/NIFI-4020 Project: Apache

[jira] [Created] (NIFI-4019) Add support for X-Forward-* headers

2017-06-05 Thread Jeff Storck (JIRA)
Jeff Storck created NIFI-4019: - Summary: Add support for X-Forward-* headers Key: NIFI-4019 URL: https://issues.apache.org/jira/browse/NIFI-4019 Project: Apache NiFi Issue Type: Improvement

[jira] [Commented] (NIFI-2923) Add expression language support to Kerberos parameters used by processors

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037654#comment-16037654 ] ASF GitHub Bot commented on NIFI-2923: -- Github user jtstorck commented on the issue:

[jira] [Commented] (NIFI-3998) Release Management for 0.7.4

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

[jira] [Commented] (NIFI-3998) Release Management for 0.7.4

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

[GitHub] nifi-minifi-cpp pull request #103: MINIFI-177 Incorporating Apache RAT to bu...

2017-06-05 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/103 --- 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

[jira] [Updated] (NIFI-4018) build from the source code , nifi ui can not work

2017-06-05 Thread shuguo zheng (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shuguo zheng updated NIFI-4018: --- Attachment: 2017-06-06_002943.png 2017-06-06_002916.png > build from the source code ,

[jira] [Created] (NIFI-4018) build from the source code , nifi ui can not work

2017-06-05 Thread shuguo zheng (JIRA)
shuguo zheng created NIFI-4018: -- Summary: build from the source code , nifi ui can not work Key: NIFI-4018 URL: https://issues.apache.org/jira/browse/NIFI-4018 Project: Apache NiFi Issue Type:

[GitHub] nifi-minifi-cpp issue #103: MINIFI-177 Incorporating Apache RAT to build wit...

2017-06-05 Thread brosander
Github user brosander commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/103 +1 LGTM --- 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-4014) Error in SiteToSiteProvenanceReportingTask event type description

2017-06-05 Thread Matt Gilman (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037142#comment-16037142 ] Matt Gilman commented on NIFI-4014: --- Removing fix version until there is review traction/close to merge.

[jira] [Updated] (NIFI-4014) Error in SiteToSiteProvenanceReportingTask event type description

2017-06-05 Thread Matt Gilman (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-4014: -- Fix Version/s: (was: 1.3.0) > Error in SiteToSiteProvenanceReportingTask event type description >

[GitHub] nifi-minifi-cpp issue #107: MINIFI-262: Configuration listener

2017-06-05 Thread benqiu2016
Github user benqiu2016 commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/107 @phrocker please review. --- 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

[jira] [Commented] (NIFI-4008) ConsumeKafkaRecord_0_10 assumes there is always one Record in a message

2017-06-05 Thread Joseph Witt (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037111#comment-16037111 ] Joseph Witt commented on NIFI-4008: --- [~ijokarumawak] i see where you're coming from on the logic of if it

[jira] [Updated] (NIFI-4008) ConsumeKafkaRecord_0_10 assumes there is always one Record in a message

2017-06-05 Thread Koji Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-4008: Status: Patch Available (was: Open) Thanks for the comments [~joewitt] [~markap14], I have

[jira] [Commented] (NIFI-4008) ConsumeKafkaRecord_0_10 assumes there is always one Record in a message

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036916#comment-16036916 ] ASF GitHub Bot commented on NIFI-4008: -- Github user ijokarumawak commented on the issue:

[GitHub] nifi issue #1891: NIFI-4008: Allow 0 or more records within a message.

2017-06-05 Thread ijokarumawak
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/1891 As @joewitt suggested on JIRA ticket, even if a message contains multiple records, the message probably should be treated as one. In order to do so, they will define a schema that has a compound

[jira] [Commented] (NIFI-4008) ConsumeKafkaRecord_0_10 assumes there is always one Record in a message

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036889#comment-16036889 ] ASF GitHub Bot commented on NIFI-4008: -- GitHub user ijokarumawak opened a pull request:

[GitHub] nifi pull request #1891: NIFI-4008: Allow 0 or more records within a message...

2017-06-05 Thread ijokarumawak
GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/1891 NIFI-4008: Allow 0 or more records within a message. Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to

[jira] [Assigned] (NIFI-4008) ConsumeKafkaRecord_0_10 assumes there is always one Record in a message

2017-06-05 Thread Koji Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura reassigned NIFI-4008: --- Assignee: Koji Kawamura > ConsumeKafkaRecord_0_10 assumes there is always one Record in a

[jira] [Updated] (NIFI-4017) Notify processor does not have any data provenance generated

2017-06-05 Thread Koji Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-4017: Status: Patch Available (was: Open) > Notify processor does not have any data provenance generated

[jira] [Commented] (NIFI-4017) Notify processor does not have any data provenance generated

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036733#comment-16036733 ] ASF GitHub Bot commented on NIFI-4017: -- GitHub user ijokarumawak opened a pull request:

[GitHub] nifi pull request #1890: NIFI-4017: Emit provenance event from Notify.

2017-06-05 Thread ijokarumawak
GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/1890 NIFI-4017: Emit provenance event from Notify. Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the

[jira] [Created] (NIFI-4017) Notify processor does not have any data provenance generated

2017-06-05 Thread Koji Kawamura (JIRA)
Koji Kawamura created NIFI-4017: --- Summary: Notify processor does not have any data provenance generated Key: NIFI-4017 URL: https://issues.apache.org/jira/browse/NIFI-4017 Project: Apache NiFi

[jira] [Commented] (NIFI-3696) Create File Manager & Config Migration Utilities

2017-06-05 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16036701#comment-16036701 ] ASF GitHub Bot commented on NIFI-3696: -- GitHub user YolandaMDavis opened a pull request:

[GitHub] nifi pull request #1889: NIFI-3696 - initial commit of ConfigMigration and F...

2017-06-05 Thread YolandaMDavis
GitHub user YolandaMDavis opened a pull request: https://github.com/apache/nifi/pull/1889 NIFI-3696 - initial commit of ConfigMigration and FileManager tools Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask

[jira] [Resolved] (NIFI-4000) Auto-Incremental For GetFTP processor

2017-06-05 Thread Koji Kawamura (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura resolved NIFI-4000. - Resolution: Not A Problem [~YANGFEIRAN] Yes, you are right. You can use StateManager to store