[jira] [Updated] (NIFI-5027) CLI - Add a command to start controller services
[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-5027: - Resolution: Fixed Fix Version/s: 1.7.0 Status: Resolved (was: Patch Available) > CLI - Add a command to start controller services > > > Key: NIFI-5027 > URL: https://issues.apache.org/jira/browse/NIFI-5027 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Bryan Bende >Priority: Major > Fix For: 1.7.0 > > Attachments: TestStartStopCS.xml > > > When importing a versioned process group from the registry, all the > components will be stopped (in case of update, only the newly added > components will be stopped). We already have a command pg-start to start a > process group, but it will fail if the process group relies on controller > services that should be enabled first. > A new command like pg-enable-cs could be added, or just add a parameter/flag > to the pg-start command. > Things to consider: > * there can be a dependency chain between the controller services requiring > to start the controller services in the right order. Example: the avro schema > registry CS and a reader/writer CS depending on the schema registry CS. > * there can be a CS defined at pg level that is not referenced by any > component inside the pg but that would need to be started nevertheless. > Example: the distributed map cache server CS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5027) CLI - Add a command to start controller services
[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426198#comment-16426198 ] ASF GitHub Bot commented on NIFI-5027: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2604 > CLI - Add a command to start controller services > > > Key: NIFI-5027 > URL: https://issues.apache.org/jira/browse/NIFI-5027 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Bryan Bende >Priority: Major > Fix For: 1.7.0 > > Attachments: TestStartStopCS.xml > > > When importing a versioned process group from the registry, all the > components will be stopped (in case of update, only the newly added > components will be stopped). We already have a command pg-start to start a > process group, but it will fail if the process group relies on controller > services that should be enabled first. > A new command like pg-enable-cs could be added, or just add a parameter/flag > to the pg-start command. > Things to consider: > * there can be a dependency chain between the controller services requiring > to start the controller services in the right order. Example: the avro schema > registry CS and a reader/writer CS depending on the schema registry CS. > * there can be a CS defined at pg level that is not referenced by any > component inside the pg but that would need to be started nevertheless. > Example: the distributed map cache server CS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5027) CLI - Add a command to start controller services
[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426197#comment-16426197 ] ASF subversion and git services commented on NIFI-5027: --- Commit 7abb02fff000e70523c8b7afb6d3b9a7df5c929f in nifi's branch refs/heads/master from [~bbende] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7abb02f ] NIFI-5027 Adding commands pg-get-services, pg-enable-services, and pg-disable-services - Improving response when service is stuck enabling, and improving response when some services couldn't be enabled - Throwing exception when a service is stuck enabling or can't be enabled so that standalone mode gets a non-zero status code, also allowing use of -verbose so stand-alone can decide if output is desired - Improving information provided by pg-disable-services Signed-off-by: Pierre Villard This closes #2604. > CLI - Add a command to start controller services > > > Key: NIFI-5027 > URL: https://issues.apache.org/jira/browse/NIFI-5027 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Bryan Bende >Priority: Major > Attachments: TestStartStopCS.xml > > > When importing a versioned process group from the registry, all the > components will be stopped (in case of update, only the newly added > components will be stopped). We already have a command pg-start to start a > process group, but it will fail if the process group relies on controller > services that should be enabled first. > A new command like pg-enable-cs could be added, or just add a parameter/flag > to the pg-start command. > Things to consider: > * there can be a dependency chain between the controller services requiring > to start the controller services in the right order. Example: the avro schema > registry CS and a reader/writer CS depending on the schema registry CS. > * there can be a CS defined at pg level that is not referenced by any > component inside the pg but that would need to be started nevertheless. > Example: the distributed map cache server CS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #2604: NIFI-5027 Adding pg-get-services command
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/2604 ---
[GitHub] nifi issue #2604: NIFI-5027 Adding pg-get-services command
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2604 Just did some more testing and it looks good to me. Thanks for all the improvements. Just a note about the response code: it's equal to 255 on my Mac, but as long as it's not equal to 0, it's good for me. Thanks @bbende ! Merging to master. ---
[jira] [Commented] (NIFI-5027) CLI - Add a command to start controller services
[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426188#comment-16426188 ] ASF GitHub Bot commented on NIFI-5027: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2604 Just did some more testing and it looks good to me. Thanks for all the improvements. Just a note about the response code: it's equal to 255 on my Mac, but as long as it's not equal to 0, it's good for me. Thanks @bbende ! Merging to master. > CLI - Add a command to start controller services > > > Key: NIFI-5027 > URL: https://issues.apache.org/jira/browse/NIFI-5027 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Bryan Bende >Priority: Major > Attachments: TestStartStopCS.xml > > > When importing a versioned process group from the registry, all the > components will be stopped (in case of update, only the newly added > components will be stopped). We already have a command pg-start to start a > process group, but it will fail if the process group relies on controller > services that should be enabled first. > A new command like pg-enable-cs could be added, or just add a parameter/flag > to the pg-start command. > Things to consider: > * there can be a dependency chain between the controller services requiring > to start the controller services in the right order. Example: the avro schema > registry CS and a reader/writer CS depending on the schema registry CS. > * there can be a CS defined at pg level that is not referenced by any > component inside the pg but that would need to be started nevertheless. > Example: the distributed map cache server CS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-4990) Add provenance events in FetchDistributedMapCache
[ https://issues.apache.org/jira/browse/NIFI-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-4990: - Resolution: Not A Problem Status: Resolved (was: Patch Available) Provenance events are already correctly generated. > Add provenance events in FetchDistributedMapCache > - > > Key: NIFI-4990 > URL: https://issues.apache.org/jira/browse/NIFI-4990 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #2563: NIFI-4990 - Add provenance events in FetchDistribut...
Github user pvillard31 closed the pull request at: https://github.com/apache/nifi/pull/2563 ---
[jira] [Commented] (NIFI-4990) Add provenance events in FetchDistributedMapCache
[ https://issues.apache.org/jira/browse/NIFI-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426091#comment-16426091 ] ASF GitHub Bot commented on NIFI-4990: -- Github user pvillard31 closed the pull request at: https://github.com/apache/nifi/pull/2563 > Add provenance events in FetchDistributedMapCache > - > > Key: NIFI-4990 > URL: https://issues.apache.org/jira/browse/NIFI-4990 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi issue #2604: NIFI-5027 Adding pg-get-services command
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/2604 @pvillard31 I just rebased and forced push, can you give this another try? The main changes since what you last tried this morning are the following... - In standalone you can use -verbose to get the same output as interactive - An exception is thrown when a service stays enabling, or when one or more are invalid, this makes a -1 response code for standalone - Improve the disable command to work similarly to the enable command ---
[jira] [Commented] (NIFI-4862) Add Copy original attributes to SelectHiveQL processor
[ https://issues.apache.org/jira/browse/NIFI-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426077#comment-16426077 ] ASF GitHub Bot commented on NIFI-4862: -- Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/2605 @ijokarumawak Mind taking a look at this one? It changed the order of provenance events so it touched your code for emitting a FETCH-FORK (now it's a FORK-FETCH). Just want to make sure the provenance chain is clear, simple, and complete. Thanks in advance! > Add Copy original attributes to SelectHiveQL processor > -- > > Key: NIFI-4862 > URL: https://issues.apache.org/jira/browse/NIFI-4862 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.5.0 >Reporter: Jakub Leś >Priority: Minor > Attachments: > 0001-NIFI-4862-Add-Copy-original-attributtes-to-SelectHiv.patch > > > Hi, > Please add "Copy original attributes" to processor SelectHiveQL. Thanks to > that we can use HttpRequest and HttpResponse to synchronize fetching query > result in webservice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi issue #2605: NIFI-4862: Keep incoming flowfile attributes in outgoing f...
Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/2605 @ijokarumawak Mind taking a look at this one? It changed the order of provenance events so it touched your code for emitting a FETCH-FORK (now it's a FORK-FETCH). Just want to make sure the provenance chain is clear, simple, and complete. Thanks in advance! ---
[jira] [Commented] (NIFI-4862) Add Copy original attributes to SelectHiveQL processor
[ https://issues.apache.org/jira/browse/NIFI-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426076#comment-16426076 ] ASF GitHub Bot commented on NIFI-4862: -- GitHub user mattyb149 opened a pull request: https://github.com/apache/nifi/pull/2605 NIFI-4862: Keep incoming flowfile attributes in outgoing flowfiles from SelectHiveQL 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? - [x] 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/mattyb149/nifi NIFI-4862 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/2605.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 #2605 commit cbd0e10b9ef6d692841b551764388c5973bdfb75 Author: Matthew Burgess Date: 2018-04-04T19:38:24Z NIFI-4862: Keep incoming flowfile attributes in outgoing flowfiles from SelectHiveQL > Add Copy original attributes to SelectHiveQL processor > -- > > Key: NIFI-4862 > URL: https://issues.apache.org/jira/browse/NIFI-4862 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.5.0 >Reporter: Jakub Leś >Priority: Minor > Attachments: > 0001-NIFI-4862-Add-Copy-original-attributtes-to-SelectHiv.patch > > > Hi, > Please add "Copy original attributes" to processor SelectHiveQL. Thanks to > that we can use HttpRequest and HttpResponse to synchronize fetching query > result in webservice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #2605: NIFI-4862: Keep incoming flowfile attributes in out...
GitHub user mattyb149 opened a pull request: https://github.com/apache/nifi/pull/2605 NIFI-4862: Keep incoming flowfile attributes in outgoing flowfiles from SelectHiveQL 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? - [x] 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/mattyb149/nifi NIFI-4862 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/2605.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 #2605 commit cbd0e10b9ef6d692841b551764388c5973bdfb75 Author: Matthew Burgess Date: 2018-04-04T19:38:24Z NIFI-4862: Keep incoming flowfile attributes in outgoing flowfiles from SelectHiveQL ---
[jira] [Commented] (MINIFICPP-445) Implement escape/unescape CSV functions in expression language
[
https://issues.apache.org/jira/browse/MINIFICPP-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426052#comment-16426052
]
ASF GitHub Bot commented on MINIFICPP-445:
--
Github user apiri commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/293
Looks like all envs in Travis are failing with:
```
---
Decode XML
---
/Users/travis/build/apache/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1052
...
/Users/travis/build/apache/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1057:
FAILED:
REQUIRE( "Zero > One < \"two!\" & 'true'" ==
expr({flow_file_a}).asString() )
with expansion:
"Zero > One < "two!" & 'true'"
==
"Zero > One < "two!" & 'true'"
```
> Implement escape/unescape CSV functions in expression language
> --
>
> Key: MINIFICPP-445
> URL: https://issues.apache.org/jira/browse/MINIFICPP-445
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> *
> [escapeCsv|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#escapecsv]
> *
> [unescapeCsv|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#unescapecsv]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi-minifi-cpp issue #293: MINIFICPP-445 Added escape/unescape CSV expressi...
Github user apiri commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/293
Looks like all envs in Travis are failing with:
```
---
Decode XML
---
/Users/travis/build/apache/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1052
...
/Users/travis/build/apache/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1057:
FAILED:
REQUIRE( "Zero > One < \"two!\" & 'true'" ==
expr({flow_file_a}).asString() )
with expansion:
"Zero > One < "two!" & 'true'"
==
"Zero > One < "two!" & 'true'"
```
---
[jira] [Commented] (NIFI-4862) Add Copy original attributes to SelectHiveQL processor
[ https://issues.apache.org/jira/browse/NIFI-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426049#comment-16426049 ] Matt Burgess commented on NIFI-4862: This is actually a regression caused by a logic bug in NIFI-4473. Rather than add another property to choose whether or not to include the original attribute, I propose we reinstate the original behavior, where if there is an incoming flow file, its attributes will be transferred to the outgoing flow file(s). > Add Copy original attributes to SelectHiveQL processor > -- > > Key: NIFI-4862 > URL: https://issues.apache.org/jira/browse/NIFI-4862 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.5.0 >Reporter: Jakub Leś >Priority: Minor > Attachments: > 0001-NIFI-4862-Add-Copy-original-attributtes-to-SelectHiv.patch > > > Hi, > Please add "Copy original attributes" to processor SelectHiveQL. Thanks to > that we can use HttpRequest and HttpResponse to synchronize fetching query > result in webservice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4942) NiFi Toolkit - Allow migration of master key without previous password
[
https://issues.apache.org/jira/browse/NIFI-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426051#comment-16426051
]
Andy LoPresto commented on NIFI-4942:
-
I coordinated with Yolanda again today to discuss how Ambari would get the salt
and cost parameters for the hash generation (hashes with different salts/costs
cannot be compared directly, but rather each can be compared to the raw input
value. As we will not have access to this at the toolkit stage, the hash *must*
be generated with the same salt and costs that are stored for comparison). The
toolkit will provide a {{--current-hash-params}} flag to query the existing
salt and cost parameters in JSON format and then accept the hash generated with
those inputs.
Example:
{code}
$ ./bin/encrypt-config.sh --current-hash-params
{"N": "1024", "r": "8", "p": "1", salt: "ABCDEFGHIJKLMNOPQRSTUV"}
{code}
> NiFi Toolkit - Allow migration of master key without previous password
> --
>
> Key: NIFI-4942
> URL: https://issues.apache.org/jira/browse/NIFI-4942
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
>Affects Versions: 1.5.0
>Reporter: Yolanda M. Davis
>Assignee: Andy LoPresto
>Priority: Major
>
> Currently the encryption cli in nifi toolkit requires that, in order to
> migrate from one master key to the next, the previous master key or password
> should be provided. In cases where the provisioning tool doesn't have the
> previous value available this becomes challenging to provide and may be prone
> to error. In speaking with [~alopresto] we can allow toolkit to support a
> mode of execution such that the master key can be updated without requiring
> the previous password. Also documentation around it's usage should be updated
> to be clear in describing the purpose and the type of environment where this
> command should be used (admin only access etc).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-4862) Add Copy original attributes to SelectHiveQL processor
[ https://issues.apache.org/jira/browse/NIFI-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-4862: --- Summary: Add Copy original attributes to SelectHiveQL processor (was: Add Copy original attributtes to SelectHiveQL processer) > Add Copy original attributes to SelectHiveQL processor > -- > > Key: NIFI-4862 > URL: https://issues.apache.org/jira/browse/NIFI-4862 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.5.0 >Reporter: Jakub Leś >Priority: Minor > Attachments: > 0001-NIFI-4862-Add-Copy-original-attributtes-to-SelectHiv.patch > > > Hi, > Please add "Copy original attributes" to processor SelectHiveQL. Thanks to > that we can use HttpRequest and HttpResponse to synchronize fetching query > result in webservice. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5042) Add section on using restricted components to the "Versioning a Dataflow" section of the User Guide
[ https://issues.apache.org/jira/browse/NIFI-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-5042: - Summary: Add section on using restricted components to the "Versioning a Dataflow" section of the User Guide (was: Add section on using restricted components to the "Versioning a Flow" section of the User Guide) > Add section on using restricted components to the "Versioning a Dataflow" > section of the User Guide > --- > > Key: NIFI-5042 > URL: https://issues.apache.org/jira/browse/NIFI-5042 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > With granular component restrictions introduced in 1.6.0 (NIFI-4885), it > would be helpful to discuss how restricted components should be used in > versioned flows. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5042) Add section on using restricted components to the "Versioning a Flow" section of the User Guide
Andrew Lim created NIFI-5042: Summary: Add section on using restricted components to the "Versioning a Flow" section of the User Guide Key: NIFI-5042 URL: https://issues.apache.org/jira/browse/NIFI-5042 Project: Apache NiFi Issue Type: Improvement Components: Documentation & Website Reporter: Andrew Lim With granular component restrictions introduced in 1.6.0 (NIFI-4885), it would be helpful to discuss how restricted components should be used in versioned flows. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-5042) Add section on using restricted components to the "Versioning a Flow" section of the User Guide
[ https://issues.apache.org/jira/browse/NIFI-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-5042: Assignee: Andrew Lim > Add section on using restricted components to the "Versioning a Flow" section > of the User Guide > --- > > Key: NIFI-5042 > URL: https://issues.apache.org/jira/browse/NIFI-5042 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > With granular component restrictions introduced in 1.6.0 (NIFI-4885), it > would be helpful to discuss how restricted components should be used in > versioned flows. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFICPP-448) Allow uuid to be built & statically-linked
[ https://issues.apache.org/jira/browse/MINIFICPP-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425961#comment-16425961 ] ASF GitHub Bot commented on MINIFICPP-448: -- Github user apiri commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/294 The 4 header files that are added are already present in thirdparty/uuid. Could we consolidate to one copy? > Allow uuid to be built & statically-linked > -- > > Key: MINIFICPP-448 > URL: https://issues.apache.org/jira/browse/MINIFICPP-448 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Major > > We already bundle uuid code in nifi-minifi-cpp, but there is no way to build > it. The CMakeLists.txt should be updated to allow building of this bundled > uuid and statically-linking it, making it easier to run in environments where > uuid is not available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi-minifi-cpp issue #294: MINIFICPP-448 Add uuid external/static link proj...
Github user apiri commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/294 The 4 header files that are added are already present in thirdparty/uuid. Could we consolidate to one copy? ---
[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship
[
https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425884#comment-16425884
]
ASF GitHub Bot commented on NIFI-3576:
--
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2601#discussion_r179217708
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/QueryElasticsearchHttp.java
---
@@ -68,8 +72,10 @@
+ "To retrieve more records, use the ScrollElasticsearchHttp
processor.")
@WritesAttributes({
@WritesAttribute(attribute = "filename", description = "The
filename attribute is set to the document identifier"),
+@WritesAttribute(attribute = "es.hitCount", description = "The
number of hits for a query"),
--- End diff --
nah, it is fine by me
> QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship
>
>
> Key: NIFI-3576
> URL: https://issues.apache.org/jira/browse/NIFI-3576
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Joseph Percivall
>Assignee: Otto Fowler
>Priority: Minor
>
> In the event of a successful call, QueryElasticsearchHttp always drops the
> incoming flowfile and then emits pages of results to the success
> relationship. If the search returns no results then no pages of results are
> emitted to the success relationship.
> The processor should offer other options for handling when there are no
> results returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi pull request #2601: NIFI-3576 Support for QueryInfo relationship, usefu...
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2601#discussion_r179217708
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/QueryElasticsearchHttp.java
---
@@ -68,8 +72,10 @@
+ "To retrieve more records, use the ScrollElasticsearchHttp
processor.")
@WritesAttributes({
@WritesAttribute(attribute = "filename", description = "The
filename attribute is set to the document identifier"),
+@WritesAttribute(attribute = "es.hitCount", description = "The
number of hits for a query"),
--- End diff --
nah, it is fine by me
---
[jira] [Commented] (NIFI-3576) QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship
[
https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425878#comment-16425878
]
ASF GitHub Bot commented on NIFI-3576:
--
Github user zenfenan commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2601#discussion_r179216547
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/QueryElasticsearchHttp.java
---
@@ -68,8 +72,10 @@
+ "To retrieve more records, use the ScrollElasticsearchHttp
processor.")
@WritesAttributes({
@WritesAttribute(attribute = "filename", description = "The
filename attribute is set to the document identifier"),
+@WritesAttribute(attribute = "es.hitCount", description = "The
number of hits for a query"),
--- End diff --
Just found out that some processors have used camel cases in writing
attributes. Sorry about that. Feel free to revert back although `es.hitcount`
itself looks good to me.
> QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship
>
>
> Key: NIFI-3576
> URL: https://issues.apache.org/jira/browse/NIFI-3576
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Joseph Percivall
>Assignee: Otto Fowler
>Priority: Minor
>
> In the event of a successful call, QueryElasticsearchHttp always drops the
> incoming flowfile and then emits pages of results to the success
> relationship. If the search returns no results then no pages of results are
> emitted to the success relationship.
> The processor should offer other options for handling when there are no
> results returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi pull request #2601: NIFI-3576 Support for QueryInfo relationship, usefu...
Github user zenfenan commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2601#discussion_r179216547
--- Diff:
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/QueryElasticsearchHttp.java
---
@@ -68,8 +72,10 @@
+ "To retrieve more records, use the ScrollElasticsearchHttp
processor.")
@WritesAttributes({
@WritesAttribute(attribute = "filename", description = "The
filename attribute is set to the document identifier"),
+@WritesAttribute(attribute = "es.hitCount", description = "The
number of hits for a query"),
--- End diff --
Just found out that some processors have used camel cases in writing
attributes. Sorry about that. Feel free to revert back although `es.hitcount`
itself looks good to me.
---
[jira] [Commented] (MINIFICPP-448) Allow uuid to be built & statically-linked
[ https://issues.apache.org/jira/browse/MINIFICPP-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425827#comment-16425827 ] ASF GitHub Bot commented on MINIFICPP-448: -- GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/294 MINIFICPP-448 Add uuid external/static link project 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-448 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/294.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 #294 commit 1f1e8f5421a9394464e67d2891fb19fb1c6dd5e9 Author: Andrew I. Christianson Date: 2018-04-04T16:41:07Z MINIFICPP-448 Add uuid external/static link project > Allow uuid to be built & statically-linked > -- > > Key: MINIFICPP-448 > URL: https://issues.apache.org/jira/browse/MINIFICPP-448 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Major > > We already bundle uuid code in nifi-minifi-cpp, but there is no way to build > it. The CMakeLists.txt should be updated to allow building of this bundled > uuid and statically-linking it, making it easier to run in environments where > uuid is not available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi-minifi-cpp pull request #294: MINIFICPP-448 Add uuid external/static li...
GitHub user achristianson opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/294 MINIFICPP-448 Add uuid external/static link project 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-448 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/pull/294.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 #294 commit 1f1e8f5421a9394464e67d2891fb19fb1c6dd5e9 Author: Andrew I. Christianson Date: 2018-04-04T16:41:07Z MINIFICPP-448 Add uuid external/static link project ---
[jira] [Created] (MINIFICPP-448) Allow uuid to be built & statically-linked
Andrew Christianson created MINIFICPP-448: - Summary: Allow uuid to be built & statically-linked Key: MINIFICPP-448 URL: https://issues.apache.org/jira/browse/MINIFICPP-448 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: Andrew Christianson Assignee: Andrew Christianson We already bundle uuid code in nifi-minifi-cpp, but there is no way to build it. The CMakeLists.txt should be updated to allow building of this bundled uuid and statically-linking it, making it easier to run in environments where uuid is not available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4185) Add XML record reader & writer services
[
https://issues.apache.org/jira/browse/NIFI-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425771#comment-16425771
]
ASF GitHub Bot commented on NIFI-4185:
--
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/2587
Hey @JohannesDaniel - just made new tests and can't reproduce what I saw
previously... so let's forget about it :) (thanks for the unit tests though!)
I tested the EL support for tag validation, working well, thanks for the
addition. I'd just make one suggestion: right now for the record tag, "in the
case of a mismatch, the respective record will be skipped". I'd suggest to make
this behavior configurable through a parameter in the CS: skip the record
(current behavior) or throw an exception for the flow file (as you're doing for
the root tag validation).
Regarding the performance test, it was a GFF => ConvertRecord (XML to JSON)
=> UpdateAttribute. Don't remember the exact numbers but IIRC it was around
1300 flowfile per second with an XML payload of 6KB (single record in my case).
Overall, it's really cool!
I'll try to have a look over the code during the week.
> Add XML record reader & writer services
> ---
>
> Key: NIFI-4185
> URL: https://issues.apache.org/jira/browse/NIFI-4185
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Affects Versions: 1.3.0
>Reporter: Andy LoPresto
>Assignee: Johannes Peter
>Priority: Major
> Labels: json, records, xml
>
> With the addition of the {{RecordReader}} and {{RecordSetWriter}} paradigm,
> XML conversion has not yet been targeted. This will replace the previous
> ticket for XML to JSON conversion.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi issue #2587: NIFI-4185 Add XML Record Reader
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2587 Hey @JohannesDaniel - just made new tests and can't reproduce what I saw previously... so let's forget about it :) (thanks for the unit tests though!) I tested the EL support for tag validation, working well, thanks for the addition. I'd just make one suggestion: right now for the record tag, "in the case of a mismatch, the respective record will be skipped". I'd suggest to make this behavior configurable through a parameter in the CS: skip the record (current behavior) or throw an exception for the flow file (as you're doing for the root tag validation). Regarding the performance test, it was a GFF => ConvertRecord (XML to JSON) => UpdateAttribute. Don't remember the exact numbers but IIRC it was around 1300 flowfile per second with an XML payload of 6KB (single record in my case). Overall, it's really cool! I'll try to have a look over the code during the week. ---
[jira] [Resolved] (MINIFICPP-440) Build & statically link libressl when not available in system
[ https://issues.apache.org/jira/browse/MINIFICPP-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Christianson resolved MINIFICPP-440. --- Resolution: Fixed > Build & statically link libressl when not available in system > - > > Key: MINIFICPP-440 > URL: https://issues.apache.org/jira/browse/MINIFICPP-440 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Andrew Christianson >Assignee: Andrew Christianson >Priority: Major > > In order to target systems where no SSL library is available, we should > support building & statically linking LibreSSL. This will help make MiNiFi - > C++ more portable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5034) Error in Controller Service with dynamic property in Cluster environment
[
https://issues.apache.org/jira/browse/NIFI-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425466#comment-16425466
]
Mark Bean commented on NIFI-5034:
-
Just to follow up: this fix was put on the system which originally experienced
the problem. The Controller Service with only dynamic properties and the UI
both functioning correctly. Thanks [~mcgilman]!.
> Error in Controller Service with dynamic property in Cluster environment
>
>
> Key: NIFI-5034
> URL: https://issues.apache.org/jira/browse/NIFI-5034
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.4.0, 1.5.0
>Reporter: Mark Bean
>Assignee: Matt Gilman
>Priority: Major
> Fix For: 1.6.0
>
>
> Environment: Controller Service provides a lookup service to other Controller
> Services. To configure, the lookup CS uses dynamic properties where the key
> is an arbitrary name and the value is an existing Controller Service.
> In a cluster environment only (this is not an issue for stand-alone
> environment), the UI displays returns "An unexpected error has occurred" due
> to http 500 return code. This occurs when attempting to configure the
> controller service with the dynamic property. Additionally, it throws the
> same error (http 500) when trying to configure the process group owning the
> lookup controller service. (The property on the controller service is created
> despite the 500 return code.)
> Diving into the code a bit, the fact of being a "cluster only" issue is in
> FlowResource.java:400.
> if (isReplicateRequest()) {
> return replicate(HttpMethod.GET);
> }
> The problem is the return value is null even when controller services exist.
> Ultimately, ApplicationResource.java:288 parses a map of http servlet
> parameters. The controller service should be a parameter. Yet, this map is
> empty.
> for (final Map.Entry entry :
> httpServletRequest.getParameterMap().entrySet()) \{ ... }
> This problem is preventing the implementation of a Controller Service with
> dynamic properties (whose property values are other Controller Services) in a
> cluster environment.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5041) Add convenient SPNEGO/Kerberos authentication support to LivySessionController
[ https://issues.apache.org/jira/browse/NIFI-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-5041: - Issue Type: Improvement (was: Bug) > Add convenient SPNEGO/Kerberos authentication support to LivySessionController > -- > > Key: NIFI-5041 > URL: https://issues.apache.org/jira/browse/NIFI-5041 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.5.0 >Reporter: Peter Toth >Priority: Minor > > Livy requires SPNEGO/Kerberos authentication on a secured cluster. Initiating > such an authentication from NiFi is a viable by providing a > java.security.auth.login.config system property > (https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/lab/part6.html), > but this is a bit cumbersome and needs kinit running outside of NiFi. > An alternative and more sophisticated solution would be to do the SPNEGO > negotiation programmatically. > * This solution would add some new properties to the LivySessionController > to fetch kerberos principal and password/keytab > * Add the required HTTP Negotiate header (with an SPNEGO token) to the > HttpURLConnection to do the authentication programmatically > (https://tools.ietf.org/html/rfc4559) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5041) Add convenient SPNEGO/Kerberos authentication support to LivySessionController
Peter Toth created NIFI-5041: Summary: Add convenient SPNEGO/Kerberos authentication support to LivySessionController Key: NIFI-5041 URL: https://issues.apache.org/jira/browse/NIFI-5041 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.5.0 Reporter: Peter Toth Livy requires SPNEGO/Kerberos authentication on a secured cluster. Initiating such an authentication from NiFi is a viable by providing a java.security.auth.login.config system property (https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/lab/part6.html), but this is a bit cumbersome and needs kinit running outside of NiFi. An alternative and more sophisticated solution would be to do the SPNEGO negotiation programmatically. * This solution would add some new properties to the LivySessionController to fetch kerberos principal and password/keytab * Add the required HTTP Negotiate header (with an SPNEGO token) to the HttpURLConnection to do the authentication programmatically (https://tools.ietf.org/html/rfc4559) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5027) CLI - Add a command to start controller services
[ https://issues.apache.org/jira/browse/NIFI-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425278#comment-16425278 ] ASF GitHub Bot commented on NIFI-5027: -- Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2604 Thanks @bbende. With your last changes: #> nifi pg-enable-services -pgid &2 -u http://localhost:8080 Using a positional back-reference for 'Test 2 - Misconfigured CS' Currently 0 enabled services and 1 disabled services, attempting to enable services... Finished with 0 enabled services and 1 disabled services The following services could not be enabled: Service: 016210d5-759f-1d4a-d095-69323147e9dd - StandardRestrictedSSLContextService Validation Errors: - 'StandardRestrictedSSLContextService : 016210d5-759f-1d4a-d095-69323147e9dd' is invalid because Does not have the KeyStore or the TrustStore populated #> #> nifi pg-enable-services -pgid &5 -u http://localhost:8080 Using a positional back-reference for 'Test 5 - Not referenced CS' Currently 0 enabled services and 2 disabled services, attempting to enable services... Currently 1 services are enabling, waiting to finish before proceeding (1 of 20) Currently 1 services are enabling, waiting to finish before proceeding (2 of 20) Currently 1 services are enabling, waiting to finish before proceeding (3 of 20) Currently 1 services are enabling, waiting to finish before proceeding (4 of 20) Currently 1 services are enabling, waiting to finish before proceeding (5 of 20) Currently 1 services are enabling, waiting to finish before proceeding (6 of 20) Currently 1 services are enabling, waiting to finish before proceeding (7 of 20) Currently 1 services are enabling, waiting to finish before proceeding (8 of 20) Currently 1 services are enabling, waiting to finish before proceeding (9 of 20) Currently 1 services are enabling, waiting to finish before proceeding (10 of 20) Currently 1 services are enabling, waiting to finish before proceeding (11 of 20) Currently 1 services are enabling, waiting to finish before proceeding (12 of 20) Currently 1 services are enabling, waiting to finish before proceeding (13 of 20) Currently 1 services are enabling, waiting to finish before proceeding (14 of 20) Currently 1 services are enabling, waiting to finish before proceeding (15 of 20) Currently 1 services are enabling, waiting to finish before proceeding (16 of 20) Currently 1 services are enabling, waiting to finish before proceeding (17 of 20) Currently 1 services are enabling, waiting to finish before proceeding (18 of 20) Currently 1 services are enabling, waiting to finish before proceeding (19 of 20) One or more services appear to be stuck enabling: Service: 016210ec-759f-1d4a-3cf3-c507e978ffc5 - DistributedMapCacheServer Reasons: - DistributedMapCacheServer[id=016210ec-759f-1d4a-3cf3-c507e978ffc5] Failed to invoke @OnEnabled method due to java.net.BindException: Address already in use: Address already in use - DistributedMapCacheServer[id=016210ec-759f-1d4a-3cf3-c507e978ffc5] Failed to invoke @OnEnabled method due to java.net.BindException: Address already in use: Address already in use That's great! Regarding the fact it's only displayed when using the interactive mode: I think it would make sense to also print it when using the "scripted" way (maybe just the error message you added with your last commit). I'd imagine users writing scripts redirecting the standard output to log files or using tools like Jenkins/Travis that already give you access to the standard output. If the script fails it would be useful to see what happened. Also, but I think it has already been mentioned in the previous PR for the CLI, having an exit code not equal to 0 could be useful to fail fast. Test 2: $ ./cli.sh nifi pg-enable-services -pgid 016210c2-759f-1d4a-c230-abfde87350cf -u http://localhost:8080 $ echo $? 0 > CLI - Add a command to start controller services > > > Key: NIFI-5027 > URL: https://issues.apache.org/jira/browse/NIFI-5027 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Pierre Villard >Assignee: Bryan Bende >Priority: Major > Attachments: TestStartStopCS.xml > > > When importing a versioned process group from the registry, all the > components will be stopped (in case of update, only the newly added > components will be stopped). We already have a command pg-start to start a > process group, but it will fail if the process gr
[GitHub] nifi issue #2604: NIFI-5027 Adding pg-get-services command
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2604 Thanks @bbende. With your last changes: #> nifi pg-enable-services -pgid &2 -u http://localhost:8080 Using a positional back-reference for 'Test 2 - Misconfigured CS' Currently 0 enabled services and 1 disabled services, attempting to enable services... Finished with 0 enabled services and 1 disabled services The following services could not be enabled: Service: 016210d5-759f-1d4a-d095-69323147e9dd - StandardRestrictedSSLContextService Validation Errors: - 'StandardRestrictedSSLContextService : 016210d5-759f-1d4a-d095-69323147e9dd' is invalid because Does not have the KeyStore or the TrustStore populated #> #> nifi pg-enable-services -pgid &5 -u http://localhost:8080 Using a positional back-reference for 'Test 5 - Not referenced CS' Currently 0 enabled services and 2 disabled services, attempting to enable services... Currently 1 services are enabling, waiting to finish before proceeding (1 of 20) Currently 1 services are enabling, waiting to finish before proceeding (2 of 20) Currently 1 services are enabling, waiting to finish before proceeding (3 of 20) Currently 1 services are enabling, waiting to finish before proceeding (4 of 20) Currently 1 services are enabling, waiting to finish before proceeding (5 of 20) Currently 1 services are enabling, waiting to finish before proceeding (6 of 20) Currently 1 services are enabling, waiting to finish before proceeding (7 of 20) Currently 1 services are enabling, waiting to finish before proceeding (8 of 20) Currently 1 services are enabling, waiting to finish before proceeding (9 of 20) Currently 1 services are enabling, waiting to finish before proceeding (10 of 20) Currently 1 services are enabling, waiting to finish before proceeding (11 of 20) Currently 1 services are enabling, waiting to finish before proceeding (12 of 20) Currently 1 services are enabling, waiting to finish before proceeding (13 of 20) Currently 1 services are enabling, waiting to finish before proceeding (14 of 20) Currently 1 services are enabling, waiting to finish before proceeding (15 of 20) Currently 1 services are enabling, waiting to finish before proceeding (16 of 20) Currently 1 services are enabling, waiting to finish before proceeding (17 of 20) Currently 1 services are enabling, waiting to finish before proceeding (18 of 20) Currently 1 services are enabling, waiting to finish before proceeding (19 of 20) One or more services appear to be stuck enabling: Service: 016210ec-759f-1d4a-3cf3-c507e978ffc5 - DistributedMapCacheServer Reasons: - DistributedMapCacheServer[id=016210ec-759f-1d4a-3cf3-c507e978ffc5] Failed to invoke @OnEnabled method due to java.net.BindException: Address already in use: Address already in use - DistributedMapCacheServer[id=016210ec-759f-1d4a-3cf3-c507e978ffc5] Failed to invoke @OnEnabled method due to java.net.BindException: Address already in use: Address already in use That's great! Regarding the fact it's only displayed when using the interactive mode: I think it would make sense to also print it when using the "scripted" way (maybe just the error message you added with your last commit). I'd imagine users writing scripts redirecting the standard output to log files or using tools like Jenkins/Travis that already give you access to the standard output. If the script fails it would be useful to see what happened. Also, but I think it has already been mentioned in the previous PR for the CLI, having an exit code not equal to 0 could be useful to fail fast. Test 2: $ ./cli.sh nifi pg-enable-services -pgid 016210c2-759f-1d4a-c230-abfde87350cf -u http://localhost:8080 $ echo $? 0 ---
[jira] [Created] (NIFI-5040) JsonPathExpressionValidator uses internal APIs that break with library upgrade
Mike Thomsen created NIFI-5040: -- Summary: JsonPathExpressionValidator uses internal APIs that break with library upgrade Key: NIFI-5040 URL: https://issues.apache.org/jira/browse/NIFI-5040 Project: Apache NiFi Issue Type: Improvement Reporter: Mike Thomsen JsonPathExpressionValidator uses a number of internal APIs from com.jayway.jsonpath. When I tried to upgrade from 2.0 to 2.2, JsonPathExpressionValidator broke due to several of the classes no longer being publicly accessible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-4517) Create a processor to allow SQL results to be output as records in any supported format (ExecuteSQLToRecord)
[ https://issues.apache.org/jira/browse/NIFI-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425243#comment-16425243 ] Ian Neethling edited comment on NIFI-4517 at 4/4/18 9:31 AM: - Hi [~mattyb149], do you think this will be a priority for Nifi 1.7.0? I'm not really all that familiar with contributing to Apache projects, but I have developed custom processors before and would be keen to help with this since with the various Schema Registries now available in Nifi a lot of resources could be saved by not including the embedded schema in the outputted flowfile, this would of course be configurable. was (Author: ioneethling): Hi [~mattyb149], do you think this will be a priority for Nifi 1.7.0? I'm not really all that familiar with contributing to Apache projects, but I have developed custom processors before and would be keen to help with this since with the various Schema Registries now available in Nifi a lot of resources could be saved by not including the embedded schema registry in the outputted flowfile, this would of course be configurable. > Create a processor to allow SQL results to be output as records in any > supported format (ExecuteSQLToRecord) > > > Key: NIFI-4517 > URL: https://issues.apache.org/jira/browse/NIFI-4517 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Burgess >Priority: Major > > ExecuteSQL currently only outputs Avro, and the schema is only available as > embedded within the flow file, not as an attribute such as record-aware > processors can handle. > I propose an ExecuteSQLToRecord processor that can be configured with a > RecordSetWriter implementation, or to change the existing ExecuteSQL > processor (although that might be more invasive and disruptive to existing > flows). This will allow output using any writer format (Avro, JSON, CSV, > Free-form text, etc.), as well as all the other features therein (such as > writing the schema to an attribute, and will avoid the need for a > ConvertAvroToXYZ or ConvertRecord processor downstream. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4517) Create a processor to allow SQL results to be output as records in any supported format (ExecuteSQLToRecord)
[ https://issues.apache.org/jira/browse/NIFI-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425243#comment-16425243 ] Ian Neethling commented on NIFI-4517: - Hi [~mattyb149], do you think this will be a priority for Nifi 1.7.0? I'm not really all that familiar with contributing to Apache projects, but I have developed custom processors before and would be keen to help with this since with the various Schema Registries now available in Nifi a lot of resources could be saved by not including the embedded schema registry in the outputted flowfile, this would of course be configurable. > Create a processor to allow SQL results to be output as records in any > supported format (ExecuteSQLToRecord) > > > Key: NIFI-4517 > URL: https://issues.apache.org/jira/browse/NIFI-4517 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Matt Burgess >Priority: Major > > ExecuteSQL currently only outputs Avro, and the schema is only available as > embedded within the flow file, not as an attribute such as record-aware > processors can handle. > I propose an ExecuteSQLToRecord processor that can be configured with a > RecordSetWriter implementation, or to change the existing ExecuteSQL > processor (although that might be more invasive and disruptive to existing > flows). This will allow output using any writer format (Avro, JSON, CSV, > Free-form text, etc.), as well as all the other features therein (such as > writing the schema to an attribute, and will avoid the need for a > ConvertAvroToXYZ or ConvertRecord processor downstream. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
