[jira] [Commented] (NIFI-4189) NiFi ignores logback rotation settings

[ https://issues.apache.org/jira/browse/NIFI-4189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088811#comment-16088811 ] Andre F de Miranda commented on NIFI-4189: -- >From what I understand, based on logback settings,

[jira] [Commented] (NIFI-2962) Default conf/logback comment for maxHistory is misleading and incorrect

[ https://issues.apache.org/jira/browse/NIFI-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088805#comment-16088805 ] Andre F de Miranda commented on NIFI-2962: -- Just as a comment on this. The logback config is

[jira] [Created] (NIFI-4189) NiFi ignores logback rotation settings

Andre F de Miranda created NIFI-4189: Summary: NiFi ignores logback rotation settings Key: NIFI-4189 URL: https://issues.apache.org/jira/browse/NIFI-4189 Project: Apache NiFi Issue Type:

[jira] [Commented] (NIFI-4081) GrokReader - add the option to keep raw message in a dedicated field

[ https://issues.apache.org/jira/browse/NIFI-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088802#comment-16088802 ] ASF GitHub Bot commented on NIFI-4081: -- Github user trixpan commented on the issue:

[GitHub] nifi issue #1921: NIFI-4081 - Added raw message option in GrokReader

Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/1921 @pvillard31 I accept it is a bit of bit picking but is there any chance we call it _raw? IIRC this is the name we used on ParseCEF. Naming conventions make user experience smoother 😀 --- If your

[jira] [Commented] (NIFI-4188) Create RethinkDB get processor

[ https://issues.apache.org/jira/browse/NIFI-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088782#comment-16088782 ] ASF GitHub Bot commented on NIFI-4188: -- GitHub user mans2singh opened a pull request:

[jira] [Commented] (NIFI-4118) Create Nifi RethinkDB Put processor

[ https://issues.apache.org/jira/browse/NIFI-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088780#comment-16088780 ] ASF GitHub Bot commented on NIFI-4118: -- Github user mans2singh closed the pull request at:

[GitHub] nifi pull request #2011: NIFI-4118 - Nifi RethinkDB Get processor

Github user mans2singh closed the pull request at: https://github.com/apache/nifi/pull/2011 --- 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

[GitHub] nifi issue #2011: NIFI-4118 - Nifi RethinkDB Get processor

Github user mans2singh commented on the issue: https://github.com/apache/nifi/pull/2011 The Jira ticket number was not correct. Will close this one and open a new request. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[jira] [Commented] (NIFI-4118) Create Nifi RethinkDB Put processor

[ https://issues.apache.org/jira/browse/NIFI-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088779#comment-16088779 ] ASF GitHub Bot commented on NIFI-4118: -- Github user mans2singh commented on the issue:

[jira] [Commented] (NIFI-4118) Create Nifi RethinkDB Put processor

[ https://issues.apache.org/jira/browse/NIFI-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088778#comment-16088778 ] ASF GitHub Bot commented on NIFI-4118: -- GitHub user mans2singh opened a pull request:

[GitHub] nifi pull request #2011: NIFI-4118 - Nifi RethinkDB Get processor

GitHub user mans2singh opened a pull request: https://github.com/apache/nifi/pull/2011 NIFI-4118 - Nifi RethinkDB Get processor Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure the

[GitHub] nifi-minifi-cpp issue #114: site2site port negotiation

Github user benqiu2016 commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/114 @phrocker @kevdoran use lock, extract token code, set default port. we need to support /nifi-api/controller which is common to 1.x and 0.x. --- If your project is set up for it, you

[jira] [Created] (NIFI-4188) Create RethinkDB get processor

Mans Singh created NIFI-4188: Summary: Create RethinkDB get processor Key: NIFI-4188 URL: https://issues.apache.org/jira/browse/NIFI-4188 Project: Apache NiFi Issue Type: New Feature

[jira] [Commented] (NIFI-4147) Class org.apache.nifi.bootstrap.RunNiFi is not designed with extensibility in mind

[ https://issues.apache.org/jira/browse/NIFI-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088715#comment-16088715 ] ASF GitHub Bot commented on NIFI-4147: -- Github user jvwing commented on a diff in the pull request:

[GitHub] nifi pull request #1972: NIFI-4147 Class org.apache.nifi.bootstrap.RunNiFi i...

Github user jvwing commented on a diff in the pull request: https://github.com/apache/nifi/pull/1972#discussion_r127591766 --- Diff: nifi-bootstrap/src/main/java/org/apache/nifi/bootstrap/RunNiFi.java --- @@ -135,8 +135,8 @@ private volatile Set loggingFutures =

[jira] [Commented] (NIFI-4147) Class org.apache.nifi.bootstrap.RunNiFi is not designed with extensibility in mind

[ https://issues.apache.org/jira/browse/NIFI-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088711#comment-16088711 ] ASF GitHub Bot commented on NIFI-4147: -- Github user jvwing commented on the issue:

[GitHub] nifi issue #1972: NIFI-4147 Class org.apache.nifi.bootstrap.RunNiFi is not d...

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/1972 @peter-gergely-horvath Thank you for submitting this PR, improving testability is always welcome. I will be happy to review. --- If your project is set up for it, you can reply to this email and

[jira] [Commented] (NIFI-4015) DeleteSQS Throws Exception Deleting Message

[ https://issues.apache.org/jira/browse/NIFI-4015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088697#comment-16088697 ] ASF GitHub Bot commented on NIFI-4015: -- Github user jvwing commented on the issue:

[GitHub] nifi issue #1888: NIFI-4015 NIFI-3999 Fix DeleteSQS Issues

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/1888 @brosander I added an update to keep the existing attribute name. Please let me know if/when we need a squash and rebase. --- If your project is set up for it, you can reply to this email and have

[GitHub] nifi issue #1983: NiFi-2829: Add Date and Time Format Support for PutSQL

Github user yjhyjhyjh0 commented on the issue: https://github.com/apache/nifi/pull/1983 Thanks for the review and feedback. I’ve add your enhancement of handing time precision at milliseconds in PutSQL. Also I'm very willing to add a unit test for it. However after

[jira] [Commented] (NIFI-2886) Framework doesn't release thread if processor administratively yields

[ https://issues.apache.org/jira/browse/NIFI-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088586#comment-16088586 ] ASF GitHub Bot commented on NIFI-2886: -- Github user olegz closed the pull request at:

[GitHub] nifi pull request #1280: NIFI-3109 Initial refactoring of TimerDrivenSchedul...

Github user olegz closed the pull request at: https://github.com/apache/nifi/pull/1280 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (NIFI-3109) Refactor TimerDrivenSchedulingAgent

[ https://issues.apache.org/jira/browse/NIFI-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088587#comment-16088587 ] ASF GitHub Bot commented on NIFI-3109: -- Github user olegz closed the pull request at:

[GitHub] nifi pull request #1278: NIFI-2886 Fixed the lifecycle delay

Github user olegz closed the pull request at: https://github.com/apache/nifi/pull/1278 --- 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