[jira] [Commented] (MINIFICPP-290) ExtractText cannot be instantiated
[ https://issues.apache.org/jira/browse/MINIFICPP-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238706#comment-16238706 ] ASF GitHub Bot commented on MINIFICPP-290: -- GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/177 MINIFICPP-290 Add ExtractText to FlowConfiguration.h so that it can b… …e recognized in flow configurations Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] If applicable, have you updated the LICENSE file? - [x] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-290 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/177.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #177 commit 0f8b78b6c512915dcb42dfdfd612f51fdf179716 Author: Andrew I. Christianson Date: 2017-11-04T02:06:20Z MINIFICPP-290 Add ExtractText to FlowConfiguration.h so that it can be recognized in flow configurations > ExtractText cannot be instantiated > -- > > Key: MINIFICPP-290 > URL: https://issues.apache.org/jira/browse/MINIFICPP-290 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Blocker > > MiNiFi - C++ does not recognize ExtractText in flow configurations because > it's not in FlowConfiguration.h. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #177: MINIFICPP-290 Add ExtractText to FlowConf...
GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/177 MINIFICPP-290 Add ExtractText to FlowConfiguration.h so that it can b⦠â¦e recognized in flow configurations Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] If applicable, have you updated the LICENSE file? - [x] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-290 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/177.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #177 commit 0f8b78b6c512915dcb42dfdfd612f51fdf179716 Author: Andrew I. Christianson Date: 2017-11-04T02:06:20Z MINIFICPP-290 Add ExtractText to FlowConfiguration.h so that it can be recognized in flow configurations ---
[jira] [Created] (MINIFICPP-290) ExtractText cannot be instantiated
Andrew Christianson created MINIFICPP-290: - Summary: ExtractText cannot be instantiated Key: MINIFICPP-290 URL: https://issues.apache.org/jira/browse/MINIFICPP-290 Project: NiFi MiNiFi C++ Issue Type: Bug Reporter: Andrew Christianson Assignee: Andrew Christianson Priority: Blocker MiNiFi - C++ does not recognize ExtractText in flow configurations because it's not in FlowConfiguration.h. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-289) Support PutFile property: Create Missing Directories
[ https://issues.apache.org/jira/browse/MINIFICPP-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238656#comment-16238656 ] ASF GitHub Bot commented on MINIFICPP-289: -- GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/176 MINIFICPP-289 Support PutFile property: Create Missing Directories Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] If applicable, have you updated the LICENSE file? - [x] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-289 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/176.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #176 commit e75ce3d7997803bd0499f2fada6b8614bf332a03 Author: Andrew I. Christianson Date: 2017-11-04T00:51:17Z MINIFICPP-289 Support PutFile property: Create Missing Directories > Support PutFile property: Create Missing Directories > - > > Key: MINIFICPP-289 > URL: https://issues.apache.org/jira/browse/MINIFICPP-289 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Normal > > Creating missing directories when a file is put is particularly important > when using generated file names. This should be supported in MiNiFi - C++. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #176: MINIFICPP-289 Support PutFile property: C...
GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/176 MINIFICPP-289 Support PutFile property: Create Missing Directories Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] If applicable, have you updated the LICENSE file? - [x] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-289 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/176.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #176 commit e75ce3d7997803bd0499f2fada6b8614bf332a03 Author: Andrew I. Christianson Date: 2017-11-04T00:51:17Z MINIFICPP-289 Support PutFile property: Create Missing Directories ---
[jira] [Created] (MINIFICPP-289) Support PutFile property: Create Missing Directories
Andrew Christianson created MINIFICPP-289: - Summary: Support PutFile property: Create Missing Directories Key: MINIFICPP-289 URL: https://issues.apache.org/jira/browse/MINIFICPP-289 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: Andrew Christianson Assignee: Andrew Christianson Priority: Normal Creating missing directories when a file is put is particularly important when using generated file names. This should be supported in MiNiFi - C++. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4568) Working Dir Property not shown nor mentioned in ExecuteProcess Processor
[ https://issues.apache.org/jira/browse/NIFI-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238583#comment-16238583 ] ASF GitHub Bot commented on NIFI-4568: -- GitHub user jugi92 opened a pull request: https://github.com/apache/nifi/pull/2250 NIFI-4568 Added existing but missing property WORKING_DIR Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [X] Does your PR title start with NIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [X] Has your PR been rebased against the latest commit within the target branch (typically master)? - [X] Is your initial contribution a single, squashed commit? ### For code changes: - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder? - [ ] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jugi92/nifi nifi-4568 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/2250.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2250 commit a69faef5ed9ea5412c49a7f1578f85b1f085b86b Author: Julian Gimbel Date: 2017-11-03T23:20:04Z NIFI-4568 Added existing but missing property WORKING_DIR > Working Dir Property not shown nor mentioned in ExecuteProcess Processor > > > Key: NIFI-4568 > URL: https://issues.apache.org/jira/browse/NIFI-4568 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration, Configuration Management >Affects Versions: 1.3.0, 1.4.0 >Reporter: Julian Gimbel > Labels: executeProcess, processor, properties > > When executing a process with the executeProcess Operator the default working > directory is the home directory of the user that started Nifi. In the code > there is a Working directory Property that seems to work if one adds it. The > documentation does not mention that it reads that argument and it is not > shown in the Properties of the Operator. > It should either be added in the documentation of the operator or directly in > the Properties with home directory as the default value. > See Line 100 to 110 in > [https://github.com/apache/nifi/blob/6279fd41844205a14cf1f2fb225ead8881b197eb/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteProcess.java] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi pull request #2250: NIFI-4568 Added existing but missing property WORKI...
GitHub user jugi92 opened a pull request: https://github.com/apache/nifi/pull/2250 NIFI-4568 Added existing but missing property WORKING_DIR Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [X] Does your PR title start with NIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [X] Has your PR been rebased against the latest commit within the target branch (typically master)? - [X] Is your initial contribution a single, squashed commit? ### For code changes: - [X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder? - [ ] Have you written or updated unit tests to verify your changes? - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jugi92/nifi nifi-4568 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/2250.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2250 commit a69faef5ed9ea5412c49a7f1578f85b1f085b86b Author: Julian Gimbel Date: 2017-11-03T23:20:04Z NIFI-4568 Added existing but missing property WORKING_DIR ---
[jira] [Commented] (MINIFICPP-253) ContentRepository should remove items from count_map_.
[ https://issues.apache.org/jira/browse/MINIFICPP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238529#comment-16238529 ] ASF GitHub Bot commented on MINIFICPP-253: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/175 > ContentRepository should remove items from count_map_. > --- > > Key: MINIFICPP-253 > URL: https://issues.apache.org/jira/browse/MINIFICPP-253 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: marco polo >Priority: Major > > removeIfOrphaned in ContentRepository should remove the key/value pair from > count_map_. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #175: MINIFICPP-253: prune claim map when a rem...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/175 ---
[jira] [Commented] (NIFI-4550) Add an InferCharacterSet processor
[ https://issues.apache.org/jira/browse/NIFI-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238500#comment-16238500 ] Matt Burgess commented on NIFI-4550: Yes it seems like we could kill both birds under 1874, although I’d recommend a (possibly optional) separate attribute for character set, to avoid needing to parse the mime.type to find it. > Add an InferCharacterSet processor > -- > > Key: NIFI-4550 > URL: https://issues.apache.org/jira/browse/NIFI-4550 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Burgess >Priority: Minor > > Sometimes in a NiFi flow it is not known what character set an incoming flow > file is using. This can make it difficult for downstream processing if the > processors expect a particular charset (whether the user can configure it or > not). There is a ConvertCharacterSet processor, but it expects an explicit > value for Input Character Set, when this might not be known. > I propose an InferCharacterSet processor, which would presumably use some > license-friendly third-party library (there is a discussion > [here|https://stackoverflow.com/questions/499010/java-how-to-determine-the-correct-charset-encoding-of-a-stream]) > to guess the character set, perhaps adding it as an attribute for use > downstream in ConvertCharacterSet. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4550) Add an InferCharacterSet processor
[ https://issues.apache.org/jira/browse/NIFI-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238451#comment-16238451 ] Michael Moser commented on NIFI-4550: - Perhaps somewhat related to NIFI-1874? > Add an InferCharacterSet processor > -- > > Key: NIFI-4550 > URL: https://issues.apache.org/jira/browse/NIFI-4550 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Burgess >Priority: Minor > > Sometimes in a NiFi flow it is not known what character set an incoming flow > file is using. This can make it difficult for downstream processing if the > processors expect a particular charset (whether the user can configure it or > not). There is a ConvertCharacterSet processor, but it expects an explicit > value for Input Character Set, when this might not be known. > I propose an InferCharacterSet processor, which would presumably use some > license-friendly third-party library (there is a discussion > [here|https://stackoverflow.com/questions/499010/java-how-to-determine-the-correct-charset-encoding-of-a-stream]) > to guess the character set, perhaps adding it as an attribute for use > downstream in ConvertCharacterSet. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-registry issue #33: NIFIREG-47 Improvements to nifi-registry-client
Github user bbende commented on the issue: https://github.com/apache/nifi-registry/pull/33 Not sure why one travis job failed, all tests passing for me locally ---
[jira] [Commented] (NIFIREG-47) Add ability to specify proxied user in nifi-registry-client
[ https://issues.apache.org/jira/browse/NIFIREG-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238339#comment-16238339 ] ASF GitHub Bot commented on NIFIREG-47: --- Github user bbende commented on the issue: https://github.com/apache/nifi-registry/pull/33 Not sure why one travis job failed, all tests passing for me locally > Add ability to specify proxied user in nifi-registry-client > --- > > Key: NIFIREG-47 > URL: https://issues.apache.org/jira/browse/NIFIREG-47 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende > > We need to be able to specify an optional proxied user per operation in the > nifi-registry-client. > For example, NiFi will make a call using the server certificate, but wants to > retrieve all of the buckets on behalf of an end user in NiFi. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (NIFIREG-48) Add module for performing a 'diff' of two versioned flows
[ https://issues.apache.org/jira/browse/NIFIREG-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende resolved NIFIREG-48. Resolution: Fixed Fix Version/s: 0.0.1 > Add module for performing a 'diff' of two versioned flows > - > > Key: NIFIREG-48 > URL: https://issues.apache.org/jira/browse/NIFIREG-48 > Project: NiFi Registry > Issue Type: New Feature >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > Fix For: 0.0.1 > > > Given two versions of a Versioned Flow, we need to create a 'diff' of the > main Versioned Process Group so that we know what changed between the two > versions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFIREG-48) Add module for performing a 'diff' of two versioned flows
[ https://issues.apache.org/jira/browse/NIFIREG-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238305#comment-16238305 ] ASF GitHub Bot commented on NIFIREG-48: --- Github user asfgit closed the pull request at: https://github.com/apache/nifi-registry/pull/31 > Add module for performing a 'diff' of two versioned flows > - > > Key: NIFIREG-48 > URL: https://issues.apache.org/jira/browse/NIFIREG-48 > Project: NiFi Registry > Issue Type: New Feature >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > > Given two versions of a Versioned Flow, we need to create a 'diff' of the > main Versioned Process Group so that we know what changed between the two > versions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-registry pull request #31: NIFIREG-48: Added new nifi-registry-flow-dif...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-registry/pull/31 ---
[jira] [Commented] (NIFIREG-48) Add module for performing a 'diff' of two versioned flows
[ https://issues.apache.org/jira/browse/NIFIREG-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238302#comment-16238302 ] ASF GitHub Bot commented on NIFIREG-48: --- Github user bbende commented on the issue: https://github.com/apache/nifi-registry/pull/31 +1 Looks good, will merge to master > Add module for performing a 'diff' of two versioned flows > - > > Key: NIFIREG-48 > URL: https://issues.apache.org/jira/browse/NIFIREG-48 > Project: NiFi Registry > Issue Type: New Feature >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > > Given two versions of a Versioned Flow, we need to create a 'diff' of the > main Versioned Process Group so that we know what changed between the two > versions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-registry issue #31: NIFIREG-48: Added new nifi-registry-flow-diff modul...
Github user bbende commented on the issue: https://github.com/apache/nifi-registry/pull/31 +1 Looks good, will merge to master ---
[jira] [Commented] (NIFIREG-47) Add ability to specify proxied user in nifi-registry-client
[ https://issues.apache.org/jira/browse/NIFIREG-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238267#comment-16238267 ] ASF GitHub Bot commented on NIFIREG-47: --- GitHub user bbende opened a pull request: https://github.com/apache/nifi-registry/pull/33 NIFIREG-47 Improvements to nifi-registry-cleitn - Using separate Jersey version for client only - Added support for proxied entities - Fixed deserializing of BucketItems - Cleaned up methods with unnecessary parameters You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbende/nifi-registry NIFIREG-47 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/33.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #33 commit ac33e6910815ba54e1d40fc15ea650d9f34259d7 Author: Bryan Bende Date: 2017-11-02T19:05:30Z NIFIREG-47 Improvements to nifi-registry-cleitn - Using separate Jersey version for client only - Added support for proxied entities - Fixed deserializing of BucketItems - Cleaned up methods with unnecessary parameters > Add ability to specify proxied user in nifi-registry-client > --- > > Key: NIFIREG-47 > URL: https://issues.apache.org/jira/browse/NIFIREG-47 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende > > We need to be able to specify an optional proxied user per operation in the > nifi-registry-client. > For example, NiFi will make a call using the server certificate, but wants to > retrieve all of the buckets on behalf of an end user in NiFi. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-registry pull request #33: NIFIREG-47 Improvements to nifi-registry-cle...
GitHub user bbende opened a pull request: https://github.com/apache/nifi-registry/pull/33 NIFIREG-47 Improvements to nifi-registry-cleitn - Using separate Jersey version for client only - Added support for proxied entities - Fixed deserializing of BucketItems - Cleaned up methods with unnecessary parameters You can merge this pull request into a Git repository by running: $ git pull https://github.com/bbende/nifi-registry NIFIREG-47 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/33.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #33 commit ac33e6910815ba54e1d40fc15ea650d9f34259d7 Author: Bryan Bende Date: 2017-11-02T19:05:30Z NIFIREG-47 Improvements to nifi-registry-cleitn - Using separate Jersey version for client only - Added support for proxied entities - Fixed deserializing of BucketItems - Cleaned up methods with unnecessary parameters ---
[jira] [Commented] (NIFIREG-40) Create UI coasters for notifications
[ https://issues.apache.org/jira/browse/NIFIREG-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238225#comment-16238225 ] ASF GitHub Bot commented on NIFIREG-40: --- GitHub user scottyaslan opened a pull request: https://github.com/apache/nifi-registry/pull/32 [NIFIREG-40] Add coasters for notifications to the FDS NgModule. Also… … upgraded to latest compatible versions of angular, angular material, covalent, and their dependencies You can merge this pull request into a Git repository by running: $ git pull https://github.com/scottyaslan/nifi-registry coasters Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/32.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #32 commit ac6299e4b203621518bdcc640e679ae95f9cc611 Author: Scott Aslan Date: 2017-11-03T19:16:52Z [NIFIREG-40] Add coasters for notifications to the FDS NgModule. Also upgraded to latest compatible versions of angular, angular material, covalent, and their dependencies > Create UI coasters for notifications > > > Key: NIFIREG-40 > URL: https://issues.apache.org/jira/browse/NIFIREG-40 > Project: NiFi Registry > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-registry pull request #32: [NIFIREG-40] Add coasters for notifications ...
GitHub user scottyaslan opened a pull request: https://github.com/apache/nifi-registry/pull/32 [NIFIREG-40] Add coasters for notifications to the FDS NgModule. Also⦠⦠upgraded to latest compatible versions of angular, angular material, covalent, and their dependencies You can merge this pull request into a Git repository by running: $ git pull https://github.com/scottyaslan/nifi-registry coasters Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/32.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #32 commit ac6299e4b203621518bdcc640e679ae95f9cc611 Author: Scott Aslan Date: 2017-11-03T19:16:52Z [NIFIREG-40] Add coasters for notifications to the FDS NgModule. Also upgraded to latest compatible versions of angular, angular material, covalent, and their dependencies ---
[jira] [Created] (MINIFICPP-288) Push flowfiles directly to a processor once persisted to avoid relying on spills to enforce state transition
marco polo created MINIFICPP-288: Summary: Push flowfiles directly to a processor once persisted to avoid relying on spills to enforce state transition Key: MINIFICPP-288 URL: https://issues.apache.org/jira/browse/MINIFICPP-288 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: marco polo Priority: Major Currently we may rely on multiple threads that ultimately rely on state transition through the repositories; however, we may be able to avoid this and do some of the work serially. This should be detectable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-253) ContentRepository should remove items from count_map_.
[ https://issues.apache.org/jira/browse/MINIFICPP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238174#comment-16238174 ] ASF GitHub Bot commented on MINIFICPP-253: -- GitHub user phrocker opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/175 MINIFICPP-253: prune claim map when a removal occurs MINIFICPP-253: use find for the stream count to avoid arbitrarily inflating the map Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFICPP-253 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/175.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #175 commit 6efcb39f43b137ac7d0375fd61ed87653f063a22 Author: Marc Parisi Date: 2017-11-03T18:45:48Z MINIFICPP-253: prune claim map when a removal occurs MINIFICPP-253: use find for the stream count to avoid arbitrarily inflating the map > ContentRepository should remove items from count_map_. > --- > > Key: MINIFICPP-253 > URL: https://issues.apache.org/jira/browse/MINIFICPP-253 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: marco polo >Priority: Major > > removeIfOrphaned in ContentRepository should remove the key/value pair from > count_map_. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #175: MINIFICPP-253: prune claim map when a rem...
GitHub user phrocker opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/175 MINIFICPP-253: prune claim map when a removal occurs MINIFICPP-253: use find for the stream count to avoid arbitrarily inflating the map Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFICPP-253 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/175.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #175 commit 6efcb39f43b137ac7d0375fd61ed87653f063a22 Author: Marc Parisi Date: 2017-11-03T18:45:48Z MINIFICPP-253: prune claim map when a removal occurs MINIFICPP-253: use find for the stream count to avoid arbitrarily inflating the map ---
[jira] [Updated] (NIFI-4459) Confluent Schema Registry - not tolerant to error in single Subject
[
https://issues.apache.org/jira/browse/NIFI-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-4459:
-
Fix Version/s: 1.5.0
Status: Patch Available (was: Open)
> Confluent Schema Registry - not tolerant to error in single Subject
> ---
>
> Key: NIFI-4459
> URL: https://issues.apache.org/jira/browse/NIFI-4459
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.4.0
>Reporter: Dave Torok
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.5.0
>
>
> Getting Could not find Schema with id 12345 from the Confluent Schema
> Registry.
> Root cause:
> 1. RestSchemaRegistryClient.java - gets all subjects from the registry
> {noformat}https://{registry}/subjects{noformat}
> 2. Iterates through the subjects to get schema IDs (getSchema method line
> 113-126)
> {noformat}https://{registry}/subjects/{subjectname}/ids/latest{noformat}
> 3. If ANY subject in the list of subjects has an error / resource not
> found, lookup FAILS, even if the subject with the matching ID is anywhere in
> the list of subjects.
> Proposed Fix:
> Tolerate individual subject calls that return errors (NOT_FOUND status).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINIFICPP-286) PutFile fails if filename property includes a path
[
https://issues.apache.org/jira/browse/MINIFICPP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238111#comment-16238111
]
ASF GitHub Bot commented on MINIFICPP-286:
--
Github user asfgit closed the pull request at:
https://github.com/apache/nifi-minifi-cpp/pull/174
> PutFile fails if filename property includes a path
> --
>
> Key: MINIFICPP-286
> URL: https://issues.apache.org/jira/browse/MINIFICPP-286
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If a flowfile 'filename' property includes a path (i.e. nested subdirs), then
> PutFile fails due to improper creation of temporary write file.
> Example ExecuteScript lua to update filename:
> {code}
> function onTrigger(context, session)
> flow_file = session:get()
> log:info('rename_file triggered')
> if flow_file ~= nil then
> file_name = flow_file:getAttribute('filename')
> new_file_name = 'a/b/' .. file_name
> log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' ..
> new_file_name)
> flow_file:updateAttribute('filename', new_file_name)
> session:transfer(flow_file, REL_SUCCESS)
> log:info('rename_file success')
> else
> log:info('no work to do')
> end
> end
> {code}
> Log output showing the error:
> {code}
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available
> lua script engine instance
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> triggered
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming
> 1509727478135549592 to a/b/1509727478135549592
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> success
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua
> script engine
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile using temporary file
> data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile writing file a/b/1509727478135549592 into directory data
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] Committing data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> committing put file operation to data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> commit put file operation to data/a/b/1509727478135549592 failed because
> rename() call failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #174: MINIFICPP-286 Correctly handle filenames ...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/174 ---
[jira] [Created] (MINIFICPP-287) Add ability go log more than one flowfile in LogAttribute
marco polo created MINIFICPP-287: Summary: Add ability go log more than one flowfile in LogAttribute Key: MINIFICPP-287 URL: https://issues.apache.org/jira/browse/MINIFICPP-287 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: marco polo Assignee: marco polo This feature has been helpful to find numerous bugs based on threading/pressure, so I'm providing it as an improvement. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFIREG-48) Add module for performing a 'diff' of two versioned flows
[ https://issues.apache.org/jira/browse/NIFIREG-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238084#comment-16238084 ] ASF GitHub Bot commented on NIFIREG-48: --- GitHub user markap14 opened a pull request: https://github.com/apache/nifi-registry/pull/31 NIFIREG-48: Added new nifi-registry-flow-diff module and updates to d… …ata model to accomodate what NiFi needs for integration. You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi-registry NIFIREG-48 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/31.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #31 commit 58b568783461d56464c421844ca5f167ccb95507 Author: Mark Payne Date: 2017-08-23T15:07:23Z NIFIREG-48: Added new nifi-registry-flow-diff module and updates to data model to accomodate what NiFi needs for integration. > Add module for performing a 'diff' of two versioned flows > - > > Key: NIFIREG-48 > URL: https://issues.apache.org/jira/browse/NIFIREG-48 > Project: NiFi Registry > Issue Type: New Feature >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Critical > > Given two versions of a Versioned Flow, we need to create a 'diff' of the > main Versioned Process Group so that we know what changed between the two > versions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-registry pull request #31: NIFIREG-48: Added new nifi-registry-flow-dif...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi-registry/pull/31 NIFIREG-48: Added new nifi-registry-flow-diff module and updates to d⦠â¦ata model to accomodate what NiFi needs for integration. You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi-registry NIFIREG-48 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-registry/pull/31.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #31 commit 58b568783461d56464c421844ca5f167ccb95507 Author: Mark Payne Date: 2017-08-23T15:07:23Z NIFIREG-48: Added new nifi-registry-flow-diff module and updates to data model to accomodate what NiFi needs for integration. ---
[jira] [Commented] (MINIFICPP-282) Improve test build speed and add Travis build cache
[ https://issues.apache.org/jira/browse/MINIFICPP-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238073#comment-16238073 ] ASF GitHub Bot commented on MINIFICPP-282: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/169 > Improve test build speed and add Travis build cache > --- > > Key: MINIFICPP-282 > URL: https://issues.apache.org/jira/browse/MINIFICPP-282 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Caleb Johnson >Priority: Minor > > * Use Travis's caching feature to persist $HOME/.ccache > * Enable parallel testing on Travis now that MINIFICPP-60 is merged > * Build catch main() and spdlib as shared objects for all tests > * Best practices according to [catch > docs|https://github.com/philsquared/Catch/blob/master/docs/slow-compiles.md]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4568) Working Dir Property not shown nor mentioned in ExecuteProcess Processor
[
https://issues.apache.org/jira/browse/NIFI-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238071#comment-16238071
]
Pierre Villard commented on NIFI-4568:
--
Hi [~jugi],
Good catch, it seems we just need to add:
{noformat}
properties.add(WORKING_DIR);
{noformat}
Do you want to submit a PR for that?
> Working Dir Property not shown nor mentioned in ExecuteProcess Processor
>
>
> Key: NIFI-4568
> URL: https://issues.apache.org/jira/browse/NIFI-4568
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Configuration Management
>Affects Versions: 1.3.0, 1.4.0
>Reporter: Julian Gimbel
> Labels: executeProcess, processor, properties
>
> When executing a process with the executeProcess Operator the default working
> directory is the home directory of the user that started Nifi. In the code
> there is a Working directory Property that seems to work if one adds it. The
> documentation does not mention that it reads that argument and it is not
> shown in the Properties of the Operator.
> It should either be added in the documentation of the operator or directly in
> the Properties with home directory as the default value.
> See Line 100 to 110 in
> [https://github.com/apache/nifi/blob/6279fd41844205a14cf1f2fb225ead8881b197eb/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteProcess.java]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #169: MINIFICPP-282 Improve test build speed, a...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/169 ---
[jira] [Created] (NIFIREG-48) Add module for performing a 'diff' of two versioned flows
Mark Payne created NIFIREG-48: - Summary: Add module for performing a 'diff' of two versioned flows Key: NIFIREG-48 URL: https://issues.apache.org/jira/browse/NIFIREG-48 Project: NiFi Registry Issue Type: New Feature Reporter: Mark Payne Assignee: Mark Payne Priority: Critical Given two versions of a Versioned Flow, we need to create a 'diff' of the main Versioned Process Group so that we know what changed between the two versions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-286) PutFile fails if filename property includes a path
[
https://issues.apache.org/jira/browse/MINIFICPP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238068#comment-16238068
]
ASF GitHub Bot commented on MINIFICPP-286:
--
Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/174#discussion_r148851261
--- Diff: libminifi/src/processors/PutFile.cpp ---
@@ -127,7 +131,33 @@ void PutFile::onTrigger(core::ProcessContext *context,
core::ProcessSession *ses
}
}
-bool PutFile::putFile(core::ProcessSession *session,
std::shared_ptr flowFile, const std::string &tmpFile, const
std::string &destFile) {
+std::string PutFile::tmpWritePath(const std::string &filename) const {
--- End diff --
thanks for breaking this out. much cleaner.
> PutFile fails if filename property includes a path
> --
>
> Key: MINIFICPP-286
> URL: https://issues.apache.org/jira/browse/MINIFICPP-286
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If a flowfile 'filename' property includes a path (i.e. nested subdirs), then
> PutFile fails due to improper creation of temporary write file.
> Example ExecuteScript lua to update filename:
> {code}
> function onTrigger(context, session)
> flow_file = session:get()
> log:info('rename_file triggered')
> if flow_file ~= nil then
> file_name = flow_file:getAttribute('filename')
> new_file_name = 'a/b/' .. file_name
> log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' ..
> new_file_name)
> flow_file:updateAttribute('filename', new_file_name)
> session:transfer(flow_file, REL_SUCCESS)
> log:info('rename_file success')
> else
> log:info('no work to do')
> end
> end
> {code}
> Log output showing the error:
> {code}
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available
> lua script engine instance
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> triggered
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming
> 1509727478135549592 to a/b/1509727478135549592
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> success
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua
> script engine
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile using temporary file
> data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile writing file a/b/1509727478135549592 into directory data
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] Committing data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> committing put file operation to data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> commit put file operation to data/a/b/1509727478135549592 failed because
> rename() call failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (NIFI-4568) Working Dir Property not shown nor mentioned in ExecuteProcess Processor
[ https://issues.apache.org/jira/browse/NIFI-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Gimbel updated NIFI-4568: Component/s: Configuration Management > Working Dir Property not shown nor mentioned in ExecuteProcess Processor > > > Key: NIFI-4568 > URL: https://issues.apache.org/jira/browse/NIFI-4568 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration, Configuration Management >Affects Versions: 1.3.0, 1.4.0 >Reporter: Julian Gimbel > Labels: executeProcess, processor, properties > > When executing a process with the executeProcess Operator the default working > directory is the home directory of the user that started Nifi. In the code > there is a Working directory Property that seems to work if one adds it. The > documentation does not mention that it reads that argument and it is not > shown in the Properties of the Operator. > It should either be added in the documentation of the operator or directly in > the Properties with home directory as the default value. > See Line 100 to 110 in > [https://github.com/apache/nifi/blob/6279fd41844205a14cf1f2fb225ead8881b197eb/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteProcess.java] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #174: MINIFICPP-286 Correctly handle filenames ...
Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/174#discussion_r148851261
--- Diff: libminifi/src/processors/PutFile.cpp ---
@@ -127,7 +131,33 @@ void PutFile::onTrigger(core::ProcessContext *context,
core::ProcessSession *ses
}
}
-bool PutFile::putFile(core::ProcessSession *session,
std::shared_ptr flowFile, const std::string &tmpFile, const
std::string &destFile) {
+std::string PutFile::tmpWritePath(const std::string &filename) const {
--- End diff --
thanks for breaking this out. much cleaner.
---
[jira] [Created] (NIFI-4568) Working Dir Property not shown nor mentioned in ExecuteProcess Processor
Julian Gimbel created NIFI-4568: --- Summary: Working Dir Property not shown nor mentioned in ExecuteProcess Processor Key: NIFI-4568 URL: https://issues.apache.org/jira/browse/NIFI-4568 Project: Apache NiFi Issue Type: Bug Components: Configuration Affects Versions: 1.4.0, 1.3.0 Reporter: Julian Gimbel When executing a process with the executeProcess Operator the default working directory is the home directory of the user that started Nifi. In the code there is a Working directory Property that seems to work if one adds it. The documentation does not mention that it reads that argument and it is not shown in the Properties of the Operator. It should either be added in the documentation of the operator or directly in the Properties with home directory as the default value. See Line 100 to 110 in [https://github.com/apache/nifi/blob/6279fd41844205a14cf1f2fb225ead8881b197eb/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteProcess.java] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-286) PutFile fails if filename property includes a path
[
https://issues.apache.org/jira/browse/MINIFICPP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238032#comment-16238032
]
ASF GitHub Bot commented on MINIFICPP-286:
--
Github user achristianson commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/174
@phrocker done.
> PutFile fails if filename property includes a path
> --
>
> Key: MINIFICPP-286
> URL: https://issues.apache.org/jira/browse/MINIFICPP-286
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If a flowfile 'filename' property includes a path (i.e. nested subdirs), then
> PutFile fails due to improper creation of temporary write file.
> Example ExecuteScript lua to update filename:
> {code}
> function onTrigger(context, session)
> flow_file = session:get()
> log:info('rename_file triggered')
> if flow_file ~= nil then
> file_name = flow_file:getAttribute('filename')
> new_file_name = 'a/b/' .. file_name
> log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' ..
> new_file_name)
> flow_file:updateAttribute('filename', new_file_name)
> session:transfer(flow_file, REL_SUCCESS)
> log:info('rename_file success')
> else
> log:info('no work to do')
> end
> end
> {code}
> Log output showing the error:
> {code}
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available
> lua script engine instance
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> triggered
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming
> 1509727478135549592 to a/b/1509727478135549592
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> success
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua
> script engine
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile using temporary file
> data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile writing file a/b/1509727478135549592 into directory data
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] Committing data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> committing put file operation to data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> commit put file operation to data/a/b/1509727478135549592 failed because
> rename() call failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #174: MINIFICPP-286 Correctly handle filenames with ne...
Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/174 @phrocker done. ---
[jira] [Commented] (MINIFICPP-286) PutFile fails if filename property includes a path
[
https://issues.apache.org/jira/browse/MINIFICPP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238014#comment-16238014
]
ASF GitHub Bot commented on MINIFICPP-286:
--
Github user phrocker commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/174
@achristianson Please add a test to this and I'll take a look. Thanks.
> PutFile fails if filename property includes a path
> --
>
> Key: MINIFICPP-286
> URL: https://issues.apache.org/jira/browse/MINIFICPP-286
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If a flowfile 'filename' property includes a path (i.e. nested subdirs), then
> PutFile fails due to improper creation of temporary write file.
> Example ExecuteScript lua to update filename:
> {code}
> function onTrigger(context, session)
> flow_file = session:get()
> log:info('rename_file triggered')
> if flow_file ~= nil then
> file_name = flow_file:getAttribute('filename')
> new_file_name = 'a/b/' .. file_name
> log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' ..
> new_file_name)
> flow_file:updateAttribute('filename', new_file_name)
> session:transfer(flow_file, REL_SUCCESS)
> log:info('rename_file success')
> else
> log:info('no work to do')
> end
> end
> {code}
> Log output showing the error:
> {code}
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available
> lua script engine instance
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> triggered
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming
> 1509727478135549592 to a/b/1509727478135549592
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> success
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua
> script engine
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile using temporary file
> data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile writing file a/b/1509727478135549592 into directory data
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] Committing data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> committing put file operation to data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> commit put file operation to data/a/b/1509727478135549592 failed because
> rename() call failed
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #174: MINIFICPP-286 Correctly handle filenames with ne...
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/174 @achristianson Please add a test to this and I'll take a look. Thanks. ---
[jira] [Commented] (MINIFICPP-286) PutFile fails if filename property includes a path
[
https://issues.apache.org/jira/browse/MINIFICPP-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238002#comment-16238002
]
ASF GitHub Bot commented on MINIFICPP-286:
--
GitHub user achristianson opened a pull request:
https://github.com/apache/nifi-minifi-cpp/pull/174
MINIFICPP-286 Correctly handle filenames with nested paths
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with MINIFI- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] If applicable, have you updated the LICENSE file?
- [x] If applicable, have you updated the NOTICE file?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-286
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-minifi-cpp/pull/174.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #174
commit 8b18adb159f2940aa43ac97ba0f559350ae8688b
Author: Andy I. Christianson
Date: 2017-11-03T17:06:06Z
MINIFICPP-286 Correctly handle filenames with nested paths
> PutFile fails if filename property includes a path
> --
>
> Key: MINIFICPP-286
> URL: https://issues.apache.org/jira/browse/MINIFICPP-286
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If a flowfile 'filename' property includes a path (i.e. nested subdirs), then
> PutFile fails due to improper creation of temporary write file.
> Example ExecuteScript lua to update filename:
> {code}
> function onTrigger(context, session)
> flow_file = session:get()
> log:info('rename_file triggered')
> if flow_file ~= nil then
> file_name = flow_file:getAttribute('filename')
> new_file_name = 'a/b/' .. file_name
> log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' ..
> new_file_name)
> flow_file:updateAttribute('filename', new_file_name)
> session:transfer(flow_file, REL_SUCCESS)
> log:info('rename_file success')
> else
> log:info('no work to do')
> end
> end
> {code}
> Log output showing the error:
> {code}
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available
> lua script engine instance
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> triggered
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming
> 1509727478135549592 to a/b/1509727478135549592
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
> success
> [2017-11-03 12:44:38.916]
> [org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua
> script engine
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile using temporary file
> data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] PutFile writing file a/b/1509727478135549592 into directory data
> [2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
> [info] Committing data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> committing put file operation to data/a/b/1509727478135549592
> [2017-11-03 12:44:38.921]
> [org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
> commit put file operation
[GitHub] nifi-minifi-cpp pull request #174: MINIFICPP-286 Correctly handle filenames ...
GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/174 MINIFICPP-286 Correctly handle filenames with nested paths Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] If applicable, have you updated the LICENSE file? - [x] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-286 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/174.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #174 commit 8b18adb159f2940aa43ac97ba0f559350ae8688b Author: Andy I. Christianson Date: 2017-11-03T17:06:06Z MINIFICPP-286 Correctly handle filenames with nested paths ---
[jira] [Created] (NIFI-4567) LdapUserGroupProvider: Allow admin to configure which group membership attribute
Matt Gilman created NIFI-4567: - Summary: LdapUserGroupProvider: Allow admin to configure which group membership attribute Key: NIFI-4567 URL: https://issues.apache.org/jira/browse/NIFI-4567 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Matt Gilman Assignee: Matt Gilman Priority: Major Currently, group membership is defined using a fully qualified DN between user and group or between group and user. When membership is defined through a user, the group DN is required. When membership is defined through a group, the user DN is required. We should add another property to configure which attribute in the referenced group or user should be used as the value of the user's group attribute or the group's user attribute. For instance, if the user's member attribute contains the value 'group1' this new property would be the group attribute that returns the value 'group1'. For backwards compatibility, when these new properties are blank a full DN is assumed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MINIFICPP-286) PutFile fails if filename property includes a path
Andrew Christianson created MINIFICPP-286:
-
Summary: PutFile fails if filename property includes a path
Key: MINIFICPP-286
URL: https://issues.apache.org/jira/browse/MINIFICPP-286
Project: NiFi MiNiFi C++
Issue Type: Bug
Reporter: Andrew Christianson
Assignee: Andrew Christianson
Priority: Major
If a flowfile 'filename' property includes a path (i.e. nested subdirs), then
PutFile fails due to improper creation of temporary write file.
Example ExecuteScript lua to update filename:
{code}
function onTrigger(context, session)
flow_file = session:get()
log:info('rename_file triggered')
if flow_file ~= nil then
file_name = flow_file:getAttribute('filename')
new_file_name = 'a/b/' .. file_name
log:info('renaming ' .. flow_file:getAttribute('filename') .. ' to ' ..
new_file_name)
flow_file:updateAttribute('filename', new_file_name)
session:transfer(flow_file, REL_SUCCESS)
log:info('rename_file success')
else
log:info('no work to do')
end
end
{code}
Log output showing the error:
{code}
[2017-11-03 12:44:38.916]
[org::apache::nifi::minifi::processors::ExecuteScript] [info] Using available
lua script engine instance
[2017-11-03 12:44:38.916]
[org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
triggered
[2017-11-03 12:44:38.916]
[org::apache::nifi::minifi::processors::ExecuteScript] [info] renaming
1509727478135549592 to a/b/1509727478135549592
[2017-11-03 12:44:38.916]
[org::apache::nifi::minifi::processors::ExecuteScript] [info] rename_file
success
[2017-11-03 12:44:38.916]
[org::apache::nifi::minifi::processors::ExecuteScript] [info] Releasing lua
script engine
[2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
[info] PutFile using temporary file
data/.a/b/1509727478135549592.486467fe-c0b6-11e7-821e-b06ebf2c6de8
[2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
[info] PutFile writing file a/b/1509727478135549592 into directory data
[2017-11-03 12:44:38.921] [org::apache::nifi::minifi::processors::PutFile]
[info] Committing data/a/b/1509727478135549592
[2017-11-03 12:44:38.921]
[org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
committing put file operation to data/a/b/1509727478135549592
[2017-11-03 12:44:38.921]
[org::apache::nifi::minifi::processors::PutFile::ReadCallback] [info] PutFile
commit put file operation to data/a/b/1509727478135549592 failed because
rename() call failed
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (NIFI-4566) GetFile provides problematic error message if unable to delete file
Mark Payne created NIFI-4566:
Summary: GetFile provides problematic error message if unable to
delete file
Key: NIFI-4566
URL: https://issues.apache.org/jira/browse/NIFI-4566
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Reporter: Mark Payne
If GetFile has permissions to read a file but not delete it, it fails with
error messages about FlowFile not being known in session:
{code}
2017-11-03 16:11:55,976 ERROR [Timer-Driven Process Thread-3]
o.a.nifi.processors.standard.GetFile
GetFile[id=82a59322-015f-1000-5cda-c14215a14961] Failed to retrieve files due
to org.apache.nifi.processor.exception.FlowFileAccessException: Unable to
delete C:\tmp\GetFile\sample.txt.txt: {}
org.apache.nifi.processor.exception.FlowFileAccessException: Unable to delete
C:\tmp\GetFile\sample.txt.txt
at
org.apache.nifi.controller.repository.StandardProcessSession.commit(StandardProcessSession.java:429)
at
org.apache.nifi.controller.repository.StandardProcessSession.commit(StandardProcessSession.java:319)
at org.apache.nifi.processors.standard.GetFile.onTrigger(GetFile.java:461)
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1118)
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.nio.file.AccessDeniedException: C:\tmp\GetFile\sample.txt.txt
at
sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at
sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269)
at
sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108)
at java.nio.file.Files.deleteIfExists(Files.java:1165)
at
org.apache.nifi.controller.repository.StandardProcessSession.commit(StandardProcessSession.java:427)
... 14 common frames omitted
2017-11-03 16:11:55,993 ERROR [Timer-Driven Process Thread-6]
o.a.n.c.r.c.StandardResourceClaimManager Decremented claimant count for
StandardResourceClaim[id=1509725515917-1, container=default, section=1] to -1
2017-11-03 16:11:56,006 ERROR [Timer-Driven Process Thread-3]
o.a.nifi.processors.standard.GetFile
GetFile[id=82a59322-015f-1000-5cda-c14215a14961]
GetFile[id=82a59322-015f-1000-5cda-c14215a14961] failed to process due to
org.apache.nifi.processor.exception.FlowFileHandlingException:
StandardFlowFileRecord[uuid=a8965a56-2c52-4577-8d7a-73de3b526a73,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1509725515917-1, container=default,
section=1], offset=0, length=12],offset=0,name=sample.txt.txt,size=12] is not
known in this session (StandardProcessSession[id=0]); rolling back session: {}
org.apache.nifi.processor.exception.FlowFileHandlingException:
StandardFlowFileRecord[uuid=a8965a56-2c52-4577-8d7a-73de3b526a73,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1509725515917-1, container=default,
section=1], offset=0, length=12],offset=0,name=sample.txt.txt,size=12] is not
known in this session (StandardProcessSession[id=0])
at
org.apache.nifi.controller.repository.StandardProcessSession.validateRecordState(StandardProcessSession.java:3024)
at
org.apache.nifi.controller.repository.StandardProcessSession.validateRecordState(StandardProcessSession.java:3010)
at
org.apache.nifi.controller.repository.StandardProcessSession.remove(StandardProcessSession.java:1897)
at org.apache.nifi.processors.standard.GetFile.onTrigger(GetFile.java:467)
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1118)
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
at
org.apache.nifi.controller
[jira] [Commented] (MINIFICPP-250) Create a packet capture process
[ https://issues.apache.org/jira/browse/MINIFICPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237857#comment-16237857 ] ASF GitHub Bot commented on MINIFICPP-250: -- Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/170 @achristianson Thanks. I received that error when their configuration script failed. From your questions I'm guessing that something did not work. I was able to get it to work on linux but made a change this morning in Mac and haven't had a chance to try again because I'm rebuilding my VM. I'll try in centos 7 when I have a chance. > Create a packet capture process > --- > > Key: MINIFICPP-250 > URL: https://issues.apache.org/jira/browse/MINIFICPP-250 > Project: NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Joseph Witt >Assignee: marco polo >Priority: Major > > It would be really powerful to have minificpp agents be able to capture > packets and produce proper pcap bundles for them. This then can be sent via > s2s to a nifi which could use pcap readers and netflow/other writers to > create filtered results, do enrichment, send raw data to kafka/etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #170: MINIFICPP-250: Initial implementation fo PacketC...
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/170 @achristianson Thanks. I received that error when their configuration script failed. From your questions I'm guessing that something did not work. I was able to get it to work on linux but made a change this morning in Mac and haven't had a chance to try again because I'm rebuilding my VM. I'll try in centos 7 when I have a chance. ---
[jira] [Commented] (MINIFICPP-250) Create a packet capture process
[ https://issues.apache.org/jira/browse/MINIFICPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237840#comment-16237840 ] ASF GitHub Bot commented on MINIFICPP-250: -- Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/170 Getting a cmake error: ``` make[4]: *** No rule to make target 'all'. Stop. Makefile:72: recipe for target 'libs' failed make[3]: *** [libs] Error 2 extensions/pcap/CMakeFiles/pcappp.dir/build.make:57: recipe for target 'extensions/pcap/CMakeFiles/pcappp' failed make[2]: *** [extensions/pcap/CMakeFiles/pcappp] Error 2 CMakeFiles/Makefile2:3285: recipe for target 'extensions/pcap/CMakeFiles/pcappp.dir/all' failed make[1]: *** [extensions/pcap/CMakeFiles/pcappp.dir/all] Error 2 Makefile:160: recipe for target 'all' failed make: *** [all] Error 2 ``` Also, pcapplusplus asked me a couple interactive questions during configure: ``` PcapPlusPlus Linux configuration script Number of arguments: 0 Compile PcapPlusPlus with PF_RING? no Compile PcapPlusPlus with DPDK? no PcapPlusPlus configuration is complete. Files created (or modified): mk/platform.mk, mk/PcapPlusPlus.mk ``` This was somewhat surprising/confusing. I checked the README for info on this but couldn't find anything. Is this expected? If so we should probably mention it in the README and note what the interactive answers should be, and if there are implications on the processor functionality. > Create a packet capture process > --- > > Key: MINIFICPP-250 > URL: https://issues.apache.org/jira/browse/MINIFICPP-250 > Project: NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Joseph Witt >Assignee: marco polo >Priority: Major > > It would be really powerful to have minificpp agents be able to capture > packets and produce proper pcap bundles for them. This then can be sent via > s2s to a nifi which could use pcap readers and netflow/other writers to > create filtered results, do enrichment, send raw data to kafka/etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #170: MINIFICPP-250: Initial implementation fo PacketC...
Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/170 Getting a cmake error: ``` make[4]: *** No rule to make target 'all'. Stop. Makefile:72: recipe for target 'libs' failed make[3]: *** [libs] Error 2 extensions/pcap/CMakeFiles/pcappp.dir/build.make:57: recipe for target 'extensions/pcap/CMakeFiles/pcappp' failed make[2]: *** [extensions/pcap/CMakeFiles/pcappp] Error 2 CMakeFiles/Makefile2:3285: recipe for target 'extensions/pcap/CMakeFiles/pcappp.dir/all' failed make[1]: *** [extensions/pcap/CMakeFiles/pcappp.dir/all] Error 2 Makefile:160: recipe for target 'all' failed make: *** [all] Error 2 ``` Also, pcapplusplus asked me a couple interactive questions during configure: ``` PcapPlusPlus Linux configuration script Number of arguments: 0 Compile PcapPlusPlus with PF_RING? no Compile PcapPlusPlus with DPDK? no PcapPlusPlus configuration is complete. Files created (or modified): mk/platform.mk, mk/PcapPlusPlus.mk ``` This was somewhat surprising/confusing. I checked the README for info on this but couldn't find anything. Is this expected? If so we should probably mention it in the README and note what the interactive answers should be, and if there are implications on the processor functionality. ---
[jira] [Commented] (MINIFICPP-250) Create a packet capture process
[ https://issues.apache.org/jira/browse/MINIFICPP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237836#comment-16237836 ] ASF GitHub Bot commented on MINIFICPP-250: -- Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/170 Processor naming is inconsistent with NiFi norms... shouldn't it be CapturePacket(s) or maybe GetPacketCapture, or similar? > Create a packet capture process > --- > > Key: MINIFICPP-250 > URL: https://issues.apache.org/jira/browse/MINIFICPP-250 > Project: NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Joseph Witt >Assignee: marco polo >Priority: Major > > It would be really powerful to have minificpp agents be able to capture > packets and produce proper pcap bundles for them. This then can be sent via > s2s to a nifi which could use pcap readers and netflow/other writers to > create filtered results, do enrichment, send raw data to kafka/etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #170: MINIFICPP-250: Initial implementation fo PacketC...
Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/170 Processor naming is inconsistent with NiFi norms... shouldn't it be CapturePacket(s) or maybe GetPacketCapture, or similar? ---
[jira] [Updated] (MINIFICPP-111) Create integration tests for cpp docker image
[ https://issues.apache.org/jira/browse/MINIFICPP-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Christianson updated MINIFICPP-111: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Create integration tests for cpp docker image > - > > Key: MINIFICPP-111 > URL: https://issues.apache.org/jira/browse/MINIFICPP-111 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Major > > Create a unit test suite which uses compose or docker commands to set up > minifi using the docker image and send data through test flows. Consider > looking into existing test frameworks/harnesses. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MINIFICPP-273) Simplify configuration by supporting default values for scheduling strategy and period
[ https://issues.apache.org/jira/browse/MINIFICPP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo resolved MINIFICPP-273. -- Resolution: Fixed > Simplify configuration by supporting default values for scheduling strategy > and period > -- > > Key: MINIFICPP-273 > URL: https://issues.apache.org/jira/browse/MINIFICPP-273 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Minor > > Simplify configuration of MiNiFi - C++ by allowing default values for > scheduling strategy and period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MINIFICPP-261) Extensions not added to docker/minificppsource, causing make docker to fail
[ https://issues.apache.org/jira/browse/MINIFICPP-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Christianson resolved MINIFICPP-261. --- Resolution: Fixed > Extensions not added to docker/minificppsource, causing make docker to fail > --- > > Key: MINIFICPP-261 > URL: https://issues.apache.org/jira/browse/MINIFICPP-261 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Major > > We're not adding the extensions/ dir to docker/minificppsource/, which > CMakeLists.txt references, so docker builds are failing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-273) Simplify configuration by supporting default values for scheduling strategy and period
[ https://issues.apache.org/jira/browse/MINIFICPP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237826#comment-16237826 ] ASF GitHub Bot commented on MINIFICPP-273: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/162 > Simplify configuration by supporting default values for scheduling strategy > and period > -- > > Key: MINIFICPP-273 > URL: https://issues.apache.org/jira/browse/MINIFICPP-273 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Minor > > Simplify configuration of MiNiFi - C++ by allowing default values for > scheduling strategy and period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MINIFICPP-279) PutFileTests can fail to build
[ https://issues.apache.org/jira/browse/MINIFICPP-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated MINIFICPP-279: - Resolution: Fixed Status: Resolved (was: Patch Available) > PutFileTests can fail to build > -- > > Key: MINIFICPP-279 > URL: https://issues.apache.org/jira/browse/MINIFICPP-279 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Affects Versions: 0.2.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri > > Need to reference the boost includes in the BuildTests CMake file for usage > of filesystem components of Boost in PutFileTests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #162: MINIFICPP-273 Simplify configuration of M...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/162 ---
[jira] [Commented] (NIFI-4473) Add support for large result sets and normalizing Avro names to SelectHiveQL
[ https://issues.apache.org/jira/browse/NIFI-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237823#comment-16237823 ] ASF GitHub Bot commented on NIFI-4473: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2247 > Add support for large result sets and normalizing Avro names to SelectHiveQL > > > Key: NIFI-4473 > URL: https://issues.apache.org/jira/browse/NIFI-4473 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.5.0 > > > A number of enhancements were made to processors like QueryDatabaseTable to > allow for such things as: > - Splitting result sets into multiple flow files (i.e. Max Rows Per Flowfile > property) > - Max number of splits/rows returned (Max fragments) > - Normalizing names to be Avro-compatible > The RDBMS processors also now support Avro logical types, but the version of > Avro needed by the current version of Hive (1.2.1) is Avro 1.7.7, which does > not support logical types. > These enhancements were made to JdbcCommon, but not to HiveJdbcCommon (the > Hive version of the JDBC utils class). Since Hive queries can return even > larger result sets than traditional RDBMS, these properties/enhancements are > at least as valuable to have for SelectHiveQL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4473) Add support for large result sets and normalizing Avro names to SelectHiveQL
[ https://issues.apache.org/jira/browse/NIFI-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237821#comment-16237821 ] ASF subversion and git services commented on NIFI-4473: --- Commit 5cd8a3e729cb9cbd64d97289d610c6e25fe87b9a in nifi's branch refs/heads/master from [~ca9mbu] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5cd8a3e ] NIFI-4473: Fixed SelectHiveQL flowfile handling during error conditions Signed-off-by: Pierre Villard This closes #2247. > Add support for large result sets and normalizing Avro names to SelectHiveQL > > > Key: NIFI-4473 > URL: https://issues.apache.org/jira/browse/NIFI-4473 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.5.0 > > > A number of enhancements were made to processors like QueryDatabaseTable to > allow for such things as: > - Splitting result sets into multiple flow files (i.e. Max Rows Per Flowfile > property) > - Max number of splits/rows returned (Max fragments) > - Normalizing names to be Avro-compatible > The RDBMS processors also now support Avro logical types, but the version of > Avro needed by the current version of Hive (1.2.1) is Avro 1.7.7, which does > not support logical types. > These enhancements were made to JdbcCommon, but not to HiveJdbcCommon (the > Hive version of the JDBC utils class). Since Hive queries can return even > larger result sets than traditional RDBMS, these properties/enhancements are > at least as valuable to have for SelectHiveQL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4473) Add support for large result sets and normalizing Avro names to SelectHiveQL
[ https://issues.apache.org/jira/browse/NIFI-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237819#comment-16237819 ] ASF GitHub Bot commented on NIFI-4473: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2247 +1, full build OK and ran few tests to confirm error scenario and provenance lineage. Merging to master, thanks @mattyb149 ! > Add support for large result sets and normalizing Avro names to SelectHiveQL > > > Key: NIFI-4473 > URL: https://issues.apache.org/jira/browse/NIFI-4473 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.5.0 > > > A number of enhancements were made to processors like QueryDatabaseTable to > allow for such things as: > - Splitting result sets into multiple flow files (i.e. Max Rows Per Flowfile > property) > - Max number of splits/rows returned (Max fragments) > - Normalizing names to be Avro-compatible > The RDBMS processors also now support Avro logical types, but the version of > Avro needed by the current version of Hive (1.2.1) is Avro 1.7.7, which does > not support logical types. > These enhancements were made to JdbcCommon, but not to HiveJdbcCommon (the > Hive version of the JDBC utils class). Since Hive queries can return even > larger result sets than traditional RDBMS, these properties/enhancements are > at least as valuable to have for SelectHiveQL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MINIFICPP-284) MiNiFi crashes if invalid processor is specified
[
https://issues.apache.org/jira/browse/MINIFICPP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Christianson resolved MINIFICPP-284.
---
Resolution: Fixed
> MiNiFi crashes if invalid processor is specified
>
>
> Key: MINIFICPP-284
> URL: https://issues.apache.org/jira/browse/MINIFICPP-284
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If an invalid processor is specified in the yml, MiNiFi identifies this, but
> it ends up with a segmentation fault.
> {code}
> [2017-11-03 11:11:40.653] [org::apache::nifi::minifi::FlowController] [info]
> Load Flow Controller from file
> /home/achristianson/workspace/minifi-flow-2017-10-25/conf/config.yml
> [New Thread 0x7fffdeffd700 (LWP 25910)]
> [New Thread 0x7fffde7fc700 (LWP 25911)]
> [New Thread 0x7fffddffb700 (LWP 25912)]
> [New Thread 0x7fffdd7fa700 (LWP 25913)]
> [New Thread 0x7fffdcff9700 (LWP 25914)]
> [2017-11-03 11:11:40.654] [org::apache::nifi::minifi::core::ProcessGroup]
> [info] ProcessGroup MiNiFi Flow created
> [2017-11-03 11:11:40.654]
> [org::apache::nifi::minifi::core::FlowConfiguration] [error] No Processor
> defined for UnkonwnProcesor
> [New Thread 0x7fffd7fff700 (LWP 25916)]
> [New Thread 0x7fffd77fe700 (LWP 25917)]
> [New Thread 0x7fffd6ffd700 (LWP 25915)]
> [New Thread 0x7fffd67fc700 (LWP 25920)]
> [New Thread 0x7fffd57fa700 (LWP 25919)]
> [New Thread 0x7fffd5ffb700 (LWP 25921)]
> [New Thread 0x7fffd4ff9700 (LWP 25918)]
> Thread 1 "minifi" received signal SIGSEGV, Segmentation fault.
> 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> Missing separate debuginfos, use: debuginfo-install
> boost-filesystem-1.53.0-27.el7.x86_64 boost-system-1.53.0-27.el7.x86_64
> bzip2-libs-1.0.6-13.el7.x86_64 cyrus-sasl-lib-2.1.26-21.el7.x86_64
> elfutils-libelf-0.168-8.el7.x86_64 elfutils-libs-0.168-8.el7.x86_64
> keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-8.el7.x86_64
> libacl-2.2.51-12.el7.x86_64 libarchive-3.1.2-10.el7_2.x86_64
> libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64
> libcom_err-1.42.9-10.el7.x86_64 libcurl-7.29.0-42.el7.x86_64
> libgcc-4.8.5-16.el7.x86_64 libidn-1.28-4.el7.x86_64
> libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-11.el7.x86_64
> libssh2-1.4.3-10.el7_2.1.x86_64 libstdc++-4.8.5-16.el7.x86_64
> libusbx-1.0.20-1.el7.x86_64 libuuid-2.23.2-43.el7.x86_64
> libxml2-2.9.1-6.el7_2.3.x86_64 lua-5.1.4-15.el7.x86_64 lzo-2.06-8.el7.x86_64
> nspr-4.13.1-1.0.el7_3.x86_64 nss-3.28.4-12.el7_4.x86_64
> nss-softokn-freebl-3.28.3-8.el7_4.x86_64 nss-util-3.28.4-3.el7.x86_64
> openldap-2.4.44-5.el7.x86_64 openssl-libs-1.0.2k-8.el7.x86_64
> pcre-8.32-17.el7.x86_64 python-libs-2.7.5-58.el7.x86_64
> systemd-libs-219-42.el7_4.1.x86_64 xz-libs-5.2.2-1.el7.x86_64
> zlib-1.2.7-17.el7.x86_64
> (gdb) bt
> #0 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> #1 0x006b1e80 in
> org::apache::nifi::minifi::core::YamlConfiguration::parseProcessorNodeYaml(YAML::Node,
> org::apache::nifi::minifi::core::ProcessGroup*) ()
> #2 0x00688add in
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(YAML::Node*) ()
> #3 0x00688e65 in
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(std::string
> const&) ()
> #4 0x006cc145 in org::apache::nifi::minifi::FlowController::load() ()
> #5 0x00563fac in main ()
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (NIFI-4473) Add support for large result sets and normalizing Avro names to SelectHiveQL
[ https://issues.apache.org/jira/browse/NIFI-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4473: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add support for large result sets and normalizing Avro names to SelectHiveQL > > > Key: NIFI-4473 > URL: https://issues.apache.org/jira/browse/NIFI-4473 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.5.0 > > > A number of enhancements were made to processors like QueryDatabaseTable to > allow for such things as: > - Splitting result sets into multiple flow files (i.e. Max Rows Per Flowfile > property) > - Max number of splits/rows returned (Max fragments) > - Normalizing names to be Avro-compatible > The RDBMS processors also now support Avro logical types, but the version of > Avro needed by the current version of Hive (1.2.1) is Avro 1.7.7, which does > not support logical types. > These enhancements were made to JdbcCommon, but not to HiveJdbcCommon (the > Hive version of the JDBC utils class). Since Hive queries can return even > larger result sets than traditional RDBMS, these properties/enhancements are > at least as valuable to have for SelectHiveQL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi pull request #2247: NIFI-4473: Fixed SelectHiveQL flowfile handling dur...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2247 ---
[GitHub] nifi issue #2247: NIFI-4473: Fixed SelectHiveQL flowfile handling during err...
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2247 +1, full build OK and ran few tests to confirm error scenario and provenance lineage. Merging to master, thanks @mattyb149 ! ---
[jira] [Commented] (MINIFICPP-284) MiNiFi crashes if invalid processor is specified
[
https://issues.apache.org/jira/browse/MINIFICPP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237798#comment-16237798
]
ASF GitHub Bot commented on MINIFICPP-284:
--
Github user asfgit closed the pull request at:
https://github.com/apache/nifi-minifi-cpp/pull/173
> MiNiFi crashes if invalid processor is specified
>
>
> Key: MINIFICPP-284
> URL: https://issues.apache.org/jira/browse/MINIFICPP-284
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If an invalid processor is specified in the yml, MiNiFi identifies this, but
> it ends up with a segmentation fault.
> {code}
> [2017-11-03 11:11:40.653] [org::apache::nifi::minifi::FlowController] [info]
> Load Flow Controller from file
> /home/achristianson/workspace/minifi-flow-2017-10-25/conf/config.yml
> [New Thread 0x7fffdeffd700 (LWP 25910)]
> [New Thread 0x7fffde7fc700 (LWP 25911)]
> [New Thread 0x7fffddffb700 (LWP 25912)]
> [New Thread 0x7fffdd7fa700 (LWP 25913)]
> [New Thread 0x7fffdcff9700 (LWP 25914)]
> [2017-11-03 11:11:40.654] [org::apache::nifi::minifi::core::ProcessGroup]
> [info] ProcessGroup MiNiFi Flow created
> [2017-11-03 11:11:40.654]
> [org::apache::nifi::minifi::core::FlowConfiguration] [error] No Processor
> defined for UnkonwnProcesor
> [New Thread 0x7fffd7fff700 (LWP 25916)]
> [New Thread 0x7fffd77fe700 (LWP 25917)]
> [New Thread 0x7fffd6ffd700 (LWP 25915)]
> [New Thread 0x7fffd67fc700 (LWP 25920)]
> [New Thread 0x7fffd57fa700 (LWP 25919)]
> [New Thread 0x7fffd5ffb700 (LWP 25921)]
> [New Thread 0x7fffd4ff9700 (LWP 25918)]
> Thread 1 "minifi" received signal SIGSEGV, Segmentation fault.
> 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> Missing separate debuginfos, use: debuginfo-install
> boost-filesystem-1.53.0-27.el7.x86_64 boost-system-1.53.0-27.el7.x86_64
> bzip2-libs-1.0.6-13.el7.x86_64 cyrus-sasl-lib-2.1.26-21.el7.x86_64
> elfutils-libelf-0.168-8.el7.x86_64 elfutils-libs-0.168-8.el7.x86_64
> keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-8.el7.x86_64
> libacl-2.2.51-12.el7.x86_64 libarchive-3.1.2-10.el7_2.x86_64
> libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64
> libcom_err-1.42.9-10.el7.x86_64 libcurl-7.29.0-42.el7.x86_64
> libgcc-4.8.5-16.el7.x86_64 libidn-1.28-4.el7.x86_64
> libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-11.el7.x86_64
> libssh2-1.4.3-10.el7_2.1.x86_64 libstdc++-4.8.5-16.el7.x86_64
> libusbx-1.0.20-1.el7.x86_64 libuuid-2.23.2-43.el7.x86_64
> libxml2-2.9.1-6.el7_2.3.x86_64 lua-5.1.4-15.el7.x86_64 lzo-2.06-8.el7.x86_64
> nspr-4.13.1-1.0.el7_3.x86_64 nss-3.28.4-12.el7_4.x86_64
> nss-softokn-freebl-3.28.3-8.el7_4.x86_64 nss-util-3.28.4-3.el7.x86_64
> openldap-2.4.44-5.el7.x86_64 openssl-libs-1.0.2k-8.el7.x86_64
> pcre-8.32-17.el7.x86_64 python-libs-2.7.5-58.el7.x86_64
> systemd-libs-219-42.el7_4.1.x86_64 xz-libs-5.2.2-1.el7.x86_64
> zlib-1.2.7-17.el7.x86_64
> (gdb) bt
> #0 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> #1 0x006b1e80 in
> org::apache::nifi::minifi::core::YamlConfiguration::parseProcessorNodeYaml(YAML::Node,
> org::apache::nifi::minifi::core::ProcessGroup*) ()
> #2 0x00688add in
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(YAML::Node*) ()
> #3 0x00688e65 in
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(std::string
> const&) ()
> #4 0x006cc145 in org::apache::nifi::minifi::FlowController::load() ()
> #5 0x00563fac in main ()
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINIFICPP-282) Improve test build speed and add Travis build cache
[ https://issues.apache.org/jira/browse/MINIFICPP-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237799#comment-16237799 ] ASF GitHub Bot commented on MINIFICPP-282: -- Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/169 LGTM > Improve test build speed and add Travis build cache > --- > > Key: MINIFICPP-282 > URL: https://issues.apache.org/jira/browse/MINIFICPP-282 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Caleb Johnson >Priority: Minor > > * Use Travis's caching feature to persist $HOME/.ccache > * Enable parallel testing on Travis now that MINIFICPP-60 is merged > * Build catch main() and spdlib as shared objects for all tests > * Best practices according to [catch > docs|https://github.com/philsquared/Catch/blob/master/docs/slow-compiles.md]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #173: MINIFICPP-284 Handle processor configurat...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi-cpp/pull/173 ---
[GitHub] nifi-minifi-cpp issue #169: MINIFICPP-282 Improve test build speed, add Trav...
Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/169 LGTM ---
[jira] [Updated] (MINIFICPP-113) Move from LevelDB to Rocks DB for all repositories.
[ https://issues.apache.org/jira/browse/MINIFICPP-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo updated MINIFICPP-113: - Resolution: Fixed Status: Resolved (was: Patch Available) > Move from LevelDB to Rocks DB for all repositories. > > > Key: MINIFICPP-113 > URL: https://issues.apache.org/jira/browse/MINIFICPP-113 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: marco polo >Assignee: marco polo >Priority: Minor > > Can also be used as a file system repo where we want to minimize the number > of inodes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MINIFICPP-285) ExecuteProcess does not stop within linux
marco polo created MINIFICPP-285: Summary: ExecuteProcess does not stop within linux Key: MINIFICPP-285 URL: https://issues.apache.org/jira/browse/MINIFICPP-285 Project: NiFi MiNiFi C++ Issue Type: Bug Reporter: marco polo Priority: Major -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-273) Simplify configuration by supporting default values for scheduling strategy and period
[ https://issues.apache.org/jira/browse/MINIFICPP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237790#comment-16237790 ] ASF GitHub Bot commented on MINIFICPP-273: -- Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/162 Ready for another look. > Simplify configuration by supporting default values for scheduling strategy > and period > -- > > Key: MINIFICPP-273 > URL: https://issues.apache.org/jira/browse/MINIFICPP-273 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Minor > > Simplify configuration of MiNiFi - C++ by allowing default values for > scheduling strategy and period. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #162: MINIFICPP-273 Simplify configuration of MiNiFi -...
Github user achristianson commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/162 Ready for another look. ---
[jira] [Commented] (MINIFICPP-284) MiNiFi crashes if invalid processor is specified
[
https://issues.apache.org/jira/browse/MINIFICPP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237780#comment-16237780
]
ASF GitHub Bot commented on MINIFICPP-284:
--
Github user minifirocks commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/173
looks good.
> MiNiFi crashes if invalid processor is specified
>
>
> Key: MINIFICPP-284
> URL: https://issues.apache.org/jira/browse/MINIFICPP-284
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If an invalid processor is specified in the yml, MiNiFi identifies this, but
> it ends up with a segmentation fault.
> {code}
> [2017-11-03 11:11:40.653] [org::apache::nifi::minifi::FlowController] [info]
> Load Flow Controller from file
> /home/achristianson/workspace/minifi-flow-2017-10-25/conf/config.yml
> [New Thread 0x7fffdeffd700 (LWP 25910)]
> [New Thread 0x7fffde7fc700 (LWP 25911)]
> [New Thread 0x7fffddffb700 (LWP 25912)]
> [New Thread 0x7fffdd7fa700 (LWP 25913)]
> [New Thread 0x7fffdcff9700 (LWP 25914)]
> [2017-11-03 11:11:40.654] [org::apache::nifi::minifi::core::ProcessGroup]
> [info] ProcessGroup MiNiFi Flow created
> [2017-11-03 11:11:40.654]
> [org::apache::nifi::minifi::core::FlowConfiguration] [error] No Processor
> defined for UnkonwnProcesor
> [New Thread 0x7fffd7fff700 (LWP 25916)]
> [New Thread 0x7fffd77fe700 (LWP 25917)]
> [New Thread 0x7fffd6ffd700 (LWP 25915)]
> [New Thread 0x7fffd67fc700 (LWP 25920)]
> [New Thread 0x7fffd57fa700 (LWP 25919)]
> [New Thread 0x7fffd5ffb700 (LWP 25921)]
> [New Thread 0x7fffd4ff9700 (LWP 25918)]
> Thread 1 "minifi" received signal SIGSEGV, Segmentation fault.
> 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> Missing separate debuginfos, use: debuginfo-install
> boost-filesystem-1.53.0-27.el7.x86_64 boost-system-1.53.0-27.el7.x86_64
> bzip2-libs-1.0.6-13.el7.x86_64 cyrus-sasl-lib-2.1.26-21.el7.x86_64
> elfutils-libelf-0.168-8.el7.x86_64 elfutils-libs-0.168-8.el7.x86_64
> keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-8.el7.x86_64
> libacl-2.2.51-12.el7.x86_64 libarchive-3.1.2-10.el7_2.x86_64
> libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64
> libcom_err-1.42.9-10.el7.x86_64 libcurl-7.29.0-42.el7.x86_64
> libgcc-4.8.5-16.el7.x86_64 libidn-1.28-4.el7.x86_64
> libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-11.el7.x86_64
> libssh2-1.4.3-10.el7_2.1.x86_64 libstdc++-4.8.5-16.el7.x86_64
> libusbx-1.0.20-1.el7.x86_64 libuuid-2.23.2-43.el7.x86_64
> libxml2-2.9.1-6.el7_2.3.x86_64 lua-5.1.4-15.el7.x86_64 lzo-2.06-8.el7.x86_64
> nspr-4.13.1-1.0.el7_3.x86_64 nss-3.28.4-12.el7_4.x86_64
> nss-softokn-freebl-3.28.3-8.el7_4.x86_64 nss-util-3.28.4-3.el7.x86_64
> openldap-2.4.44-5.el7.x86_64 openssl-libs-1.0.2k-8.el7.x86_64
> pcre-8.32-17.el7.x86_64 python-libs-2.7.5-58.el7.x86_64
> systemd-libs-219-42.el7_4.1.x86_64 xz-libs-5.2.2-1.el7.x86_64
> zlib-1.2.7-17.el7.x86_64
> (gdb) bt
> #0 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> #1 0x006b1e80 in
> org::apache::nifi::minifi::core::YamlConfiguration::parseProcessorNodeYaml(YAML::Node,
> org::apache::nifi::minifi::core::ProcessGroup*) ()
> #2 0x00688add in
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(YAML::Node*) ()
> #3 0x00688e65 in
> org::apache::nifi::minifi::core::YamlConfiguration::getRoot(std::string
> const&) ()
> #4 0x006cc145 in org::apache::nifi::minifi::FlowController::load() ()
> #5 0x00563fac in main ()
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] nifi-minifi-cpp issue #173: MINIFICPP-284 Handle processor configuration err...
Github user minifirocks commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/173 looks good. ---
[jira] [Commented] (MINIFICPP-284) MiNiFi crashes if invalid processor is specified
[
https://issues.apache.org/jira/browse/MINIFICPP-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237737#comment-16237737
]
ASF GitHub Bot commented on MINIFICPP-284:
--
GitHub user achristianson opened a pull request:
https://github.com/apache/nifi-minifi-cpp/pull/173
MINIFICPP-284 Handle processor configuration errors better
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with MINIFI- where is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] If applicable, have you updated the LICENSE file?
- [x] If applicable, have you updated the NOTICE file?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-284
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-minifi-cpp/pull/173.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #173
commit 563afa1b367db20c4fc1d218a1a7da2cb074f79c
Author: Andy I. Christianson
Date: 2017-11-03T15:20:29Z
MINIFICPP-284 Handle processor configuration errors better
> MiNiFi crashes if invalid processor is specified
>
>
> Key: MINIFICPP-284
> URL: https://issues.apache.org/jira/browse/MINIFICPP-284
> Project: NiFi MiNiFi C++
> Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> If an invalid processor is specified in the yml, MiNiFi identifies this, but
> it ends up with a segmentation fault.
> {code}
> [2017-11-03 11:11:40.653] [org::apache::nifi::minifi::FlowController] [info]
> Load Flow Controller from file
> /home/achristianson/workspace/minifi-flow-2017-10-25/conf/config.yml
> [New Thread 0x7fffdeffd700 (LWP 25910)]
> [New Thread 0x7fffde7fc700 (LWP 25911)]
> [New Thread 0x7fffddffb700 (LWP 25912)]
> [New Thread 0x7fffdd7fa700 (LWP 25913)]
> [New Thread 0x7fffdcff9700 (LWP 25914)]
> [2017-11-03 11:11:40.654] [org::apache::nifi::minifi::core::ProcessGroup]
> [info] ProcessGroup MiNiFi Flow created
> [2017-11-03 11:11:40.654]
> [org::apache::nifi::minifi::core::FlowConfiguration] [error] No Processor
> defined for UnkonwnProcesor
> [New Thread 0x7fffd7fff700 (LWP 25916)]
> [New Thread 0x7fffd77fe700 (LWP 25917)]
> [New Thread 0x7fffd6ffd700 (LWP 25915)]
> [New Thread 0x7fffd67fc700 (LWP 25920)]
> [New Thread 0x7fffd57fa700 (LWP 25919)]
> [New Thread 0x7fffd5ffb700 (LWP 25921)]
> [New Thread 0x7fffd4ff9700 (LWP 25918)]
> Thread 1 "minifi" received signal SIGSEGV, Segmentation fault.
> 0x0068ecde in
> org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
> unsigned char*) ()
> Missing separate debuginfos, use: debuginfo-install
> boost-filesystem-1.53.0-27.el7.x86_64 boost-system-1.53.0-27.el7.x86_64
> bzip2-libs-1.0.6-13.el7.x86_64 cyrus-sasl-lib-2.1.26-21.el7.x86_64
> elfutils-libelf-0.168-8.el7.x86_64 elfutils-libs-0.168-8.el7.x86_64
> keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-8.el7.x86_64
> libacl-2.2.51-12.el7.x86_64 libarchive-3.1.2-10.el7_2.x86_64
> libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64
> libcom_err-1.42.9-10.el7.x86_64 libcurl-7.29.0-42.el7.x86_64
> libgcc-4.8.5-16.el7.x86_64 libidn-1.28-4.el7.x86_64
> libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-11.el7.x86_64
> libssh2-1.4.3-10.el7_2.1.x86_64 libstdc++-4.8.5-16.el7.x86_64
> libusbx-1.0.20-1.el7.x86_64 libuuid-2.23.2-43.el7.x86_64
> libxml2-2.9.1-6.el7_2.3.x86_64 lua-5.1.4-15.el7.x86_64 lzo-2.06-8.el7.x86_64
> nspr-4.13.1-1.0.el7_3.x86_64 nss-3.28.4-12.el7_4.x86_64
> nss-softokn-freebl-3.28.3-8.el7_4.x86
[GitHub] nifi-minifi-cpp pull request #173: MINIFICPP-284 Handle processor configurat...
GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/173 MINIFICPP-284 Handle processor configuration errors better Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [x] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [x] Has your PR been rebased against the latest commit within the target branch (typically master)? - [x] Is your initial contribution a single, squashed commit? ### For code changes: - [x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [x] If applicable, have you updated the LICENSE file? - [x] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [x] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-284 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/173.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #173 commit 563afa1b367db20c4fc1d218a1a7da2cb074f79c Author: Andy I. Christianson Date: 2017-11-03T15:20:29Z MINIFICPP-284 Handle processor configuration errors better ---
[jira] [Created] (MINIFICPP-284) MiNiFi crashes if invalid processor is specified
Andrew Christianson created MINIFICPP-284:
-
Summary: MiNiFi crashes if invalid processor is specified
Key: MINIFICPP-284
URL: https://issues.apache.org/jira/browse/MINIFICPP-284
Project: NiFi MiNiFi C++
Issue Type: Bug
Reporter: Andrew Christianson
Assignee: Andrew Christianson
Priority: Major
If an invalid processor is specified in the yml, MiNiFi identifies this, but it
ends up with a segmentation fault.
{code}
[2017-11-03 11:11:40.653] [org::apache::nifi::minifi::FlowController] [info]
Load Flow Controller from file
/home/achristianson/workspace/minifi-flow-2017-10-25/conf/config.yml
[New Thread 0x7fffdeffd700 (LWP 25910)]
[New Thread 0x7fffde7fc700 (LWP 25911)]
[New Thread 0x7fffddffb700 (LWP 25912)]
[New Thread 0x7fffdd7fa700 (LWP 25913)]
[New Thread 0x7fffdcff9700 (LWP 25914)]
[2017-11-03 11:11:40.654] [org::apache::nifi::minifi::core::ProcessGroup]
[info] ProcessGroup MiNiFi Flow created
[2017-11-03 11:11:40.654] [org::apache::nifi::minifi::core::FlowConfiguration]
[error] No Processor defined for UnkonwnProcesor
[New Thread 0x7fffd7fff700 (LWP 25916)]
[New Thread 0x7fffd77fe700 (LWP 25917)]
[New Thread 0x7fffd6ffd700 (LWP 25915)]
[New Thread 0x7fffd67fc700 (LWP 25920)]
[New Thread 0x7fffd57fa700 (LWP 25919)]
[New Thread 0x7fffd5ffb700 (LWP 25921)]
[New Thread 0x7fffd4ff9700 (LWP 25918)]
Thread 1 "minifi" received signal SIGSEGV, Segmentation fault.
0x0068ecde in
org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
unsigned char*) ()
Missing separate debuginfos, use: debuginfo-install
boost-filesystem-1.53.0-27.el7.x86_64 boost-system-1.53.0-27.el7.x86_64
bzip2-libs-1.0.6-13.el7.x86_64 cyrus-sasl-lib-2.1.26-21.el7.x86_64
elfutils-libelf-0.168-8.el7.x86_64 elfutils-libs-0.168-8.el7.x86_64
keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-8.el7.x86_64
libacl-2.2.51-12.el7.x86_64 libarchive-3.1.2-10.el7_2.x86_64
libattr-2.4.46-12.el7.x86_64 libcap-2.22-9.el7.x86_64
libcom_err-1.42.9-10.el7.x86_64 libcurl-7.29.0-42.el7.x86_64
libgcc-4.8.5-16.el7.x86_64 libidn-1.28-4.el7.x86_64
libpng-1.5.13-7.el7_2.x86_64 libselinux-2.5-11.el7.x86_64
libssh2-1.4.3-10.el7_2.1.x86_64 libstdc++-4.8.5-16.el7.x86_64
libusbx-1.0.20-1.el7.x86_64 libuuid-2.23.2-43.el7.x86_64
libxml2-2.9.1-6.el7_2.3.x86_64 lua-5.1.4-15.el7.x86_64 lzo-2.06-8.el7.x86_64
nspr-4.13.1-1.0.el7_3.x86_64 nss-3.28.4-12.el7_4.x86_64
nss-softokn-freebl-3.28.3-8.el7_4.x86_64 nss-util-3.28.4-3.el7.x86_64
openldap-2.4.44-5.el7.x86_64 openssl-libs-1.0.2k-8.el7.x86_64
pcre-8.32-17.el7.x86_64 python-libs-2.7.5-58.el7.x86_64
systemd-libs-219-42.el7_4.1.x86_64 xz-libs-5.2.2-1.el7.x86_64
zlib-1.2.7-17.el7.x86_64
(gdb) bt
#0 0x0068ecde in
org::apache::nifi::minifi::core::FlowConfiguration::createProcessor(std::string,
unsigned char*) ()
#1 0x006b1e80 in
org::apache::nifi::minifi::core::YamlConfiguration::parseProcessorNodeYaml(YAML::Node,
org::apache::nifi::minifi::core::ProcessGroup*) ()
#2 0x00688add in
org::apache::nifi::minifi::core::YamlConfiguration::getRoot(YAML::Node*) ()
#3 0x00688e65 in
org::apache::nifi::minifi::core::YamlConfiguration::getRoot(std::string const&)
()
#4 0x006cc145 in org::apache::nifi::minifi::FlowController::load() ()
#5 0x00563fac in main ()
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON
[ https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237669#comment-16237669 ] John Reynolds commented on MINIFICPP-114: - [~calebj], By all means go ahead and work on this. I've been busy working on a few other things so haven't had a chance to get to this one yet. Can't change assignee though. > Consolidate JSON API use to RapidJSON > - > > Key: MINIFICPP-114 > URL: https://issues.apache.org/jira/browse/MINIFICPP-114 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: John Reynolds >Assignee: John Reynolds >Priority: Major > > MiNiFi was updated with new dependencies to jsoncpp: > SiteToSiteProvenanceReportingTask > Performance observations indicate significant improvements with RapidJSON vs. > jsoncpp. Convert all use of jsoncpp to RapidJSON where applicable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON
[ https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237662#comment-16237662 ] Caleb Johnson commented on MINIFICPP-114: - Is this a release priority? The following components currently depend on jsoncpp: * Un/FocusArchive * RemoteProcessorGroupPort * Site-to-site provenance reporting I can work on this if John doesn't want to. > Consolidate JSON API use to RapidJSON > - > > Key: MINIFICPP-114 > URL: https://issues.apache.org/jira/browse/MINIFICPP-114 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: John Reynolds >Assignee: John Reynolds >Priority: Major > > MiNiFi was updated with new dependencies to jsoncpp: > SiteToSiteProvenanceReportingTask > Performance observations indicate significant improvements with RapidJSON vs. > jsoncpp. Convert all use of jsoncpp to RapidJSON where applicable. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4325) Create a new ElasticSearch processor that supports the JSON DSL
[ https://issues.apache.org/jira/browse/NIFI-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237621#comment-16237621 ] ASF GitHub Bot commented on NIFI-4325: -- Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/2113 Reviewing... > Create a new ElasticSearch processor that supports the JSON DSL > --- > > Key: NIFI-4325 > URL: https://issues.apache.org/jira/browse/NIFI-4325 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Priority: Minor > > The existing ElasticSearch processors use the Lucene-style syntax for > querying, not the JSON DSL. A new processor is needed that can take a full > JSON query and execute it. It should also support aggregation queries in this > syntax. A user needs to be able to take a query as-is from Kibana and drop it > into NiFi and have it just run. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi issue #2113: NIFI-4325 Added new processor that uses the JSON DSL.
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/2113 Reviewing... ---
[jira] [Commented] (MINIFICPP-33) Create GetGPS processor for acquiring GPS coordinates
[ https://issues.apache.org/jira/browse/MINIFICPP-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237602#comment-16237602 ] ASF GitHub Bot commented on MINIFICPP-33: - GitHub user phrocker opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/172 MINIFI-218: Update per current MiNiFi C++ standards GetGPS refactoring Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFI-218 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/172.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #172 commit 4765ec849356c62f7a7427bd67e51c25065b2b40 Author: jdye64 Date: 2017-05-03T14:42:16Z MINIFI-218: Update per current MiNiFi C++ standards GetGPS refactoring > Create GetGPS processor for acquiring GPS coordinates > - > > Key: MINIFICPP-33 > URL: https://issues.apache.org/jira/browse/MINIFICPP-33 > Project: NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Jeremy Dyer >Assignee: Jeremy Dyer >Priority: Major > > GPSD is a popular framework for interacting with a multitude of GPS devices. > It drastically simplifies the interaction with vendor specific GPS devices by > providing a daemon service which communicates with the device, converts the > raw NMEA 0183 sentences into JSON objects, and then emits those JSON objects > over a socket for 0-N downstream devices to consume. > This feature would create a GetGPS processor that would listen to a running > instance of GPSD as one of those downstream consumers. The processor would > provide integration with the GPSD daemon to accept the JSON objects and > create new flowfiles for each of the JSON objects received. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi-minifi-cpp pull request #172: MINIFI-218: Update per current MiNiFi C++...
GitHub user phrocker opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/172 MINIFI-218: Update per current MiNiFi C++ standards GetGPS refactoring Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFI- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible. You can merge this pull request into a Git repository by running: $ git pull https://github.com/phrocker/nifi-minifi-cpp MINIFI-218 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/172.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #172 commit 4765ec849356c62f7a7427bd67e51c25065b2b40 Author: jdye64 Date: 2017-05-03T14:42:16Z MINIFI-218: Update per current MiNiFi C++ standards GetGPS refactoring ---
[jira] [Resolved] (MINIFICPP-39) Create FocusArchive processor
[ https://issues.apache.org/jira/browse/MINIFICPP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo resolved MINIFICPP-39. - Resolution: Fixed > Create FocusArchive processor > - > > Key: MINIFICPP-39 > URL: https://issues.apache.org/jira/browse/MINIFICPP-39 > Project: NiFi MiNiFi C++ > Issue Type: Task >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Minor > > Create an FocusArchive processor which implements a lens over an archive > (tar, etc.). A concise, though informal, definition of a lens is as follows: > "Essentially, they represent the act of “peering into” or “focusing in on” > some particular piece/path of a complex data object such that you can more > precisely target particular operations without losing the context or > structure of the overall data you’re working with." > https://medium.com/@dtipson/functional-lenses-d1aba9e52254#.hdgsvbraq > Why an FocusArchive in MiNiFi? Simply put, it will enable us to "focus in on" > an entry in the archive, perform processing *in-context* of that entry, then > re-focus on the overall archive. This allows for transformation or other > processing of an entry in the archive without losing the overall context of > the archive. > Initial format support is tar, due to its simplicity and ubiquity. > Attributes: > - Path (the path in the archive to focus; "/" to re-focus the overall archive) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MINIFICPP-110) Implement ExecuteScript
[ https://issues.apache.org/jira/browse/MINIFICPP-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] marco polo resolved MINIFICPP-110. -- Resolution: Fixed > Implement ExecuteScript > --- > > Key: MINIFICPP-110 > URL: https://issues.apache.org/jira/browse/MINIFICPP-110 > Project: NiFi MiNiFi C++ > Issue Type: New Feature >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Major > > Initially support python and lua. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MINIFICPP-39) Create FocusArchive processor
[ https://issues.apache.org/jira/browse/MINIFICPP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237561#comment-16237561 ] Caleb Johnson commented on MINIFICPP-39: I think this should be marked as resolved? > Create FocusArchive processor > - > > Key: MINIFICPP-39 > URL: https://issues.apache.org/jira/browse/MINIFICPP-39 > Project: NiFi MiNiFi C++ > Issue Type: Task >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Minor > > Create an FocusArchive processor which implements a lens over an archive > (tar, etc.). A concise, though informal, definition of a lens is as follows: > "Essentially, they represent the act of “peering into” or “focusing in on” > some particular piece/path of a complex data object such that you can more > precisely target particular operations without losing the context or > structure of the overall data you’re working with." > https://medium.com/@dtipson/functional-lenses-d1aba9e52254#.hdgsvbraq > Why an FocusArchive in MiNiFi? Simply put, it will enable us to "focus in on" > an entry in the archive, perform processing *in-context* of that entry, then > re-focus on the overall archive. This allows for transformation or other > processing of an entry in the archive without losing the overall context of > the archive. > Initial format support is tar, due to its simplicity and ubiquity. > Attributes: > - Path (the path in the archive to focus; "/" to re-focus the overall archive) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (NIFI-4560) Add mime.type and record.count to @WritesAttributes doc for ValidateRecord
[ https://issues.apache.org/jira/browse/NIFI-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard resolved NIFI-4560. -- Resolution: Fixed Fix Version/s: 1.5.0 > Add mime.type and record.count to @WritesAttributes doc for ValidateRecord > -- > > Key: NIFI-4560 > URL: https://issues.apache.org/jira/browse/NIFI-4560 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.4.0 >Reporter: Matt Burgess >Assignee: Andrew Lim >Priority: Major > Fix For: 1.5.0 > > > Currently (NiFi 1.4.0) ValidateRecord will transfer any attributes from the > WriteResult to the outgoing FlowFile, but I don't think there are any (for a > query) at the time of this writing. However the ValidateRecord processor also > updates the "mime.type" attribute based on the RecordSetWriter chosen, and > also sets the "record.count" attribute to the number of records that match > the query. > None of the aforementioned are in the processor documentation; if the > WriteResult ones are premature to mention that's ok, but we should add the > mime.type and record.count attributes to the documentation for ValidateRecord. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4560) Add mime.type and record.count to @WritesAttributes doc for ValidateRecord
[ https://issues.apache.org/jira/browse/NIFI-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237398#comment-16237398 ] ASF GitHub Bot commented on NIFI-4560: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2249 > Add mime.type and record.count to @WritesAttributes doc for ValidateRecord > -- > > Key: NIFI-4560 > URL: https://issues.apache.org/jira/browse/NIFI-4560 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.4.0 >Reporter: Matt Burgess >Assignee: Andrew Lim >Priority: Major > > Currently (NiFi 1.4.0) ValidateRecord will transfer any attributes from the > WriteResult to the outgoing FlowFile, but I don't think there are any (for a > query) at the time of this writing. However the ValidateRecord processor also > updates the "mime.type" attribute based on the RecordSetWriter chosen, and > also sets the "record.count" attribute to the number of records that match > the query. > None of the aforementioned are in the processor documentation; if the > WriteResult ones are premature to mention that's ok, but we should add the > mime.type and record.count attributes to the documentation for ValidateRecord. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4560) Add mime.type and record.count to @WritesAttributes doc for ValidateRecord
[ https://issues.apache.org/jira/browse/NIFI-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237397#comment-16237397 ] ASF subversion and git services commented on NIFI-4560: --- Commit b5d7aecfac6b5f4424b3bc775c1477281f599846 in nifi's branch refs/heads/master from [~andrewmlim] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b5d7aec ] NIFI-4560 Added mime.type and record.count Write Attributes to ValidateRecord doc Signed-off-by: Pierre Villard This closes #2249. > Add mime.type and record.count to @WritesAttributes doc for ValidateRecord > -- > > Key: NIFI-4560 > URL: https://issues.apache.org/jira/browse/NIFI-4560 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.4.0 >Reporter: Matt Burgess >Assignee: Andrew Lim >Priority: Major > > Currently (NiFi 1.4.0) ValidateRecord will transfer any attributes from the > WriteResult to the outgoing FlowFile, but I don't think there are any (for a > query) at the time of this writing. However the ValidateRecord processor also > updates the "mime.type" attribute based on the RecordSetWriter chosen, and > also sets the "record.count" attribute to the number of records that match > the query. > None of the aforementioned are in the processor documentation; if the > WriteResult ones are premature to mention that's ok, but we should add the > mime.type and record.count attributes to the documentation for ValidateRecord. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NIFI-4560) Add mime.type and record.count to @WritesAttributes doc for ValidateRecord
[ https://issues.apache.org/jira/browse/NIFI-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237396#comment-16237396 ] ASF GitHub Bot commented on NIFI-4560: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2249 +1, full build ok, thanks @andrewmlim, merging to master > Add mime.type and record.count to @WritesAttributes doc for ValidateRecord > -- > > Key: NIFI-4560 > URL: https://issues.apache.org/jira/browse/NIFI-4560 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.4.0 >Reporter: Matt Burgess >Assignee: Andrew Lim >Priority: Major > > Currently (NiFi 1.4.0) ValidateRecord will transfer any attributes from the > WriteResult to the outgoing FlowFile, but I don't think there are any (for a > query) at the time of this writing. However the ValidateRecord processor also > updates the "mime.type" attribute based on the RecordSetWriter chosen, and > also sets the "record.count" attribute to the number of records that match > the query. > None of the aforementioned are in the processor documentation; if the > WriteResult ones are premature to mention that's ok, but we should add the > mime.type and record.count attributes to the documentation for ValidateRecord. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] nifi issue #2249: NIFI-4560 Added mime.type and record.count Write Attribute...
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2249 +1, full build ok, thanks @andrewmlim, merging to master ---
[GitHub] nifi pull request #2249: NIFI-4560 Added mime.type and record.count Write At...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2249 ---
