[jira] [Commented] (NIFI-4170) PutWebSocket processor does not support 'Penalty duration' and 'Yield duration' settings

[ https://issues.apache.org/jira/browse/NIFI-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079870#comment-16079870 ] Koji Kawamura commented on NIFI-4170: - Thanks for sharing a patch [~ywik] While there are few

[jira] [Commented] (NIFI-4145) RouteOnAttribute doesn't document the attribute it writes

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

[GitHub] nifi pull request #1998: NIFI-4145 Added missing write attribute annotation

GitHub user mans2singh opened a pull request: https://github.com/apache/nifi/pull/1998 NIFI-4145 Added missing write attribute annotation Thank you for submitting a contribution to Apache NiFi. In order to streamline the review of the contribution we ask you to ensure

[jira] [Assigned] (NIFI-4145) RouteOnAttribute doesn't document the attribute it writes

[ https://issues.apache.org/jira/browse/NIFI-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mans Singh reassigned NIFI-4145: Assignee: Mans Singh > RouteOnAttribute doesn't document the attribute it writes >

[jira] [Commented] (NIFI-2528) Update ListenHTTP to honor SSLContextService Protocols

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

[GitHub] nifi issue #1986: NIFI-2528: added support for SSLContextService protocols i...

Github user trkurc commented on the issue: https://github.com/apache/nifi/pull/1986 reviewing now --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[jira] [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=16079734#comment-16079734 ] ASF GitHub Bot commented on NIFI-4118: -- Github user mans2singh commented on the issue:

[GitHub] nifi issue #1942: NIFI-4118 First commit of RethinkDB put processor

Github user mans2singh commented on the issue: https://github.com/apache/nifi/pull/1942 Thanks @jvwing --- 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

[jira] [Updated] (NIFI-4154) fix windows line endings in source code

[ https://issues.apache.org/jira/browse/NIFI-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Wing updated NIFI-4154: - Resolution: Fixed Fix Version/s: 1.4.0 Status: Resolved (was: Patch Available) > fix

[jira] [Commented] (NIFI-4154) fix windows line endings in source code

[ https://issues.apache.org/jira/browse/NIFI-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079698#comment-16079698 ] ASF subversion and git services commented on NIFI-4154: --- Commit

[jira] [Commented] (NIFI-4154) fix windows line endings in source code

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

[GitHub] nifi pull request #1982: NIFI-4154 - fix line endings in source code

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/1982 --- 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 #1982: NIFI-4154 - fix line endings in source code

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/1982 Thanks @trkurc, @m-hogue. I confirmed the whitespace-only changes in the diffs, ran full build with contrib-check OK. I'll merge shortly. --- If your project is set up for it, you can reply to this

[jira] [Commented] (NIFI-4154) fix windows line endings in source code

[ https://issues.apache.org/jira/browse/NIFI-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079697#comment-16079697 ] ASF GitHub Bot commented on NIFI-4154: -- Github user jvwing 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=16079685#comment-16079685 ] ASF GitHub Bot commented on NIFI-4118: -- Github user jvwing commented on the issue:

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

[ https://issues.apache.org/jira/browse/NIFI-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Wing resolved NIFI-4118. -- Resolution: Fixed > Create Nifi RethinkDB Put processor > --- > >

[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=16079684#comment-16079684 ] ASF GitHub Bot commented on NIFI-4118: -- Github user asfgit closed the pull request at:

[GitHub] nifi issue #1942: NIFI-4118 First commit of RethinkDB put processor

Github user jvwing commented on the issue: https://github.com/apache/nifi/pull/1942 Thanks @mans2singh! This has been merged 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

[GitHub] nifi pull request #1942: NIFI-4118 First commit of RethinkDB put processor

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