[GitHub] nifi-minifi-cpp pull request #31: MiNiFi-168 enable minifi cpp agents to be ...
GitHub user rkarthik29 opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/31 MiNiFi-168 enable minifi cpp agents to be able to receive flow files You can merge this pull request into a Git repository by running: $ git pull https://github.com/rkarthik29/nifi-minifi-cpp master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi-cpp/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 14ad33eb196a5a596bc77cfa389df2b3244881b6 Author: Kathik Narayanan Date: 2016-12-19T19:18:20Z receive flow files commit b2a514d1d075a97c0aeee98a4d8df9479ffb273c Author: Kathik Narayanan Date: 2016-12-21T04:39:33Z removed log warnings and errors commit d07e00f94fb08a0ddeb8a498e23d5017d3daa07b Author: Kathik Narayanan Date: 2016-12-21T04:52:26Z Merge branch 'master' of https://github.com/apache/nifi-minifi-cpp --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3010) Add expression language support for JoltTransformJson processor
[
https://issues.apache.org/jira/browse/NIFI-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765915#comment-15765915
]
ASF GitHub Bot commented on NIFI-3010:
--
GitHub user YolandaMDavis opened a pull request:
https://github.com/apache/nifi/pull/1348
NIFI-3010 - Incorporate Expression Language support for JoltTransformJSON
This PR contains several feature enhancements:
- Support of expression language within the specification
- Support of expression language testing using Advanced UI with new Test
Attributes dialog
- Update of Jolt library to version 0.1
- Added support for new Modifier library (Jolt Beta functionality)
For Testing:
Expression language can now be referenced within a Jolt Specification.
Expressions can be written on either side on the left hand side ( matching
input json keys) or the right hand side (output of json data) of the
specification. The Advanced UI can test expressions that reference attributes
using the Attributes dialog which allows users to provide key/value pairs that
will be resolved when testing a transformation.
https://cloud.githubusercontent.com/assets/1371858/21375258/4e9f1878-c6fa-11e6-9a45-2213e6f42107.png";>
https://cloud.githubusercontent.com/assets/1371858/21375261/52c60d44-c6fa-11e6-9fff-9e815c6e7ce9.png";>
Jolt 0.1 has added support for transformation of data within a given schema
through the Modifier library. Modifier introduces more sophisticated data
manipulation capabilities including for strings, lists, type conversion, etc.
https://cloud.githubusercontent.com/assets/1371858/21375249/4080ccb4-c6fa-11e6-8e34-c41c33644aa9.png";>
Below is an example chain specification that can be used against Twitter
payload for testing. When testing in the Advanced UI ensure that attributes
referenced in expression language are provided for testing (${rating.var} and
${id.var}) and that left side variable content match actual input (e.g. id.var
should equal 'id' for twitter json to match). Custom attributes can also be
configured with nifi to use this specification within an actual flow.
`
[{
"operation": "shift",
"spec": {
"created_at": "created_date_time",
"id": "tweet_id",
"text": "tweet_text",
"user": {
"${id.var}": "user_id"
}
}
},
{
"operation": "default",
"spec":{
"user-rating" : 4,
"twitter-rating" : "${rating.var}"
}
},{
"operation": "modify-default-beta",
"spec": {
"~in_reply_to_status_id": 0,
"~in_reply_to_status_id_str": 0,
"~in_reply_to_user_id": "",
"~in_reply_to_user_id_str": 0,
"~in_reply_to_screen_name": ""
}
},{
"operation": "modify-define-beta",
"spec": {
"user_nearby_address":"na"
}
},{
"operation": "modify-overwrite-beta",
"spec": {
"truncate" : true
}
}
]
`
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:
- [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 me
[GitHub] nifi pull request #1348: NIFI-3010 - Incorporate Expression Language support...
GitHub user YolandaMDavis opened a pull request:
https://github.com/apache/nifi/pull/1348
NIFI-3010 - Incorporate Expression Language support for JoltTransformJSON
This PR contains several feature enhancements:
- Support of expression language within the specification
- Support of expression language testing using Advanced UI with new Test
Attributes dialog
- Update of Jolt library to version 0.1
- Added support for new Modifier library (Jolt Beta functionality)
For Testing:
Expression language can now be referenced within a Jolt Specification.
Expressions can be written on either side on the left hand side ( matching
input json keys) or the right hand side (output of json data) of the
specification. The Advanced UI can test expressions that reference attributes
using the Attributes dialog which allows users to provide key/value pairs that
will be resolved when testing a transformation.
https://cloud.githubusercontent.com/assets/1371858/21375258/4e9f1878-c6fa-11e6-9a45-2213e6f42107.png";>
https://cloud.githubusercontent.com/assets/1371858/21375261/52c60d44-c6fa-11e6-9fff-9e815c6e7ce9.png";>
Jolt 0.1 has added support for transformation of data within a given schema
through the Modifier library. Modifier introduces more sophisticated data
manipulation capabilities including for strings, lists, type conversion, etc.
https://cloud.githubusercontent.com/assets/1371858/21375249/4080ccb4-c6fa-11e6-8e34-c41c33644aa9.png";>
Below is an example chain specification that can be used against Twitter
payload for testing. When testing in the Advanced UI ensure that attributes
referenced in expression language are provided for testing (${rating.var} and
${id.var}) and that left side variable content match actual input (e.g. id.var
should equal 'id' for twitter json to match). Custom attributes can also be
configured with nifi to use this specification within an actual flow.
`
[{
"operation": "shift",
"spec": {
"created_at": "created_date_time",
"id": "tweet_id",
"text": "tweet_text",
"user": {
"${id.var}": "user_id"
}
}
},
{
"operation": "default",
"spec":{
"user-rating" : 4,
"twitter-rating" : "${rating.var}"
}
},{
"operation": "modify-default-beta",
"spec": {
"~in_reply_to_status_id": 0,
"~in_reply_to_status_id_str": 0,
"~in_reply_to_user_id": "",
"~in_reply_to_user_id_str": 0,
"~in_reply_to_screen_name": ""
}
},{
"operation": "modify-define-beta",
"spec": {
"user_nearby_address":"na"
}
},{
"operation": "modify-overwrite-beta",
"spec": {
"truncate" : true
}
}
]
`
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:
- [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/YolandaMDavis/nifi NIFI-3010
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1348.patch
To close
[jira] [Commented] (NIFI-2585) Add attributes to track where a flow file came from when receiving over site-to-site
[ https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765671#comment-15765671 ] ASF GitHub Bot commented on NIFI-2585: -- Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/1342 @bbende Thanks for the comment. I reconsidered about s2s.address property, and by focusing only on the downstream flow, I think it probably doesn't matter whether the flow file came into the flow either by pulling or receiving it. If one needs to distinguish the direction in downstream flow, they can do so by adding UpdateAttribute to add whatever context they need. I think it's better to keep the number of attributes that NiFi framework create automatically at minimum. Removing feature from framework may be harder than adding it. So, I will keep the attribute names as they are now. Will update the PR with additional unit tests later. Thanks! > Add attributes to track where a flow file came from when receiving over > site-to-site > > > Key: NIFI-2585 > URL: https://issues.apache.org/jira/browse/NIFI-2585 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Randy Gelhausen >Priority: Minor > > With MiNiFi starting be used to send data to a central NiFi, it would be > helpful if information about the sending host and port was added to each flow > file received over site-to-site. Currently this information is available and > used to generate the transit URI in the RECEIVE event, but this information > isn't available to downstream processors that might want to make routing > decisions. > For reference: > https://github.com/apache/nifi/blob/e23b2356172e128086585fe2c425523c3628d0e7/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/protocol/AbstractFlowFileServerProtocol.java#L452 > A possible approach might be to add two attributes to each flow file, > something like "remote.host" and "remote.address" where remote.host has only > the sending hostname, and remote.address has the sending host and port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #1342: NIFI-2585 Add attributes to track s2s host and port
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/1342 @bbende Thanks for the comment. I reconsidered about s2s.address property, and by focusing only on the downstream flow, I think it probably doesn't matter whether the flow file came into the flow either by pulling or receiving it. If one needs to distinguish the direction in downstream flow, they can do so by adding UpdateAttribute to add whatever context they need. I think it's better to keep the number of attributes that NiFi framework create automatically at minimum. Removing feature from framework may be harder than adding it. So, I will keep the attribute names as they are now. Will update the PR with additional unit tests later. Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-3238) ListenLumberjack should support the *beat protocol
Andre created NIFI-3238: --- Summary: ListenLumberjack should support the *beat protocol Key: NIFI-3238 URL: https://issues.apache.org/jira/browse/NIFI-3238 Project: Apache NiFi Issue Type: Improvement Reporter: Andre ListenLumberjack currently only supports v1 of the Lumberjack protocol. This version has been deprecated in favor of v2, which is used on *beat (e.g. filebeat, packetbeat, etc) edge components of the ELK stack. We should consider deprecating ListenLumberjack or to extend it to handle both v1 and v2 of the protocol. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-3237) Store hostname and UI port of cluster nodes in ZK
Jeff Storck created NIFI-3237: - Summary: Store hostname and UI port of cluster nodes in ZK Key: NIFI-3237 URL: https://issues.apache.org/jira/browse/NIFI-3237 Project: Apache NiFi Issue Type: New Feature Components: Core Framework Reporter: Jeff Storck Priority: Minor Cluster node information (hostname and UI port) should be available in ZooKeeper. This would make it easier to configure services that produce to or consume data from NiFi. A couple examples: * External producers to NiFi that send data to the Primary Node and need to be able to dynamically respond to changes of the Primary node without requiring manual configuration * Dynamically configured haproxy instances that aim to load-balance requests across the nodes of a NiFi cluster -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3071) Consider deprecating org.apache.nifi.stream.io.ByteArrayOutputStream in favor of java.io.ByteArrayOutputStream
[ https://issues.apache.org/jira/browse/NIFI-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre updated NIFI-3071: Summary: Consider deprecating org.apache.nifi.stream.io.ByteArrayOutputStream in favor of java.io.ByteArrayOutputStream (was: Consider deprecating org.apache.nifi.stream.io.ByteArrayOutputStream in favor of jaba.io.ByteArrayOutputStream) > Consider deprecating org.apache.nifi.stream.io.ByteArrayOutputStream in favor > of java.io.ByteArrayOutputStream > -- > > Key: NIFI-3071 > URL: https://issues.apache.org/jira/browse/NIFI-3071 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Oleg Zhurakousky >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.2.0, 1.1.1 > > > I believe the "efficiency" statements need to be revisited. For example, > preliminary testing shows that there are no performance difference between > using the one provided with java.io. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3234) Fix two broken links in the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Percivall updated NIFI-3234: --- Resolution: Fixed Fix Version/s: 1.2.0 Status: Resolved (was: Patch Available) > Fix two broken links in the Admin Guide > --- > > Key: NIFI-3234 > URL: https://issues.apache.org/jira/browse/NIFI-3234 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.1.0 >Reporter: Sarah Olson >Assignee: Sarah Olson >Priority: Minor > Fix For: 1.2.0 > > > Several external links in the below section are broken. Update with > appropriate new links. > http://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encryption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1345: NIFI-3234: Updated two broken links in the Encrypti...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1345 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3234) Fix two broken links in the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765481#comment-15765481 ] ASF GitHub Bot commented on NIFI-3234: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1345 > Fix two broken links in the Admin Guide > --- > > Key: NIFI-3234 > URL: https://issues.apache.org/jira/browse/NIFI-3234 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.1.0 >Reporter: Sarah Olson >Assignee: Sarah Olson >Priority: Minor > > Several external links in the below section are broken. Update with > appropriate new links. > http://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encryption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3234) Fix two broken links in the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765478#comment-15765478 ] ASF subversion and git services commented on NIFI-3234: --- Commit 00149603c81593b502f8527f9b1d4c247499f60a in nifi's branch refs/heads/master from [~solson75] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0014960 ] NIFI-3234: Updated two broken links in the Encryption Configuration sectionof the Admin Guide This closes #1345 Signed-off-by: jpercivall > Fix two broken links in the Admin Guide > --- > > Key: NIFI-3234 > URL: https://issues.apache.org/jira/browse/NIFI-3234 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.1.0 >Reporter: Sarah Olson >Assignee: Sarah Olson >Priority: Minor > > Several external links in the below section are broken. Update with > appropriate new links. > http://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encryption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #1345: NIFI-3234: Updated two broken links in the Encryption Conf...
Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/1345 +1 Changes appear in line with the intended description of links. Thanks @thesolson I will merge it in. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3234) Fix two broken links in the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765454#comment-15765454 ] ASF GitHub Bot commented on NIFI-3234: -- Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/1345 +1 Changes appear in line with the intended description of links. Thanks @thesolson I will merge it in. > Fix two broken links in the Admin Guide > --- > > Key: NIFI-3234 > URL: https://issues.apache.org/jira/browse/NIFI-3234 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.1.0 >Reporter: Sarah Olson >Assignee: Sarah Olson >Priority: Minor > > Several external links in the below section are broken. Update with > appropriate new links. > http://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encryption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1347: NIFI-3236 - SplitJson performance improvements
Github user brosander closed the pull request at: https://github.com/apache/nifi/pull/1347 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3236) SplitJson performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765438#comment-15765438 ] ASF GitHub Bot commented on NIFI-3236: -- Github user brosander closed the pull request at: https://github.com/apache/nifi/pull/1347 > SplitJson performance improvements > -- > > Key: NIFI-3236 > URL: https://issues.apache.org/jira/browse/NIFI-3236 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > SplitJson does a lot of work in every onTrigger() that it doesn't need to. > This includes putting each attribute separately as well as looping over the > output segments twice. > It also fetches a property in onTrigger() that could be gotten in an > @OnScheduled method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3236) SplitJson performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765417#comment-15765417 ] ASF GitHub Bot commented on NIFI-3236: -- GitHub user brosander opened a pull request: https://github.com/apache/nifi/pull/1347 NIFI-3236 - SplitJson performance improvements 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] - N/A - Functionality already covered by tests - Have you written or updated unit tests to verify your changes? - [X] - N/A - 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] - N/A - If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [X] - N/A - If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [X] - N/A - If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [X] - N/A - 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/brosander/nifi NIFI-3236 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1347.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 #1347 commit 026397d6defd533a10436f77fd760d2110107a82 Author: Bryan Rosander Date: 2016-12-20T21:39:22Z NIFI-3236 - SplitJson performance improvements > SplitJson performance improvements > -- > > Key: NIFI-3236 > URL: https://issues.apache.org/jira/browse/NIFI-3236 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > SplitJson does a lot of work in every onTrigger() that it doesn't need to. > This includes putting each attribute separately as well as looping over the > output segments twice. > It also fetches a property in onTrigger() that could be gotten in an > @OnScheduled method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1347: NIFI-3236 - SplitJson performance improvements
GitHub user brosander opened a pull request: https://github.com/apache/nifi/pull/1347 NIFI-3236 - SplitJson performance improvements 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] - N/A - Functionality already covered by tests - Have you written or updated unit tests to verify your changes? - [X] - N/A - 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] - N/A - If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [X] - N/A - If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [X] - N/A - If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [X] - N/A - 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/brosander/nifi NIFI-3236 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1347.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 #1347 commit 026397d6defd533a10436f77fd760d2110107a82 Author: Bryan Rosander Date: 2016-12-20T21:39:22Z NIFI-3236 - SplitJson performance improvements --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-3236) SplitJson performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Rosander updated NIFI-3236: - Attachment: after.png before.png > SplitJson performance improvements > -- > > Key: NIFI-3236 > URL: https://issues.apache.org/jira/browse/NIFI-3236 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > SplitJson does a lot of work in every onTrigger() that it doesn't need to. > This includes putting each attribute separately as well as looping over the > output segments twice. > It also fetches a property in onTrigger() that could be gotten in an > @OnScheduled method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-3236) SplitJson performance improvements
Bryan Rosander created NIFI-3236: Summary: SplitJson performance improvements Key: NIFI-3236 URL: https://issues.apache.org/jira/browse/NIFI-3236 Project: Apache NiFi Issue Type: Improvement Reporter: Bryan Rosander Assignee: Bryan Rosander Priority: Minor SplitJson does a lot of work in every onTrigger() that it doesn't need to. This includes putting each attribute separately as well as looping over the output segments twice. It also fetches a property in onTrigger() that could be gotten in an @OnScheduled method. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3234) Fix two broken links in the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Olson updated NIFI-3234: -- Status: Patch Available (was: Open) https://github.com/apache/nifi/pull/1345 > Fix two broken links in the Admin Guide > --- > > Key: NIFI-3234 > URL: https://issues.apache.org/jira/browse/NIFI-3234 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website >Affects Versions: 1.1.0 >Reporter: Sarah Olson >Assignee: Sarah Olson >Priority: Minor > > Several external links in the below section are broken. Update with > appropriate new links. > http://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encryption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Rosander updated NIFI-3235: - Description: EvaluateJsonPath does a lot of work in every onTrigger() that can be done when scheduled. This has the effect of making it take more cpu cycles than necessary to do its job. Initializing the -JsonPath objects in a ThreadLocal- recycling JsonPath objects from a queue and getting the properties from the ProcessContext a single time in onSchedule() should reduce the amount of CPU time this processor needs to perform a given task. was: EvaluateJsonPath does a lot of work in every onTrigger() that can be done when scheduled. This has the effect of making it take more cpu cycles than necessary to do its job. Initializing the JsonPath objects in a ThreadLocal and getting the properties from the ProcessContext a single time in onSchedule() should reduce the amount of CPU time this processor needs to perform a given task. > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the -JsonPath objects in a ThreadLocal- recycling JsonPath > objects from a queue and getting the properties from the ProcessContext a > single time in onSchedule() should reduce the amount of CPU time this > processor needs to perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi-minifi pull request #68: MINIFI-128 Adjusting handling of change ingest...
GitHub user apiri opened a pull request: https://github.com/apache/nifi-minifi/pull/68 MINIFI-128 Adjusting handling of change ingestor configuration and error messaging. MINIFI-128 Adjusting handling of change ingestor configuration and error messaging. Thank you for submitting a contribution to Apache NiFi - MiNiFi. 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 ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi-minifi 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 minifi-assembly? - [-] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly? ### 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/apiri/nifi-minifi MINIFI-128 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/68.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 #68 commit ab43706e6ec21a633e587681ecccadddfeb4b829 Author: Aldrin Piri Date: 2016-12-20T20:42:03Z MINIFI-128 Adjusting handling of change ingestor configuration and error messaging. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi-minifi pull request #67: MINIFI-144 Bumping logback version to 1.1.8
GitHub user JPercivall opened a pull request: https://github.com/apache/nifi-minifi/pull/67 MINIFI-144 Bumping logback version to 1.1.8 You can merge this pull request into a Git repository by running: $ git pull https://github.com/JPercivall/nifi-minifi MINIFI-144 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/67.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 #67 commit 33b41d1134b1c9cfb15709b670d342b376967887 Author: Joseph Percivall Date: 2016-12-20T20:43:51Z MINIFI-144 Bumping logback version to 1.1.8 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765157#comment-15765157 ] ASF GitHub Bot commented on NIFI-3235: -- GitHub user brosander reopened a pull request: https://github.com/apache/nifi/pull/1346 NIFI-3235 - EvaluateJsonPath performance improvements 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] - N/A - Tests already cover changes - Have you written or updated unit tests to verify your changes? - [X] - N/A - 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] - N/A - If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [X] - N/A - If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [X] - N/A - If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [X] - N/A - 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/brosander/nifi NIFI-3235 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1346.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 #1346 commit ae2185709faec01d32d7af363a42bac2345d72b7 Author: Bryan Rosander Date: 2016-12-20T17:29:15Z NIFI-3235 - EvaluateJsonPath performance improvements > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the JsonPath objects in a ThreadLocal and getting the properties > from the ProcessContext a single time in onSchedule() should reduce the > amount of CPU time this processor needs to perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1346: NIFI-3235 - EvaluateJsonPath performance improvemen...
GitHub user brosander reopened a pull request: https://github.com/apache/nifi/pull/1346 NIFI-3235 - EvaluateJsonPath performance improvements 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] - N/A - Tests already cover changes - Have you written or updated unit tests to verify your changes? - [X] - N/A - 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] - N/A - If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [X] - N/A - If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [X] - N/A - If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [X] - N/A - 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/brosander/nifi NIFI-3235 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1346.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 #1346 commit ae2185709faec01d32d7af363a42bac2345d72b7 Author: Bryan Rosander Date: 2016-12-20T17:29:15Z NIFI-3235 - EvaluateJsonPath performance improvements --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (NIFI-1323) UI visual design enhancement
[ https://issues.apache.org/jira/browse/NIFI-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran resolved NIFI-1323. - Resolution: Done > UI visual design enhancement > > > Key: NIFI-1323 > URL: https://issues.apache.org/jira/browse/NIFI-1323 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Trivial > Attachments: flowfont.zip, nifi-add-processor-dialog.png, > nifi-component-samples.png, > nifi-configure-processor-properties-set-value.png, > nifi-configure-processor-properties.png, > nifi-configure-processor-scheduling.png, > nifi-configure-processor-settings.png, nifi-dialog-samp...@800px.png, > nifi-drag-drop-compon...@2x.png, nifi-global-menu-pending-u...@2x.png, > nifi-global-menu.png, nifi-interaction-and-menu-samples.png, > nifi-lineage-gra...@800px.png, nifi-sample-fl...@800px.png, > nifi-sample-flow.png, nifi-search-resu...@2x.png, nifi-shell-samp...@800px.png > > > (I will attach mockups and supporting files as they become available) > I am starting to work on a design to modernize the look and feel of the NiFi > UI. The initial focus of the design is to freshen the UI (flat design, SVG > icons, etc.). Additionally, the new design will propose usability > improvements such as exposing more flow-related actions into collapsible > panes, improving hierarchy of information, etc. > Going forward, the design plan is to help lay the foundation for other UI/UX > related issues such as those documented in NIFI-951. > --- > *flowfont.zip* > Contains icon font and supporting files > *nifi-add-processor-dialog.png* > Dialog sample. This sample shows the 'Add Processor' dialog. > *nifi-component-samples.png* > To show styling for all components, as well as those components when a user > is unauthorized to access. > *nifi-configure-processor-properties* > *nifi-configure-processor-properties-set-value* > *nifi-configure-processor-scheduling* > *nifi-configure-processor-settings* > Configure Processor dialog. See related Comments below (in Activity section). > *nifi-dialog-sample-@800px* > Dialog sample in 800px wide viewport. This sample shows the the 'Details' tab > of a provenance event. > *nifi-drag-drop-component@2x* > To show updated component toolbar button style and user interaction > improvements > *nifi-drop.svg* > NiFi logo without 'nifi > *nifi-global-menu* > To show global menu > *nifi-global-menu-pending-user@2x* > Demonstrates a generic notification with an aggregate count that appears on > the global menu icon. When the menu is displayed, the same notification (and > individual count) appears in line with the corresponding item. > *nifi-interaction-and-menu-samples.png* > To demonstrate user interactions - hover states, tooltips, menus, etc. > *nifi-lineage-graph-@800px* > To show lineage graph with explicit action to get back to data provenance > event list. > *nifi-sample-flow-@800px* > Shows a very useable UI down to around 800px in width. The thinking here is > that at anything lower than this, the NiFi user experience will change to > more of a monitoring and/or administrative type workflow. Future mockups will > be created to illustrate this. > *nifi-logo.svg* > NiFi logo complete > *nifi-sample-flow.png* > Mockup of sample flow. Updated to show revised tool and status bars. > Management related actions will move to a menu via mouseover (see > _nifi-global-menu_). Added benefits here include reducing clutter and more > user-friendly menu with text labels to reduce time spent scanning only a > large set of icons. This also helps gain valuable viewport width in a browser > (see _nifi-sample-flow-@800px_) > *nifi-search-resu...@2x.png* > Search results example > *nifi-shell-sample-@800px* > Shell sample in 800px wide viewport. This sample shows the 'Data Provenance' > table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1593) New Processor to make use of a template engine
[ https://issues.apache.org/jira/browse/NIFI-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1593: -- Component/s: (was: Core UI) Extensions > New Processor to make use of a template engine > -- > > Key: NIFI-1593 > URL: https://issues.apache.org/jira/browse/NIFI-1593 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Affects Versions: 0.4.1 > Environment: all >Reporter: Uwe Geercken >Priority: Minor > > Add a new processor that allows to use the functionality of a template engine > such as Apache Velocity. > The user would provide either the template code or reference a template file. > In the process the flowfile content/attributes would be merged with the > template and thus transforming the content. > A use case would be: > Get a Json file >> EvaluateJsonPath >> transform the attributes of the Json > file to a different format using the given template code or template file > (using the template engine) >> conversion into any other text based format > such as xml, html, text. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1608) Enahncements to PutMongo Processor
[ https://issues.apache.org/jira/browse/NIFI-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1608: -- Component/s: (was: Core UI) Extensions > Enahncements to PutMongo Processor > -- > > Key: NIFI-1608 > URL: https://issues.apache.org/jira/browse/NIFI-1608 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 0.5.1 > Environment: all >Reporter: Uwe Geercken >Priority: Minor > > Mongodb allows to update an existing document by replacing it completely or > by using the $set operator to update all or parts of the document. When an > update to an existing document is made but the update does not contain all > fields of the document, then those fields are lost/deleted. > The PutMongo processor does a complete replacement of an existing document. > The request is to enhance the functionality to allow updates of parts of the > document. > This would allow to e.g. insert a document and later doing updates to parts > of the document. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1611) Enhancements to PutMongo processor: Upserts
[ https://issues.apache.org/jira/browse/NIFI-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1611: -- Component/s: (was: Core UI) Extensions > Enhancements to PutMongo processor: Upserts > --- > > Key: NIFI-1611 > URL: https://issues.apache.org/jira/browse/NIFI-1611 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 0.5.1 > Environment: all >Reporter: Uwe Geercken >Priority: Minor > > The current implementation of the PutMongo processor does not allow to use > operators such as $push or $inc. > Enhance the processor to allow the use of mongodb operators to allow a more > flexible usage. > As mongodb has a lot of these operators maybe an idea would be to allow a > "raw" mode, where the content of the Json document is directly sent to > mongodb as-is and thus is executed as-is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1641) NiFi UI - Processor properties not rendered initially
[ https://issues.apache.org/jira/browse/NIFI-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1641. --- Resolution: Cannot Reproduce The issue seems to have been addressed. > NiFi UI - Processor properties not rendered initially > - > > Key: NIFI-1641 > URL: https://issues.apache.org/jira/browse/NIFI-1641 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Matt Gilman >Priority: Minor > > It appears at times some Processor properties are not rendered when the > dialog is opened initially. Upon scrolling all properties appear. This is > likely due to the usage of slickgrid where the dataview is updated but the > grid is not redrawn. Will need to evaluate further to be sure. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1720) Add icon for scheduled (idle) processors
[ https://issues.apache.org/jira/browse/NIFI-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1720. --- Resolution: Not A Problem Closing as the scheduled state and active threads provide the desired breakdown. > Add icon for scheduled (idle) processors > > > Key: NIFI-1720 > URL: https://issues.apache.org/jira/browse/NIFI-1720 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Ian Hellstrom >Priority: Minor > > Processors currently only show the green "Play" icon to indicate that they > are running or the red "Stop" icon to indicate they have been stopped. It > would be nice for processors that run on a schedule to have a "Pause" (or > "Stopwatch" / "Clock") icon to indicate that they are running but due to the > schedule currently inactive/idle. > This would make it slightly easier to debug schedule problems and see what's > happening in real-time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2922) Ability to clear bulletins on a per-processor basis
[
https://issues.apache.org/jira/browse/NIFI-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman resolved NIFI-2922.
---
Resolution: Duplicate
> Ability to clear bulletins on a per-processor basis
> ---
>
> Key: NIFI-2922
> URL: https://issues.apache.org/jira/browse/NIFI-2922
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework, Core UI
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Andy LoPresto
>Priority: Trivial
> Labels: bulletins, ui
>
> Often when testing or verifying a change in processor properties, etc., I
> will run a "negative" flow (a flow I expect to result in some type of error
> case, generate bulletins, etc.) and then change the setting under examination
> and re-run. In this case, I would like to be able to quickly clear the
> existing bulletins from the processor under examination in order to be able
> to determine if the issue is resolved without having to manually examine
> timestamps in the bulletins/wait for the 5 minute bulletin expiration to age
> off the existing bulletins.
> I imagine this being implemented as a REST API (likely {{PUT}}/{{DELETE}} on
> {{/processors/{id}/bulletins}}) which could be invoked via a context menu
> item or a dedicated button in the Operate palette.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-2056) Support clearing bulletins from processors via right-click context menu
[ https://issues.apache.org/jira/browse/NIFI-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2056: -- Priority: Minor (was: Major) > Support clearing bulletins from processors via right-click context menu > --- > > Key: NIFI-2056 > URL: https://issues.apache.org/jira/browse/NIFI-2056 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Randy Gelhausen >Priority: Minor > Attachments: Screen Shot 2016-06-18 at 5.29.30 PM.png > > > Since most bulletins of error or warning type are lengthy, it takes only 2-3 > bulletins to cause display to extend below the bottom of the screen. > It's common to iteratively edit processor configuration and test for desired > effect. When the desired setup is finished, processors will continue > displaying bulletins for 5 minutes, leading users to be unsure whether new > errors/warnings are coming in, or whether they're old and can be ignored. > NiFi's UI should support "clearing" bulletins from processors via a right > click menu. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2073) Test new flowfont
[ https://issues.apache.org/jira/browse/NIFI-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2073. --- Resolution: Won't Fix Opted for initial flowfont. > Test new flowfont > - > > Key: NIFI-2073 > URL: https://issues.apache.org/jira/browse/NIFI-2073 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Moran > Attachments: flowfont.zip > > > Need to test new flowfont files to see if positioning issues still exist. > _flowfont.zip is attached_ > This new version was generated with revised sizing, export settings, and > minor design updates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2132) New scheduler slider
[ https://issues.apache.org/jira/browse/NIFI-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2132: -- Priority: Minor (was: Major) > New scheduler slider > > > Key: NIFI-2132 > URL: https://issues.apache.org/jira/browse/NIFI-2132 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Minor > > scheduler slider need refresh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2110) Queue Position doesn't show up in List Queue Details dialog
[ https://issues.apache.org/jira/browse/NIFI-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2110: -- Priority: Minor (was: Major) > Queue Position doesn't show up in List Queue Details dialog > --- > > Key: NIFI-2110 > URL: https://issues.apache.org/jira/browse/NIFI-2110 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Burgess >Priority: Minor > Attachments: no-queue-position.png > > > After bringing up the List Queue dialog, if you select an entry and click the > View Details button, on the Details tab there is a Queue Position field but > it always reads "no value set" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2202) Read Only User/Group Management
[ https://issues.apache.org/jira/browse/NIFI-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2202. --- Resolution: Fixed Fix Version/s: 1.1.0 > Read Only User/Group Management > --- > > Key: NIFI-2202 > URL: https://issues.apache.org/jira/browse/NIFI-2202 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Matt Gilman > Fix For: 1.1.0 > > > Update the User/Group management page to support users with read only > permissions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2312) set different colors also for Processor groups
[ https://issues.apache.org/jira/browse/NIFI-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2312: -- Priority: Minor (was: Major) > set different colors also for Processor groups > -- > > Key: NIFI-2312 > URL: https://issues.apache.org/jira/browse/NIFI-2312 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Alexander Kell >Priority: Minor > Labels: features, usability > > It is already possible to change the color of processors , unfortunately this > is not possible for processorgroups , it would be really helpful to keep the > overview of data flows by having different colors also for groups -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2314) UI - Consistent Dialog Resizing
[ https://issues.apache.org/jira/browse/NIFI-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2314: -- Priority: Trivial (was: Minor) > UI - Consistent Dialog Resizing > --- > > Key: NIFI-2314 > URL: https://issues.apache.org/jira/browse/NIFI-2314 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Priority: Trivial > > For dialogs that support resizing, that behavior should be consistent. The > stats history resizing originates from the center of the screen while the > property value dialogs expand down and to the right. > Possibly consider using center oriented throughout the application to further > increase consistency with regards to dialog positioning/draggable behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2408) If a node is disconnected, it should still provide user ability to see the 'cluster screen'
[ https://issues.apache.org/jira/browse/NIFI-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2408: -- Priority: Minor (was: Major) > If a node is disconnected, it should still provide user ability to see the > 'cluster screen' > --- > > Key: NIFI-2408 > URL: https://issues.apache.org/jira/browse/NIFI-2408 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Matt Gilman >Priority: Minor > > A decision was made a while back that if a node is disconnected from the > cluster, the 'cluster screen' should not be available in the menu in the > top-right corner. However, after using the app like this, I now think it was > a bad decision. The node is still part of the cluster, even though it is > disconnected. Unless the user clicks 'remove', the node is a part of the > cluster, so should be able to render the cluster information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2723) UI - Decouple component and status refresh
[ https://issues.apache.org/jira/browse/NIFI-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2723. --- Resolution: Won't Fix Decoupling no longer necessary as each client tracks outstanding requests that was previously causing issues with large responses when the configuration and status were combined. > UI - Decouple component and status refresh > -- > > Key: NIFI-2723 > URL: https://issues.apache.org/jira/browse/NIFI-2723 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Priority: Minor > > Currently, the UI refreshes a component and it's status together. This logic > should be decoupled so we can update the status without running through the > logic to update the component. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2753) HttpServletRequest / HTTP Context Map
[ https://issues.apache.org/jira/browse/NIFI-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2753. --- Resolution: Not A Bug Created a new JIRA to improve the UX around Controller Services in 1.x. See referenced JIRA. > HttpServletRequest / HTTP Context Map > - > > Key: NIFI-2753 > URL: https://issues.apache.org/jira/browse/NIFI-2753 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 > Environment: Chrome 55, Nifi 1.0.0, Java 1.8.0_102, Windows 10 >Reporter: Curtis Ruck >Priority: Minor > > When trying to create a HandleHttpRequest -> HandleHttpResponse I am unable > to create a new HTTP Context Map object and use it to start the > HandleHttpRequest or HandleHttpResponse processors. When creating a new HTTP > Context Map within the HandleHttpRequest editor, it doesn't show in the > Controller Services pane to enable, and when creating the > StandardHttpContextMap in the Controller Services pane, it is unable to be > selected in the HandleHttpRequest and HandleHttpResponse editor. This > renders these processors useless, since they can't be started without a HTTP > Context Map that is enabled for them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2974) Populate default values in SSLContextService creation dialog
[
https://issues.apache.org/jira/browse/NIFI-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-2974:
--
Component/s: (was: Core UI)
Extensions
> Populate default values in SSLContextService creation dialog
>
>
> Key: NIFI-2974
> URL: https://issues.apache.org/jira/browse/NIFI-2974
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Priority: Trivial
> Labels: beginner, tls, ui
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When users create a {{SSLContextService}}, some common default values could
> be auto-populated:
> * {{Keystore location}} - {{$NIFI_HOME/conf/keystore.jks}}
> * {{Keystore Type}} - {{JKS}}
> * {{Truststore location}} - {{$NIFI_HOME/conf/truststore.jks}}
> * {{Truststore Type}} - {{JKS}}
> These are the default values when using the TLS Toolkit and safe defaults for
> manual generation as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2990) Access Policies: Link for process group should navigate to the Access Policies window for that process group
[ https://issues.apache.org/jira/browse/NIFI-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764954#comment-15764954 ] Matt Gilman commented on NIFI-2990: --- While requiring an extra click or two, I think that navigating back to the component on the canvas is actually a good thing. It allows the user to re-orient themselves with the component in question in the context of the data flow and not simply rely on a potentially ambiguous name. > Access Policies: Link for process group should navigate to the Access > Policies window for that process group > - > > Key: NIFI-2990 > URL: https://issues.apache.org/jira/browse/NIFI-2990 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.1.0 >Reporter: Andrew Lim > > Currently, the link takes you to that process group being selected in the > canvas. So if the user wants to modify the access policies on that PG, > he/she has to select the "key" icon in the Operate Palette. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764934#comment-15764934 ] ASF GitHub Bot commented on NIFI-3235: -- Github user brosander commented on the issue: https://github.com/apache/nifi/pull/1346 Closing to get rid of thread local > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the JsonPath objects in a ThreadLocal and getting the properties > from the ProcessContext a single time in onSchedule() should reduce the > amount of CPU time this processor needs to perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764935#comment-15764935 ] ASF GitHub Bot commented on NIFI-3235: -- Github user brosander closed the pull request at: https://github.com/apache/nifi/pull/1346 > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the JsonPath objects in a ThreadLocal and getting the properties > from the ProcessContext a single time in onSchedule() should reduce the > amount of CPU time this processor needs to perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1346: NIFI-3235 - EvaluateJsonPath performance improvemen...
Github user brosander closed the pull request at: https://github.com/apache/nifi/pull/1346 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi issue #1346: NIFI-3235 - EvaluateJsonPath performance improvements
Github user brosander commented on the issue: https://github.com/apache/nifi/pull/1346 Closing to get rid of thread local --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3115) Enhance user policy management functionality
[
https://issues.apache.org/jira/browse/NIFI-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764912#comment-15764912
]
Matt Gilman commented on NIFI-3115:
---
May be a good idea to break this apart into many sub-tasks that can be
implemented independently.
> Enhance user policy management functionality
>
>
> Key: NIFI-3115
> URL: https://issues.apache.org/jira/browse/NIFI-3115
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework, Core UI
>Affects Versions: 1.1.0
>Reporter: Andy LoPresto
>Priority: Critical
> Labels: dac, permissions, policy, rbac, user
> Attachments: Screen Shot 2016-11-28 at 6.57.43 PM.png
>
>
> With the multi-tenant authorization model introduced in version 1.1.0, NiFi
> has moved from role-based access control (RBAC) to a more granular
> combination of discretionary access control (DAC) (permissions based on
> individual user credentials combined with membership in groups) and
> permission-based access control (granting explicit behavioral access on
> individual resources to specific users and groups). See [Overview of Access
> Control Models|https://www.owasp.org/index.php/Access_Control_Cheat_Sheet]
> for more details.
> Because of this change, centralized management of user permissions ("policy
> in NiFi terminology) can be complex. For example, to add a new user with the
> same policies as the "Initial Administrator Identity" requires approximately
> 55 clicks, and to add a user with all policies would take approximately 80.
> Currently, the mental model appears to me to be policy-focused as opposed to
> user-focused. This makes sense as the development of these features was
> highly-focused on policy definition, and in default deployments, the number
> of policies outnumbers the number of users. Much like [NIFI-2926] streamlined
> viewing the policies assigned to a user across the entire application, I
> propose a couple of features to make user/policy management much easier.
> I believe these should be broken out into subtasks of this ticket, but I am
> including all of my thoughts in the ticket description to facilitate
> discussion in a single location. Once the community has weighed in, they can
> be subdivided.
> * Clone user feature
> ** This feature would allow an administrator/user with necessary user
> management permissions to clone an existing user and copy their permissions.
> This is useful for adding new members of a team with the expectation that
> they would gain access to the same resources and global policies granted to a
> colleague at a similar level of job responsibility. This feature should be
> implemented in a way that the policies are cloned but not related -- i.e. if
> Andy has permission X and Matt is a clone, Matt should have permission X
> permanently, even if Andy loses permission X tomorrow.
> * New user policy definition dialog
> ** Similar to the attached screenshot for viewing policies assigned to a
> user, I suggest a feature where a specific user or group can be selected and
> all available global and per-resource policies on the system are exposed as a
> list with checkboxes or a ternary selector if applicable (NONE, READ,
> READ+WRITE). The existing policies for the user/group would be
> pre-populated/selected. This would allow the rapid creation of a new user
> with appropriate policy assignment without cloning an existing user, and the
> rapid application of new policies to an existing user/group.
> * Batch user import
> ** Whether the users are providing client certificates, LDAP credentials, or
> Kerberos tickets to authenticate, the canonical source of identity is still
> managed by NiFi. I propose a mechanism to quickly define multiple users in
> the system (without affording any policy assignments). Here I am looking for
> substantial community input on the most common/desired use cases, but my
> initial thoughts are:
> *** One user per line in a text file/pastable text area in a UI dialog
> Each line is parsed and a user defined with the provided username
> *** LDAP-specific
> A manager DN and password (similar to necessary for LDAP authentication)
> are used to authenticate the admin/user manager, and then a LDAP query string
> (i.e. {{ou=users,dc=nifi,dc=apache,dc=org}}) is provided and the dialog
> displays/API returns a list of users/groups matching the query. The admin can
> then select which to import to NiFi and confirm.
> *** Kerberos-specific
> No existing thoughts
> *** Client certificate-specific
> No way to know all client certificates signed by the CA cert a priori
> without integration to CA (even then, intermediate signatures could raise
> issues)
--
This message was sent by Atlassian
[jira] [Updated] (NIFI-3232) Extend UI menus to allow cascading (menu item > subitem)
[ https://issues.apache.org/jira/browse/NIFI-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-3232: -- Priority: Major (was: Minor) > Extend UI menus to allow cascading (menu item > subitem) > > > Key: NIFI-3232 > URL: https://issues.apache.org/jira/browse/NIFI-3232 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Rob Moran > > With expanding functionality UI menu options are growing, making the size of > some quite large. Cascading menus will allow better information hierarchy to > improve the presentation of available user actions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-3119) UI - Nodewise breakdown of System Diagnostics
[ https://issues.apache.org/jira/browse/NIFI-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-3119: - Assignee: Matt Gilman > UI - Nodewise breakdown of System Diagnostics > - > > Key: NIFI-3119 > URL: https://issues.apache.org/jira/browse/NIFI-3119 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Minor > Fix For: 1.2.0 > > > When selecting a specific node in the summary page, that node should be used > for the basis of the system diagnostics. However, it appears that the values > are aggregated as if the entire cluster was selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3121) Remove read permissions on proxy resource for Node Identities
[
https://issues.apache.org/jira/browse/NIFI-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-3121:
--
Component/s: (was: Core UI)
Extensions
> Remove read permissions on proxy resource for Node Identities
> -
>
> Key: NIFI-3121
> URL: https://issues.apache.org/jira/browse/NIFI-3121
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Pierre Villard
>Priority: Trivial
>
> When running a cluster, node identifies defined in {{authorizers.xml}} are
> granted read and write permissions in {{authorizations.xml}} although only
> write is required (and only write can be granted from UI for new users).
> {noformat}
> resource="/proxy" action="R">
>
>
>
>
> resource="/proxy" action="W">
>
>
>
>
>
> {noformat}
> Removing read access would be nice to avoid confusion when looking at the UI
> to grant same policies to a new user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-3169) Root Process Group name should be used for NiFi instance name
[ https://issues.apache.org/jira/browse/NIFI-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764903#comment-15764903 ] Matt Gilman commented on NIFI-3169: --- Because of multi-tenancy may want to introduce a new field for the instance name which would be used in places like the About dialog and Browser tab. > Root Process Group name should be used for NiFi instance name > - > > Key: NIFI-3169 > URL: https://issues.apache.org/jira/browse/NIFI-3169 > Project: Apache NiFi > Issue Type: New Feature > Components: Core UI >Affects Versions: 1.1.0 >Reporter: Jeff Storck >Priority: Minor > > In NiFi 0.x, you could name the NiFi flow and that name would be displayed in > the browser tab. In 1.x, a user can name the root process group, but not the > instance itself. The name configured for the root process group could be > used as the name of the NiFi instance and be displayed in places like the > browser tab, in the Status History dialog (where currently "NiFi" is used as > the aggregate status across nodes), etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3169) Root Process Group name should be used for NiFi instance name
[ https://issues.apache.org/jira/browse/NIFI-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-3169: -- Issue Type: New Feature (was: Bug) > Root Process Group name should be used for NiFi instance name > - > > Key: NIFI-3169 > URL: https://issues.apache.org/jira/browse/NIFI-3169 > Project: Apache NiFi > Issue Type: New Feature > Components: Core UI >Affects Versions: 1.1.0 >Reporter: Jeff Storck >Priority: Minor > > In NiFi 0.x, you could name the NiFi flow and that name would be displayed in > the browser tab. In 1.x, a user can name the root process group, but not the > instance itself. The name configured for the root process group could be > used as the name of the NiFi instance and be displayed in places like the > browser tab, in the Status History dialog (where currently "NiFi" is used as > the aggregate status across nodes), etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3210) Should disallow creation of duplicate rule names in Advanced UI
[ https://issues.apache.org/jira/browse/NIFI-3210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-3210: -- Issue Type: Bug (was: Improvement) > Should disallow creation of duplicate rule names in Advanced UI > --- > > Key: NIFI-3210 > URL: https://issues.apache.org/jira/browse/NIFI-3210 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0, 1.1.0 >Reporter: Andrew Lim >Priority: Minor > Attachments: NIFI-3210_duplicateRuleName.png > > > Filing this because I haven't been able to come up with a use case where > duplicate rule names would be desired. But if so, understand if this Jira is > closed. > However, as shown in the attached screenshot, allowing duplicate rule names > causes some very confusing scenarios for ordering of rules and also when > selecting a rule to copy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Rosander updated NIFI-3235: - Description: EvaluateJsonPath does a lot of work in every onTrigger() that can be done when scheduled. This has the effect of making it take more cpu cycles than necessary to do its job. Initializing the JsonPath objects in a ThreadLocal and getting the properties from the ProcessContext a single time in onSchedule() should reduce the amount of CPU time this processor needs to perform a given task. was: EvaluateJsonPath does a lot of work in every onTrigger() that can be done when scheduled. This has the effect of making it take more cpu cycles than necessary to do its job. Initializing the JsonPath objects in a ThreadLocal because they aren't thread-safe and getting the properties from the ProcessContext a single time in onSchedule() should reduce the amount of CPU time this processor needs to perform a given task. > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the JsonPath objects in a ThreadLocal and getting the properties > from the ProcessContext a single time in onSchedule() should reduce the > amount of CPU time this processor needs to perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3230) Get/Put JMS broken for simple ActiveMQ SSL URIs
[ https://issues.apache.org/jira/browse/NIFI-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Moser updated NIFI-3230: Affects Version/s: (was: 0.7.1) (was: 0.6.1) Status: Patch Available (was: Open) > Get/Put JMS broken for simple ActiveMQ SSL URIs > --- > > Key: NIFI-3230 > URL: https://issues.apache.org/jira/browse/NIFI-3230 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.1.0, 0.5.1 >Reporter: Michael Moser >Assignee: Michael Moser > > The GetJMS* and PutJMS processors don't work with ActiveMQ SSL using the > simple ssl://127.0.0.1:65189 URI. It does work, though, with composite URIs > like failover:(ssl://127.0.0.1:65189,ssl://127.0.0.1:65188)?randomize=false > Even though we want people to use ConsumeJMS and PublishJMS, we should fix > the GetJMS* and PutJMS processors because they are still in the baseline. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi-minifi pull request #66: MINIFI-157 Adjusting toolkit readme to align w...
Github user asfgit closed the pull request at: https://github.com/apache/nifi-minifi/pull/66 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764839#comment-15764839 ] ASF GitHub Bot commented on NIFI-3235: -- GitHub user brosander opened a pull request: https://github.com/apache/nifi/pull/1346 NIFI-3235 - EvaluateJsonPath performance improvements 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] - N/A - Tests already cover changes - Have you written or updated unit tests to verify your changes? - [X] - N/A - 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] - N/A - If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [X] - N/A - If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [X] - N/A - If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [X] - N/A - 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/brosander/nifi NIFI-3235 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1346.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 #1346 commit ae2185709faec01d32d7af363a42bac2345d72b7 Author: Bryan Rosander Date: 2016-12-20T17:29:15Z NIFI-3235 - EvaluateJsonPath performance improvements > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the JsonPath objects in a ThreadLocal because they aren't > thread-safe and getting the properties from the ProcessContext a single time > in onSchedule() should reduce the amount of CPU time this processor needs to > perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1346: NIFI-3235 - EvaluateJsonPath performance improvemen...
GitHub user brosander opened a pull request: https://github.com/apache/nifi/pull/1346 NIFI-3235 - EvaluateJsonPath performance improvements 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] - N/A - Tests already cover changes - Have you written or updated unit tests to verify your changes? - [X] - N/A - 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] - N/A - If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly? - [X] - N/A - If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly? - [X] - N/A - If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties? ### For documentation related changes: - [X] - N/A - 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/brosander/nifi NIFI-3235 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1346.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 #1346 commit ae2185709faec01d32d7af363a42bac2345d72b7 Author: Bryan Rosander Date: 2016-12-20T17:29:15Z NIFI-3235 - EvaluateJsonPath performance improvements --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #1345: Updated two broken links in the Encryption Configur...
GitHub user thesolson opened a pull request: https://github.com/apache/nifi/pull/1345 Updated two broken links in the Encryption Configuration section of th… …e Admin Guide 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: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with NIFI- 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: - [ ] 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/thesolson/nifi NIFI-3234 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1345.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 #1345 commit b14b5626a45a7deddca1ed2feafe9d4d3fb70723 Author: Sarah Olson Date: 2016-12-20T17:33:37Z Updated two broken links in the Encryption Configuration sectionof the Admin Guide --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-3235) EvaluateJsonPath performance improvements
[ https://issues.apache.org/jira/browse/NIFI-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Rosander updated NIFI-3235: - Attachment: after.png before.png After changes the processor uses about 80% of the cpu time to do the same amount of work (same flow and input data/rate, the per 5 minute differences in input are due to slight differences in queue state but difference is negligible (less than 0.01%)) > EvaluateJsonPath performance improvements > - > > Key: NIFI-3235 > URL: https://issues.apache.org/jira/browse/NIFI-3235 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > EvaluateJsonPath does a lot of work in every onTrigger() that can be done > when scheduled. This has the effect of making it take more cpu cycles than > necessary to do its job. > Initializing the JsonPath objects in a ThreadLocal because they aren't > thread-safe and getting the properties from the ProcessContext a single time > in onSchedule() should reduce the amount of CPU time this processor needs to > perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3230) Get/Put JMS broken for simple ActiveMQ SSL URIs
[ https://issues.apache.org/jira/browse/NIFI-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764749#comment-15764749 ] ASF GitHub Bot commented on NIFI-3230: -- GitHub user mosermw opened a pull request: https://github.com/apache/nifi/pull/1344 NIFI-3230 fix ActiveMQ SSL support for simple connect URIs in Get/Put JMS processors 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/mosermw/nifi nifi-3230 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1344.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 #1344 commit 7d64a59c7f101c97cfd273437cbd98f4c1af6f11 Author: Mike Moser Date: 2016-12-20T17:26:39Z NIFI-3230 fix ActiveMQ SSL support for simple connect URIs in Get/Put JMS processors > Get/Put JMS broken for simple ActiveMQ SSL URIs > --- > > Key: NIFI-3230 > URL: https://issues.apache.org/jira/browse/NIFI-3230 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.5.1, 0.6.1, 1.1.0, 0.7.1 >Reporter: Michael Moser >Assignee: Michael Moser > > The GetJMS* and PutJMS processors don't work with ActiveMQ SSL using the > simple ssl://127.0.0.1:65189 URI. It does work, though, with composite URIs > like failover:(ssl://127.0.0.1:65189,ssl://127.0.0.1:65188)?randomize=false > Even though we want people to use ConsumeJMS and PublishJMS, we should fix > the GetJMS* and PutJMS processors because they are still in the baseline. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1344: NIFI-3230 fix ActiveMQ SSL support for simple conne...
GitHub user mosermw opened a pull request: https://github.com/apache/nifi/pull/1344 NIFI-3230 fix ActiveMQ SSL support for simple connect URIs in Get/Put JMS processors 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/mosermw/nifi nifi-3230 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1344.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 #1344 commit 7d64a59c7f101c97cfd273437cbd98f4c1af6f11 Author: Mike Moser Date: 2016-12-20T17:26:39Z NIFI-3230 fix ActiveMQ SSL support for simple connect URIs in Get/Put JMS processors --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-3235) EvaluateJsonPath performance improvements
Bryan Rosander created NIFI-3235: Summary: EvaluateJsonPath performance improvements Key: NIFI-3235 URL: https://issues.apache.org/jira/browse/NIFI-3235 Project: Apache NiFi Issue Type: Improvement Reporter: Bryan Rosander Priority: Minor EvaluateJsonPath does a lot of work in every onTrigger() that can be done when scheduled. This has the effect of making it take more cpu cycles than necessary to do its job. Initializing the JsonPath objects in a ThreadLocal because they aren't thread-safe and getting the properties from the ProcessContext a single time in onSchedule() should reduce the amount of CPU time this processor needs to perform a given task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2861) ControlRate should accept more than one flow file per execution
[
https://issues.apache.org/jira/browse/NIFI-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764738#comment-15764738
]
Michael Moser commented on NIFI-2861:
-
[~markap14] I will pick this up for review if you don't have the time, because
I've been in the ControlRate code before. Let me know.
> ControlRate should accept more than one flow file per execution
> ---
>
> Key: NIFI-2861
> URL: https://issues.apache.org/jira/browse/NIFI-2861
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Joe Skora
>Assignee: Joe Skora
>
> The {{ControlRate}} processor implements a {{FlowFileFilter}} that returns
> the {{FlowFileFilter.ACCEPT_AND_TERMINATE}} result if the {{FlowFile}} fits
> with the rate limit, affectively limiting it to one {{FlowFile}} per
> {{ConrolRate.onTrigger()}} invocation. This is a significant bottleneck when
> processing very large quantities of small files making it unlikely to hit the
> rate limits.
> It should allow multiple files, perhaps with a configurable maximum, per
> {{ControlRate.onTrigger()}} invocation by issuing the
> {{FlowFileFilter.ACCEPT_AND_CONTINUE}} result until the limits are reached.
> In a preliminary test this eliminated the bottleneck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-3230) Get/Put JMS broken for simple ActiveMQ SSL URIs
[ https://issues.apache.org/jira/browse/NIFI-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764704#comment-15764704 ] Michael Moser commented on NIFI-3230: - By "GetJMSQueue doesn't work with ActiveMQ SSL" I mean I get this error message when I start the GetJMSQueue processor. ERROR [Timer-Driven Process Thread-10] o.a.nifi.processors.standard.GetJMSQueue GetJMSQueue[id=0943d5cc-0159-1000-059e-6f460652b59b] Failed to connect to JMS Server due to javax.jms.JMSException: Could not connect to broker URL: ssl://localhost:61615. Reason: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > Get/Put JMS broken for simple ActiveMQ SSL URIs > --- > > Key: NIFI-3230 > URL: https://issues.apache.org/jira/browse/NIFI-3230 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 0.5.1, 0.6.1, 1.1.0, 0.7.1 >Reporter: Michael Moser >Assignee: Michael Moser > > The GetJMS* and PutJMS processors don't work with ActiveMQ SSL using the > simple ssl://127.0.0.1:65189 URI. It does work, though, with composite URIs > like failover:(ssl://127.0.0.1:65189,ssl://127.0.0.1:65188)?randomize=false > Even though we want people to use ConsumeJMS and PublishJMS, we should fix > the GetJMS* and PutJMS processors because they are still in the baseline. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-3225) Abstract Processor type that batches session.get() and session.commit() calls
[ https://issues.apache.org/jira/browse/NIFI-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Rosander resolved NIFI-3225. -- Resolution: Invalid > Abstract Processor type that batches session.get() and session.commit() calls > - > > Key: NIFI-3225 > URL: https://issues.apache.org/jira/browse/NIFI-3225 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > For processors that are stateless and support batching, it should be safe to > get and process multiple input FlowFiles for each onTrigger() call. > This should amortize the cost of session.get(), session.checkpoint(), > session.commit() as well as any setup in onTrigger() that isn't dependent on > the FlowFile(s) attributes or content. > An AbstractBatchingProcessor type should reduce boilerplate code in candidate > processors and encourage uniform configurability via a property to control > batch size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (NIFI-3225) Abstract Processor type that batches session.get() and session.commit() calls
[ https://issues.apache.org/jira/browse/NIFI-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Rosander closed NIFI-3225. > Abstract Processor type that batches session.get() and session.commit() calls > - > > Key: NIFI-3225 > URL: https://issues.apache.org/jira/browse/NIFI-3225 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Rosander >Assignee: Bryan Rosander >Priority: Minor > Attachments: after.png, before.png > > > For processors that are stateless and support batching, it should be safe to > get and process multiple input FlowFiles for each onTrigger() call. > This should amortize the cost of session.get(), session.checkpoint(), > session.commit() as well as any setup in onTrigger() that isn't dependent on > the FlowFile(s) attributes or content. > An AbstractBatchingProcessor type should reduce boilerplate code in candidate > processors and encourage uniform configurability via a property to control > batch size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-3234) Fix two broken links in the Admin Guide
Sarah Olson created NIFI-3234: - Summary: Fix two broken links in the Admin Guide Key: NIFI-3234 URL: https://issues.apache.org/jira/browse/NIFI-3234 Project: Apache NiFi Issue Type: Bug Components: Documentation & Website Affects Versions: 1.1.0 Reporter: Sarah Olson Assignee: Sarah Olson Priority: Minor Several external links in the below section are broken. Update with appropriate new links. http://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#encryption -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3233: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Assignee: Mark Rebuck >Priority: Trivial > Fix For: 1.2.0 > > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi-minifi pull request #66: MINIFI-157 Adjusting toolkit readme to align w...
GitHub user JPercivall opened a pull request: https://github.com/apache/nifi-minifi/pull/66 MINIFI-157 Adjusting toolkit readme to align with 0.1.0 features Thank you for submitting a contribution to Apache NiFi - MiNiFi. 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: - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi-minifi 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 minifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly? ### 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/JPercivall/nifi-minifi MINIFI-157 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/66.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 #66 commit 077e568077b6c88e0832ab089e559ec0b9cd7049 Author: Joseph Percivall Date: 2016-12-20T16:25:19Z MINIFI-157 Adjusting toolkit readme to align with 0.1.0 features --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3233: -- Assignee: Mark Rebuck Status: Patch Available (was: Open) > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Assignee: Mark Rebuck >Priority: Trivial > Fix For: 1.2.0 > > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764562#comment-15764562 ] ASF GitHub Bot commented on NIFI-3233: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1343 > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Priority: Trivial > Fix For: 1.2.0 > > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764559#comment-15764559 ] ASF subversion and git services commented on NIFI-3233: --- Commit 445c075963422e9dd2eccb634dd5065a5fbd5230 in nifi's branch refs/heads/master from [~MarkRebuck] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=445c075 ] NIFI-3233 Fix minor typo in developer-guide.adoc This closes #1343. Signed-off-by: Aldrin Piri > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Priority: Trivial > Fix For: 1.2.0 > > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3233: -- Fix Version/s: 1.2.0 > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Priority: Trivial > Fix For: 1.2.0 > > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1343: NIFI-3233 Fix minor typo in developer-guide.adoc
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1343 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764556#comment-15764556 ] ASF GitHub Bot commented on NIFI-3233: -- Github user apiri commented on the issue: https://github.com/apache/nifi/pull/1343 Thanks for fixing and submitting a patch. Will merge this in. > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Priority: Trivial > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #1343: NIFI-3233 Fix minor typo in developer-guide.adoc
Github user apiri commented on the issue: https://github.com/apache/nifi/pull/1343 Thanks for fixing and submitting a patch. Will merge this in. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-3233) Minor typo in developer guide
[ https://issues.apache.org/jira/browse/NIFI-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764541#comment-15764541 ] ASF GitHub Bot commented on NIFI-3233: -- GitHub user MarkRebuck opened a pull request: https://github.com/apache/nifi/pull/1343 NIFI-3233 Fix minor typo in developer-guide.adoc From https://issues.apache.org/jira/browse/NIFI-3233 : In section "Common Processor Patterns" -> "Data Ingress", the sentence "A Processor that ingests data into NiFi has a single Relationship names success" should read "...named success". You can merge this pull request into a Git repository by running: $ git pull https://github.com/MarkRebuck/nifi NIFI-3233 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1343.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 #1343 commit 7ed8030eac8b5226e41b2989a774ccdafa70e47b Author: Mark Rebuck Date: 2016-12-20T16:09:03Z NIFI-3233 Fix minor typo in developer-guide.adoc > Minor typo in developer guide > - > > Key: NIFI-3233 > URL: https://issues.apache.org/jira/browse/NIFI-3233 > Project: Apache NiFi > Issue Type: New Feature > Components: Documentation & Website >Reporter: Mark Rebuck >Priority: Trivial > > In section "Common Processor Patterns" -> "Data Ingress", the sentence "A > Processor that ingests data into NiFi has a single Relationship names > success" should read "...named success". > Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1343: NIFI-3233 Fix minor typo in developer-guide.adoc
GitHub user MarkRebuck opened a pull request: https://github.com/apache/nifi/pull/1343 NIFI-3233 Fix minor typo in developer-guide.adoc From https://issues.apache.org/jira/browse/NIFI-3233 : In section "Common Processor Patterns" -> "Data Ingress", the sentence "A Processor that ingests data into NiFi has a single Relationship names success" should read "...named success". You can merge this pull request into a Git repository by running: $ git pull https://github.com/MarkRebuck/nifi NIFI-3233 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/1343.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 #1343 commit 7ed8030eac8b5226e41b2989a774ccdafa70e47b Author: Mark Rebuck Date: 2016-12-20T16:09:03Z NIFI-3233 Fix minor typo in developer-guide.adoc --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-3233) Minor typo in developer guide
Mark Rebuck created NIFI-3233: - Summary: Minor typo in developer guide Key: NIFI-3233 URL: https://issues.apache.org/jira/browse/NIFI-3233 Project: Apache NiFi Issue Type: New Feature Components: Documentation & Website Reporter: Mark Rebuck Priority: Trivial In section "Common Processor Patterns" -> "Data Ingress", the sentence "A Processor that ingests data into NiFi has a single Relationship names success" should read "...named success". Will submit github PR momentarily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (NIFI-3232) Extend UI menus to allow cascading (menu item > subitem)
[ https://issues.apache.org/jira/browse/NIFI-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764482#comment-15764482 ] Rob Moran edited comment on NIFI-3232 at 12/20/16 3:41 PM: --- To expand alignment options (NIFI-96) we need cascading menus. was (Author: rmoran): To expand alignment options we need cascading menus. > Extend UI menus to allow cascading (menu item > subitem) > > > Key: NIFI-3232 > URL: https://issues.apache.org/jira/browse/NIFI-3232 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Rob Moran >Priority: Minor > > With expanding functionality UI menu options are growing, making the size of > some quite large. Cascading menus will allow better information hierarchy to > improve the presentation of available user actions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-3232) Extend UI menus to allow cascading (menu item > subitem)
[ https://issues.apache.org/jira/browse/NIFI-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764482#comment-15764482 ] Rob Moran commented on NIFI-3232: - To expand alignment options we need cascading menus. > Extend UI menus to allow cascading (menu item > subitem) > > > Key: NIFI-3232 > URL: https://issues.apache.org/jira/browse/NIFI-3232 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Rob Moran >Priority: Minor > > With expanding functionality UI menu options are growing, making the size of > some quite large. Cascading menus will allow better information hierarchy to > improve the presentation of available user actions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (NIFI-96) Consider click to align for components on canvas
[ https://issues.apache.org/jira/browse/NIFI-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764408#comment-15764408 ] Rob Moran edited comment on NIFI-96 at 12/20/16 3:37 PM: - Alignment actions - similar to what you'd see in design or layout applications - could be made available from any selected component's context menu, when multiple components are selected. I think initially providing two options will be very useful: # Align center (horizontally) # Align middle (vertically) Future iterations can expand on these options (such as align left/right/top/bottom and distribute horizontally/vertically). However, I think in order for context menus to support that many options we should look at expanding context menus to allow cascading (menu > submenu). I plan to create a separate jira for that and link them. >> NIFI-3232 was (Author: rmoran): Alignment actions - similar to what you'd see in design or layout applications - could be made available from any selected component's context menu, when multiple components are selected. I think initially providing two options will be very useful: # Align center (horizontally) # Align middle (vertically) Future iterations can expand on these options (such as align left/right/top/bottom and distribute horizontally/vertically). However, I think in order for context menus to support that many options we should look at expanding context menus to allow cascading (menu > submenu). I plan to create a separate jira for that and link them. > Consider click to align for components on canvas > > > Key: NIFI-96 > URL: https://issues.apache.org/jira/browse/NIFI-96 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Scott Aslan >Priority: Minor > > Provide the user with layout options to arrange components on the canvas with > more precision. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-3232) Extend UI menus to allow cascading (menu item > subitem)
Rob Moran created NIFI-3232: --- Summary: Extend UI menus to allow cascading (menu item > subitem) Key: NIFI-3232 URL: https://issues.apache.org/jira/browse/NIFI-3232 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Rob Moran Priority: Minor With expanding functionality UI menu options are growing, making the size of some quite large. Cascading menus will allow better information hierarchy to improve the presentation of available user actions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2585) Add attributes to track where a flow file came from when receiving over site-to-site
[ https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764414#comment-15764414 ] ASF GitHub Bot commented on NIFI-2585: -- Github user bbende commented on the issue: https://github.com/apache/nifi/pull/1342 @ijokarumawak thanks for digging in to this! I closed the other PR. Everything you described makes sense... I'm on the fence about the attribute names... lets say we have MiNiFi -> s2s -> NiFi, the s2s.address is always going to be the address of MiNiFi, but from the address we don't know if MiNiFi was the client (push to NiFi) vs the server (NiFi pull from MiNiFi). I was originally thinking of having a third attribute like s2s.direction which could have values of "push" or "pull" which then gives you context about the host and port. What do you think? > Add attributes to track where a flow file came from when receiving over > site-to-site > > > Key: NIFI-2585 > URL: https://issues.apache.org/jira/browse/NIFI-2585 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Randy Gelhausen >Priority: Minor > > With MiNiFi starting be used to send data to a central NiFi, it would be > helpful if information about the sending host and port was added to each flow > file received over site-to-site. Currently this information is available and > used to generate the transit URI in the RECEIVE event, but this information > isn't available to downstream processors that might want to make routing > decisions. > For reference: > https://github.com/apache/nifi/blob/e23b2356172e128086585fe2c425523c3628d0e7/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/protocol/AbstractFlowFileServerProtocol.java#L452 > A possible approach might be to add two attributes to each flow file, > something like "remote.host" and "remote.address" where remote.host has only > the sending hostname, and remote.address has the sending host and port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #1342: NIFI-2585 Add attributes to track s2s host and port
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/1342 @ijokarumawak thanks for digging in to this! I closed the other PR. Everything you described makes sense... I'm on the fence about the attribute names... lets say we have MiNiFi -> s2s -> NiFi, the s2s.address is always going to be the address of MiNiFi, but from the address we don't know if MiNiFi was the client (push to NiFi) vs the server (NiFi pull from MiNiFi). I was originally thinking of having a third attribute like s2s.direction which could have values of "push" or "pull" which then gives you context about the host and port. What do you think? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-96) Consider click to align for components on canvas
[ https://issues.apache.org/jira/browse/NIFI-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764408#comment-15764408 ] Rob Moran commented on NIFI-96: --- Alignment actions - similar to what you'd see in design or layout applications - could be made available from any selected component's context menu, when multiple components are selected. I think initially providing two options will be very useful: # Align center (horizontally) # Align middle (vertically) Future iterations can expand on these options (such as align left/right/top/bottom and distribute horizontally/vertically). However, I think in order for context menus to support that many options we should look at expanding context menus to allow cascading (menu > submenu). I plan to create a separate jira for that and link them. > Consider click to align for components on canvas > > > Key: NIFI-96 > URL: https://issues.apache.org/jira/browse/NIFI-96 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Scott Aslan >Priority: Minor > > Provide the user with layout options to arrange components on the canvas with > more precision. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-96) Consider click to align for components on canvas
[ https://issues.apache.org/jira/browse/NIFI-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Moran updated NIFI-96: -- Description: Provide the user with layout options to arrange components on the canvas with more precision. > Consider click to align for components on canvas > > > Key: NIFI-96 > URL: https://issues.apache.org/jira/browse/NIFI-96 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Scott Aslan >Priority: Minor > > Provide the user with layout options to arrange components on the canvas with > more precision. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2585) Add attributes to track where a flow file came from when receiving over site-to-site
[ https://issues.apache.org/jira/browse/NIFI-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764287#comment-15764287 ] ASF GitHub Bot commented on NIFI-2585: -- Github user bbende closed the pull request at: https://github.com/apache/nifi/pull/1320 > Add attributes to track where a flow file came from when receiving over > site-to-site > > > Key: NIFI-2585 > URL: https://issues.apache.org/jira/browse/NIFI-2585 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Randy Gelhausen >Priority: Minor > > With MiNiFi starting be used to send data to a central NiFi, it would be > helpful if information about the sending host and port was added to each flow > file received over site-to-site. Currently this information is available and > used to generate the transit URI in the RECEIVE event, but this information > isn't available to downstream processors that might want to make routing > decisions. > For reference: > https://github.com/apache/nifi/blob/e23b2356172e128086585fe2c425523c3628d0e7/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/protocol/AbstractFlowFileServerProtocol.java#L452 > A possible approach might be to add two attributes to each flow file, > something like "remote.host" and "remote.address" where remote.host has only > the sending hostname, and remote.address has the sending host and port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #1320: NIFI-2585 Add attributes to track s2s host and port
Github user bbende closed the pull request at: https://github.com/apache/nifi/pull/1320 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-3231) PutTCP and PutUDP should support EL for host and port
Bryan Bende created NIFI-3231: - Summary: PutTCP and PutUDP should support EL for host and port Key: NIFI-3231 URL: https://issues.apache.org/jira/browse/NIFI-3231 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.1.0, 1.0.0, 1.1.1 Reporter: Bryan Bende PutTCP and PutUDP should support expression language (without a flow file) for host and port in order to make use of the variable registry and reference different hosts and ports per environment. Relevant code: https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutTCP.java#L110 https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/PutUDP.java#L94 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
