[jira] [Created] (NIFI-5158) getStateValue function from NiFi expression language pads extra space in front of the returned value

2018-05-06 Thread Rahul Soni (JIRA)
Rahul Soni created NIFI-5158: Summary: getStateValue function from NiFi expression language pads extra space in front of the returned value Key: NIFI-5158 URL: https://issues.apache.org/jira/browse/NIFI-5158

[jira] [Commented] (MINIFICPP-394) Implement MQTT C2 protocol

2018-05-06 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/MINIFICPP-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465320#comment-16465320 ] ASF GitHub Bot commented on MINIFICPP-394: -- Github user phrocker commented on

[GitHub] nifi-minifi-cpp issue #321: MINIFICPP-394: Implement MQTT C2 protocol along ...

2018-05-06 Thread phrocker
Github user phrocker commented on the issue: https://github.com/apache/nifi-minifi-cpp/pull/321 I noticed there were no MQTT tests. Before this is merged I want to change this in some way. Plan was to use a stubbed out MQTT controller service to test the business logic. ---

[jira] [Commented] (MINIFICPP-394) Implement MQTT C2 protocol

2018-05-06 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/MINIFICPP-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465319#comment-16465319 ] ASF GitHub Bot commented on MINIFICPP-394: -- GitHub user phrocker opened a pull

[GitHub] nifi-minifi-cpp pull request #321: MINIFICPP-394: Implement MQTT C2 protocol...

2018-05-06 Thread phrocker
GitHub user phrocker opened a pull request: https://github.com/apache/nifi-minifi-cpp/pull/321 MINIFICPP-394: Implement MQTT C2 protocol along with MQTT/REST translation layer Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamlin

[jira] [Commented] (NIFI-5109) AbstractListProcessor stop calling performListing after primary node reelection

2018-05-06 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465202#comment-16465202 ] ASF GitHub Bot commented on NIFI-5109: -- Github user joewitt commented on the issue:

[GitHub] nifi issue #2657: NIFI-5109 Reset justElectedPrimaryNode flag right after re...

2018-05-06 Thread joewitt
Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/2657 fields being volatile can be fine. volatile makes a more explicit assertion about how java will guarantee the value to be read across threads. The issue, at least from a quick look, is the potential

[jira] [Commented] (NIFI-5109) AbstractListProcessor stop calling performListing after primary node reelection

2018-05-06 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/NIFI-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465195#comment-16465195 ] ASF GitHub Bot commented on NIFI-5109: -- Github user viazovskyi commented on the issue:

[GitHub] nifi issue #2657: NIFI-5109 Reset justElectedPrimaryNode flag right after re...

2018-05-06 Thread viazovskyi
Github user viazovskyi commented on the issue: https://github.com/apache/nifi/pull/2657 Thanks Joe. There are more volatile fields (lastListedLatestEntryTimestampMillis, lastProcessedLatestEntryTimestampMillis, etc) altered after the check. So this should be redesigned what do you thi