[jira] [Commented] (NIFI-2835) GetAzureEventHub processor should leverage partition offset to better handle restarts

[Eric Ulicny (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256902#comment-16256902
 ] 

Eric Ulicny commented on NIFI-2835:
---

Hello Koji

When I attempt to build from the azure nar file path I am getting the following 
error.

[ERROR] Failed to execute goal on project nifi-azure-processors: Could not 
resolve dependencies for project 
org.apache.nifi:nifi-azure-processors:jar:1.5.0-SNAPSHOT: The following 
artifacts could not be resolved: org.apache.nifi:nifi-mock:jar:1.5.0-SNAPSHOT, 
org.apache.nifi:nifi-processor-utils:jar:1.5.0-SNAPSHOT: Could not find 
artifact org.apache.nifi:nifi-mock:jar:1.5.0-SNAPSHOT in apache.snapshots 
(http://repository.apache.org/snapshots) -> [Help 1]
[ERROR]

command: mvn clean install
Maven version: Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 
2017-04-03T15:39:06-04:00)
Maven home: C:\Projects\nifi\maven\bin\..
Java version: 1.8.0_102, vendor: Oracle Corporation

> GetAzureEventHub processor should leverage partition offset to better handle 
> restarts
> -
>
> Key: NIFI-2835
> URL: https://issues.apache.org/jira/browse/NIFI-2835
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joseph Percivall
>Assignee: Eric Ulicny
>
> The GetAzureEventHub processor utilizes the Azure client that consists of 
> receivers for each partition. The processor stores them in a map[1] that gets 
> cleared every time the processor is stopped[2]. These receivers have 
> partition offsets which keep track of which message it's currently on and 
> which it should receive next. So currently, when the processor is 
> stopped/restarted, any tracking of which message is next to be received is 
> lost.
> If instead of clearing the map each time, we hold onto the receivers, or kept 
> track of the partitionId/Offsets when stopping, (barring any relevant 
> configuration changes) the processor would restart exactly where it left off 
> with no loss of data.
> This would work very well with NIFI-2826.
> [1]https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/eventhub/GetAzureEventHub.java#L122
> [2] 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-azure-bundle/nifi-azure-processors/src/main/java/org/apache/nifi/processors/azure/eventhub/GetAzureEventHub.java#L229



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MINIFICPP-312) Resolve CompressContentsTest by installing xz with brew

[marco polo (JIRA)]

marco polo created MINIFICPP-312:


 Summary: Resolve CompressContentsTest by installing xz with brew
 Key: MINIFICPP-312
 URL: https://issues.apache.org/jira/browse/MINIFICPP-312
 Project: NiFi MiNiFi C++
  Issue Type: Bug
Reporter: marco polo
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-312) Resolve CompressContentsTest by installing xz with brew

[marco polo (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256937#comment-16256937
 ] 

marco polo commented on MINIFICPP-312:
--

First attempt is to add xz

> Resolve CompressContentsTest by installing xz with brew
> ---
>
> Key: MINIFICPP-312
> URL: https://issues.apache.org/jira/browse/MINIFICPP-312
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFIREG-30) Integrate security/user/group endpoints

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257099#comment-16257099
 ] 

ASF GitHub Bot commented on NIFIREG-30:
---

GitHub user scottyaslan opened a pull request:

https://github.com/apache/nifi-registry/pull/40

[NIFIREG-30] GET users/groups, delete user/group, delete users/groups…

…, create group, introduce group side nav

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/scottyaslan/nifi-registry NIFIREG-30

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-registry/pull/40.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 #40


commit d744c21a780b3fea11340c1839b96bad4223b210
Author: Scott Aslan 
Date:   2017-11-17T15:08:59Z

[NIFIREG-30] GET users/groups, delete user/group, delete users/groups, 
create group, introduce group side nav




> Integrate security/user/group endpoints
> ---
>
> Key: NIFIREG-30
> URL: https://issues.apache.org/jira/browse/NIFIREG-30
> Project: NiFi Registry
>  Issue Type: Improvement
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-registry pull request #40: [NIFIREG-30] GET users/groups, delete user/g...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

https://github.com/apache/nifi-registry/pull/40

[NIFIREG-30] GET users/groups, delete user/group, delete users/groups…

…, create group, introduce group side nav

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/scottyaslan/nifi-registry NIFIREG-30

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-registry/pull/40.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 #40


commit d744c21a780b3fea11340c1839b96bad4223b210
Author: Scott Aslan 
Date:   2017-11-17T15:08:59Z

[NIFIREG-30] GET users/groups, delete user/group, delete users/groups, 
create group, introduce group side nav




---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257104#comment-16257104
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user sbouchex commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151708941
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

I will add a "else" to the already existing check and set the status in 
that case. I believe, it will be find.


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257006#comment-16257006
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user achristianson commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/191#discussion_r151692781
  
--- Diff: extensions/http-curl/protocols/RESTProtocol.cpp ---
@@ -81,48 +93,117 @@ const C2Payload RESTProtocol::parseJsonResponse(const 
C2Payload , const
   return std::move(C2Payload(payload.getOperation(), 
state::UpdateState::READ_ERROR, true));
 }
 
-Json::Value RESTProtocol::serializeJsonPayload(Json::Value _root, 
const C2Payload ) {
-  // get the name from the content
-  Json::Value json_payload;
-  std::map children;
-  for (const auto _payload : payload.getNestedPayloads()) {
-Json::Value child_payload = serializeJsonPayload(json_payload, 
nested_payload);
-children[nested_payload.getLabel()].push_back(child_payload);
-  }
-  for (auto child_vector : children) {
-if (child_vector.second.size() > 1) {
-  Json::Value children_json(Json::arrayValue);
-  for (auto child : child_vector.second) {
-json_payload[child_vector.first] = child;
-  }
-} else {
-  if (child_vector.second.size() == 1) {
-if (child_vector.second.at(0).isMember(child_vector.first)) {
-  json_payload[child_vector.first] = 
child_vector.second.at(0)[child_vector.first];
-} else {
-  json_payload[child_vector.first] = child_vector.second.at(0);
-}
-  }
-}
-  }
+void setJsonStr(const std::string& key, const std::string& value, 
rapidjson::Value& parent, rapidjson::Document::AllocatorType& alloc) { // NOLINT
+  rapidjson::Value keyVal;
+  rapidjson::Value valueVal;
+  const char* c_key = key.c_str();
+  const char* c_val = value.c_str();
 
+  keyVal.SetString(c_key, key.length()), alloc;
+  valueVal.SetString(c_val, value.length(), alloc);
+
+  parent.AddMember(keyVal, valueVal, alloc);
+}
+
+rapidjson::Value getStringValue(const std::string& value, 
rapidjson::Document::AllocatorType& alloc) { // NOLINT
+  rapidjson::Value Val;
--- End diff --

IMO we should only use macros where really necessary, so the code can be 
clearer and easier to read.


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #191: MINIFICPP-114 Consolidate JSON API use to...

[achristianson]

Github user achristianson commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/191#discussion_r151692781
  
--- Diff: extensions/http-curl/protocols/RESTProtocol.cpp ---
@@ -81,48 +93,117 @@ const C2Payload RESTProtocol::parseJsonResponse(const 
C2Payload , const
   return std::move(C2Payload(payload.getOperation(), 
state::UpdateState::READ_ERROR, true));
 }
 
-Json::Value RESTProtocol::serializeJsonPayload(Json::Value _root, 
const C2Payload ) {
-  // get the name from the content
-  Json::Value json_payload;
-  std::map children;
-  for (const auto _payload : payload.getNestedPayloads()) {
-Json::Value child_payload = serializeJsonPayload(json_payload, 
nested_payload);
-children[nested_payload.getLabel()].push_back(child_payload);
-  }
-  for (auto child_vector : children) {
-if (child_vector.second.size() > 1) {
-  Json::Value children_json(Json::arrayValue);
-  for (auto child : child_vector.second) {
-json_payload[child_vector.first] = child;
-  }
-} else {
-  if (child_vector.second.size() == 1) {
-if (child_vector.second.at(0).isMember(child_vector.first)) {
-  json_payload[child_vector.first] = 
child_vector.second.at(0)[child_vector.first];
-} else {
-  json_payload[child_vector.first] = child_vector.second.at(0);
-}
-  }
-}
-  }
+void setJsonStr(const std::string& key, const std::string& value, 
rapidjson::Value& parent, rapidjson::Document::AllocatorType& alloc) { // NOLINT
+  rapidjson::Value keyVal;
+  rapidjson::Value valueVal;
+  const char* c_key = key.c_str();
+  const char* c_val = value.c_str();
 
+  keyVal.SetString(c_key, key.length()), alloc;
+  valueVal.SetString(c_val, value.length(), alloc);
+
+  parent.AddMember(keyVal, valueVal, alloc);
+}
+
+rapidjson::Value getStringValue(const std::string& value, 
rapidjson::Document::AllocatorType& alloc) { // NOLINT
+  rapidjson::Value Val;
--- End diff --

IMO we should only use macros where really necessary, so the code can be 
clearer and easier to read.


---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257025#comment-16257025
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151695374
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

In addition to setting this here, we need to update it when merging 
responses in a clustered scenario. This merging happens to account for cases 
when a processor is invalid based on an environmental condition. A good example 
of this is a processor configured with a directory where that directory does 
not exist on one node of a cluster. On that node, the processor is invalid, but 
on the others that processor would be considered stopped. In this case, we need 
to ensure the invalid run status takes precedence. You can see an example of 
this here [1].

I think the easiest way to handle this would be to update the runStatus in 
the ProcessorStatusDTO when the method referenced in [1] returns when 
appropriate. Let me know if you have any questions about this.

[1] 
https://github.com/apache/nifi/blob/2da72f15243ef62d47369e8a87cc202a82dbe004/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-cluster/src/main/java/org/apache/nifi/cluster/manager/StatusMerger.java#L403


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-301) Create processor to apply arbitrary Tensor Flow graphs to tensors

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257066#comment-16257066
 ] 

ASF GitHub Bot commented on MINIFICPP-301:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/183


> Create processor to apply arbitrary Tensor Flow graphs to tensors
> -
>
> Key: MINIFICPP-301
> URL: https://issues.apache.org/jira/browse/MINIFICPP-301
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> In many cases, it may be desirable to interpret/preprocess raw signal inputs 
> on the edge, where MiNiFI runs, before sending semantic interpretations 
> upstream.
> Tensor Flow is a data flow system for processing tensors, and many graphs 
> exist or could be created which are well-suited to interpret signal inputs. 
> It would therefore be useful to have a processor in MiNiFi - C++ which takes 
> tensors (serialized as binary protocol buffers), feeds them into an input 
> node on a supplied graph, reads tensors from an output node, and finally 
> writes those output tensors as flow files containing binary protocol buffers.
> While there are many additional convenience utilities which would be helpful, 
> such as converting various standard sensor types into tensors, the initial 
> scope of this feature is a processor which processes arbitrary tensors 
> through arbitrary graphs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257024#comment-16257024
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151693413
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
 
 final ProcessorStatusSnapshotDTO snapshot = new 
ProcessorStatusSnapshotDTO();
 dto.setAggregateSnapshot(snapshot);
 
 snapshot.setId(procStatus.getId());
 snapshot.setGroupId(procStatus.getGroupId());
 snapshot.setName(procStatus.getName());
+snapshot.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

This is already being set a few lines below.


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-312) Resolve CompressContentsTest by installing xz with brew

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257070#comment-16257070
 ] 

ASF GitHub Bot commented on MINIFICPP-312:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/194


> Resolve CompressContentsTest by installing xz with brew
> ---
>
> Key: MINIFICPP-312
> URL: https://issues.apache.org/jira/browse/MINIFICPP-312
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri updated NIFI-4616:
--
Affects Version/s: 1.4.0

> ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to 
> communicate with Kafka broker that is SSL enabled
> 
>
> Key: NIFI-4616
> URL: https://issues.apache.org/jira/browse/NIFI-4616
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
>Reporter: Aldrin Piri
> Fix For: 1.1.0
>
>
> If I use ConsumeKafka and point to a broker that is in a bad state, I see 
> ConsumeKafka block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled

[Aldrin Piri (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257014#comment-16257014
 ] 

Aldrin Piri commented on NIFI-4616:
---

This is a clone of NIFI-2739.  I am noticing similar behavior when connecting 
to an SSL enabled Kafka broker.

If I configure a Consume Kafka processor with Security Provider and an SSL 
Context Service and then start it, it will not error and have a task attempting 
to connect even when my broker is not started.  If I then start my broker, the 
processor will remain in its prior state.  Stopping the processor, I see 
another concurrent task pop up, providing a total of 2 and then a warning level 
bulletin is posted with the following.

{quote}
2017-11-17 09:09:29,640 WARN [Timer-Driven Process Thread-9] 
o.a.n.p.kafka.pubsub.ConsumeKafka_0_10 
ConsumeKafka_0_10[id=015f1005-38d4-13aa-8ba4-def62a3de935] Was interrupted 
while trying to communicate with Kafka with lease 
org.apache.nifi.processors.kafka.pubsub.ConsumerPool$SimpleConsumerLease@230ccbef.
 Will roll back session and discard any partially received data.
{quote}

> ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to 
> communicate with Kafka broker that is SSL enabled
> 
>
> Key: NIFI-4616
> URL: https://issues.apache.org/jira/browse/NIFI-4616
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
>Reporter: Aldrin Piri
> Fix For: 1.1.0
>
>
> If I use ConsumeKafka and point to a broker that is in a bad state, I see 
> ConsumeKafka block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #193: MINIFICPP-311 Correct PutFile output dire...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/193


---

[jira] [Commented] (MINIFICPP-311) Docker verify fails due to obsolete PutFile property

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257075#comment-16257075
 ] 

ASF GitHub Bot commented on MINIFICPP-311:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/193


> Docker verify fails due to obsolete PutFile property
> 
>
> Key: MINIFICPP-311
> URL: https://issues.apache.org/jira/browse/MINIFICPP-311
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Minor
> Fix For: 0.3.0
>
>
> The 'Output Directory' property of PutFile was renamed to 'Directory,' which 
> broke the docker integration tests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2276: NIFI-4615 processor status is set to the ProcessorS...

[sbouchex]

GitHub user sbouchex opened a pull request:

https://github.com/apache/nifi/pull/2276

NIFI-4615 processor status is set to the ProcessorStatusDTO object

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?
- [ x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ x] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ x] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [x ] 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/infovista/nifi NIFI-4615

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2276.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 #2276


commit 329046a294118196c01c5d3c93d62f5479b23d55
Author: sbouchex 
Date:   2017-11-17T13:25:16Z

processor status is set to the ProcessorStatusDTO object




---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256962#comment-16256962
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

GitHub user sbouchex opened a pull request:

https://github.com/apache/nifi/pull/2276

NIFI-4615 processor status is set to the ProcessorStatusDTO object

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?
- [ x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ x] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ x] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [x ] 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/infovista/nifi NIFI-4615

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2276.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 #2276


commit 329046a294118196c01c5d3c93d62f5479b23d55
Author: sbouchex 
Date:   2017-11-17T13:25:16Z

processor status is set to the ProcessorStatusDTO object




> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256966#comment-16256966
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user calebj commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@achristianson something in the master branch is failing. Looks like 
something in the commit before the latest one, 
9b9c3354330d525cfdd50f656ae42fc3da80764c, broke it.

Regarding the LICENSE, there are a handful of them. IANAL, so can someone 
look over [rapidjson's 
license.txt](https://github.com/Tencent/rapidjson/blob/master/license.txt) and 
see what might have to be left out, if anything?


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2276: NIFI-4615 processor status is set to the ProcessorS...

[mcgilman]

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151711473
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

I'm not sure I follow what "else" you're referring to. No change is needed 
when merging snapshots (line 384), that part is already correct. What we need 
to account for is the runStatus when merging status (line 354). We can account 
for the runStatus there using one of the two options I proposed above after 
merging the aggregate snapshot on line 363. 


---

[GitHub] nifi issue #2276: NIFI-4615 processor status is set to the ProcessorStatusDT...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2276
  
@sbouchex This is a great catch and thanks for the contribution! Reviewing 
the code it appears that the runStatus was moved into the status snapshot 
likely during the 0.x -> 1.x transtion. This value is being set currently and 
is what the UI uses to render the status. However, with the runStatus still 
being available in the status it makes sense to populate it as well. I'll 
continue the review by commenting on the code...


---

[jira] [Commented] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled

[Aldrin Piri (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257017#comment-16257017
 ] 

Aldrin Piri commented on NIFI-4616:
---

Verified the behavior is the same across both ConsumeKafka and its 0_10 variant

> ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to 
> communicate with Kafka broker that is SSL enabled
> 
>
> Key: NIFI-4616
> URL: https://issues.apache.org/jira/browse/NIFI-4616
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.4.0
>Reporter: Aldrin Piri
> Fix For: 1.1.0
>
>
> If I use ConsumeKafka and point to a broker that is in a bad state, I see 
> ConsumeKafka block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2276: NIFI-4615 processor status is set to the ProcessorS...

[mcgilman]

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151695374
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

In addition to setting this here, we need to update it when merging 
responses in a clustered scenario. This merging happens to account for cases 
when a processor is invalid based on an environmental condition. A good example 
of this is a processor configured with a directory where that directory does 
not exist on one node of a cluster. On that node, the processor is invalid, but 
on the others that processor would be considered stopped. In this case, we need 
to ensure the invalid run status takes precedence. You can see an example of 
this here [1].

I think the easiest way to handle this would be to update the runStatus in 
the ProcessorStatusDTO when the method referenced in [1] returns when 
appropriate. Let me know if you have any questions about this.

[1] 
https://github.com/apache/nifi/blob/2da72f15243ef62d47369e8a87cc202a82dbe004/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-cluster/src/main/java/org/apache/nifi/cluster/manager/StatusMerger.java#L403


---

[GitHub] nifi pull request #2276: NIFI-4615 processor status is set to the ProcessorS...

[mcgilman]

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151693413
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
 
 final ProcessorStatusSnapshotDTO snapshot = new 
ProcessorStatusSnapshotDTO();
 dto.setAggregateSnapshot(snapshot);
 
 snapshot.setId(procStatus.getId());
 snapshot.setGroupId(procStatus.getGroupId());
 snapshot.setName(procStatus.getName());
+snapshot.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

This is already being set a few lines below.


---

[jira] [Created] (NIFI-4615) Processor status is not reported with the API

[JIRA]

Sébastien Bouchex Bellomié created NIFI-4615:


 Summary: Processor status is not reported with the API
 Key: NIFI-4615
 URL: https://issues.apache.org/jira/browse/NIFI-4615
 Project: Apache NiFi
  Issue Type: Bug
  Components: Configuration Management
Affects Versions: 1.4.0
Reporter: Sébastien Bouchex Bellomié


* Start a processor
* Request its status with the Processor/get/{id] API

Issue : ProcessorEntity.status.runStatus is always null

Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp issue #191: MINIFICPP-114 Consolidate JSON API use to RapidJ...

[achristianson]

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@phrocker There are some benchmarks over here: 
https://github.com/miloyip/nativejson-benchmark


---

[jira] [Updated] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri updated NIFI-4616:
--
Reporter: Aldrin Piri  (was: Mark Payne)

> ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to 
> communicate with Kafka broker that is SSL enabled
> 
>
> Key: NIFI-4616
> URL: https://issues.apache.org/jira/browse/NIFI-4616
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Aldrin Piri
> Fix For: 1.1.0
>
>
> If I use ConsumeKafka and point to a broker that is in a bad state, I see 
> ConsumeKafka block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled

[Aldrin Piri (JIRA)]

Aldrin Piri created NIFI-4616:
-

 Summary: ConsumeKafka and ConsumeKafka_0_10 can block indefinitely 
if unable to communicate with Kafka broker that is SSL enabled
 Key: NIFI-4616
 URL: https://issues.apache.org/jira/browse/NIFI-4616
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Reporter: Mark Payne
Assignee: Mark Payne
 Fix For: 1.1.0


If I use ConsumeKafka and point to a broker that is in a bad state, I see 
ConsumeKafka block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri reassigned NIFI-4616:
-

Assignee: (was: Mark Payne)

> ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to 
> communicate with Kafka broker that is SSL enabled
> 
>
> Key: NIFI-4616
> URL: https://issues.apache.org/jira/browse/NIFI-4616
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
> Fix For: 1.1.0
>
>
> If I use ConsumeKafka and point to a broker that is in a bad state, I see 
> ConsumeKafka block indefinitely.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257018#comment-16257018
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@calebj with regard to the license, I think @phrocker is just referring to 
adding RapidJSON's license text to our LICENSE file. If you look in there, for 
every project we include in our thirdparty/ dir, we mention that we did that 
and what the license of that project is.

RapidJSON is MIT license which is fully compatible. A good reference is 
https://www.apache.org/legal/resolved.html

So I think we're good if you copy their LICENSE 
(https://github.com/Tencent/rapidjson/blob/master/license.txt) into our LICENSE 
using the same format as the others.


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #183: MINIFICPP-301 Added initial implementatio...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/183


---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257093#comment-16257093
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151706697
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

You cannot just set target.setRunStatus(toMerge.getRunStatus) in case 
target is invalid. I believe you have two options...

1) Duplicate the isValid check

if (RunStatus.Invalid.name().equals(toMerge.getRunStatus())) {
target.setRunStatus(RunStatus.Invalid.name());
}

2) Copy the calculated runStatus from the aggregate snapshot

target.setRunStatus(target.getAggregateSnapshot().getRunStatus());


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2276: NIFI-4615 processor status is set to the ProcessorS...

[mcgilman]

Github user mcgilman commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151706697
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

You cannot just set target.setRunStatus(toMerge.getRunStatus) in case 
target is invalid. I believe you have two options...

1) Duplicate the isValid check

if (RunStatus.Invalid.name().equals(toMerge.getRunStatus())) {
target.setRunStatus(RunStatus.Invalid.name());
}

2) Copy the calculated runStatus from the aggregate snapshot

target.setRunStatus(target.getAggregateSnapshot().getRunStatus());


---

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257117#comment-16257117
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user calebj commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
I know that it's MIT licensed, but their license.txt comes with others 
tacked on for subcomponents. If you think they're all compatible, I'll copy all 
of them in.


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp issue #191: MINIFICPP-114 Consolidate JSON API use to RapidJ...

[calebj]

Github user calebj commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
I know that it's MIT licensed, but their license.txt comes with others 
tacked on for subcomponents. If you think they're all compatible, I'll copy all 
of them in.


---

[GitHub] nifi-minifi-cpp issue #191: MINIFICPP-114 Consolidate JSON API use to RapidJ...

[achristianson]

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@calebj we're 100% golden on the licence.

We have:
- RapidJSON itself under MIT (Apache Category A)
- msinttypes r29 under BSD (Apache Category A)
- JSON_checker under JSON (Recently banned/put into to Apache Category X)

Upon closer inspection of the JSON_checker, the RapidJSON license says this:

"To avoid the problematic JSON license in your own projects, it's 
sufficient to exclude the bin/jsonchecker/ directory, as it's the only code 
under the JSON license."

So, strip out the bin/jsonchecker/ dir and we're fully in Category A 
territory.


---

[jira] [Commented] (NIFI-4400) Advanced UI with code editor for scripted processors

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257260#comment-16257260
 ] 

ASF GitHub Bot commented on NIFI-4400:
--

Github user moranr commented on the issue:

https://github.com/apache/nifi/pull/2269
  
@yuri1969 the behavior of the code editor addition looks good! Changes made 
between the Script Engine/Body properties stay in place as changes are made and 
as you move between the standard/advanced editors. I did not experience 
anything odd there.

I agree with others about how closing it should return to point from which 
you came.

Regarding the save/close behavior - I would not expect 'SAVE' to close as 
well. It is, however, not very intuitive to save then have to go up the the 'X' 
button to close it out. Ideally I'd suggest an auto-save behavior that 
continuously notifies the user their work has been saved after a certain amount 
of time. Then place a close/done/ok button at the bottom right to close it out. 
Alternatively, and probably easier, group a separate 'Save' button with the 
code editor and add a close/done/ok button at the bottom right. There is more 
of a natural flow that way, working from the top left to the bottom right of 
the dialog.

Also, another idea, with the exception of Jolt these advanced UIs are 
pretty simple in that you're only choosing a type (engine) then entering code 
(body). It would be nice to simply have access the code editor directly from 
the property list when you click the cell to edit the value. This would 
eliminate the need for the advanced UI.


> Advanced UI with code editor for scripted processors
> 
>
> Key: NIFI-4400
> URL: https://issues.apache.org/jira/browse/NIFI-4400
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Extensions
>Reporter: Pierre Villard
>Assignee: Yuri
>
> For the scripted processors it would nice to add an advanced UI with a "code 
> editor mode" that would provide some very useful features when typing code:
> - indentation
> - code highlighting
> - do not close the window when hitting enter
> etc
> The use of codemirror.js (as already done for EL auto-completion) sounds like 
> a good option.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4400) Advanced UI with code editor for scripted processors

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257272#comment-16257272
 ] 

ASF GitHub Bot commented on NIFI-4400:
--

Github user moranr commented on the issue:

https://github.com/apache/nifi/pull/2269
  
To add to my previous comments, I also notice some styling changes, not 
only in the advanced UI but other areas of the app as well. For example:

- Visible elements in the toolbar, status bar, and canvas palettes now have 
a border-radius being applied; previously they had square corners (i.e., no 
border-radius)

- Other areas such as shells and dialogs where the same canvas palette 
style buttons appear are being affected as well (e.g., 'Open in New Window', 
'Close', 'Refresh', etc.)

- Scott noted the fa-align icon sitting a pixel or two higher - I think 
this is occurring on many other 'fa-...' icons. I notice shifted positions in 
the canvas palette buttons, dialogs, and shells too

I would suggest that unless a new UI component is being introduced, we use 
established styles to maintain a consistent look. From what I've seen I don't 
believe there is a need to introduce anything new.

In the advanced UIs:

- the primary buttons (e.g., 'SAVE') have a border-radius now and also as 
Scott noted some position shifting occurs on hover

- select/combo box styling is completely different, including the menu that 
is shown when it is clicked on

- the 'Format' button should be square as are others that share the same 
look

I would also suggest capitalizing 'ruby', 'lua', and 'python' --> Ruby, 
Lua, Python


> Advanced UI with code editor for scripted processors
> 
>
> Key: NIFI-4400
> URL: https://issues.apache.org/jira/browse/NIFI-4400
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI, Extensions
>Reporter: Pierre Villard
>Assignee: Yuri
>
> For the scripted processors it would nice to add an advanced UI with a "code 
> editor mode" that would provide some very useful features when typing code:
> - indentation
> - code highlighting
> - do not close the window when hitting enter
> etc
> The use of codemirror.js (as already done for EL auto-completion) sounds like 
> a good option.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4614) ManagedRangerAuthorizer: Wildcard policies

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-4614:
--
Status: Patch Available  (was: In Progress)

> ManagedRangerAuthorizer: Wildcard policies
> --
>
> Key: NIFI-4614
> URL: https://issues.apache.org/jira/browse/NIFI-4614
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>
> The ManagedRangerAuthorizer performs a best effort policy conversion between 
> Ranger and NiFi domain models. While all policies are retained for access 
> decisions, some policies are filtered out for viewing purposes only. This 
> includes exclude and recursive policies. We need to similarly account for 
> wildcard policies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4614) ManagedRangerAuthorizer: Wildcard policies

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257409#comment-16257409
 ] 

ASF GitHub Bot commented on NIFI-4614:
--

GitHub user mcgilman opened a pull request:

https://github.com/apache/nifi/pull/2277

NIFI-4614: ManagedRangerAuthorizer: Wildcard policies

NIFI-4614:
- Updating the types of resources that are filtered out for viewing 
purposes. Updates include resources with no values and resources that contain 
wildcards.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mcgilman/nifi NIFI-4614

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2277.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 #2277


commit 219c5e4a1df5de324071607c01d8eb85d74a74df
Author: Matt Gilman 
Date:   2017-11-17T19:05:49Z

NIFI-4614:
- Updating the types of resources that are filtered out for viewing 
purposes. Updates include resources with no values and resources that contain 
wildcards.




> ManagedRangerAuthorizer: Wildcard policies
> --
>
> Key: NIFI-4614
> URL: https://issues.apache.org/jira/browse/NIFI-4614
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>
> The ManagedRangerAuthorizer performs a best effort policy conversion between 
> Ranger and NiFi domain models. While all policies are retained for access 
> decisions, some policies are filtered out for viewing purposes only. This 
> includes exclude and recursive policies. We need to similarly account for 
> wildcard policies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2277: NIFI-4614: ManagedRangerAuthorizer: Wildcard polici...

[mcgilman]

GitHub user mcgilman opened a pull request:

https://github.com/apache/nifi/pull/2277

NIFI-4614: ManagedRangerAuthorizer: Wildcard policies

NIFI-4614:
- Updating the types of resources that are filtered out for viewing 
purposes. Updates include resources with no values and resources that contain 
wildcards.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mcgilman/nifi NIFI-4614

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2277.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 #2277


commit 219c5e4a1df5de324071607c01d8eb85d74a74df
Author: Matt Gilman 
Date:   2017-11-17T19:05:49Z

NIFI-4614:
- Updating the types of resources that are filtered out for viewing 
purposes. Updates include resources with no values and resources that contain 
wildcards.




---

[jira] [Resolved] (MINIFICPP-292) GetFile uses non-portable d_type property to determine if path is a directory

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved MINIFICPP-292.
---
Resolution: Fixed

> GetFile uses non-portable d_type property to determine if path is a directory
> -
>
> Key: MINIFICPP-292
> URL: https://issues.apache.org/jira/browse/MINIFICPP-292
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> Using entry->d_type is not portable and will fail on some systems.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-310) Docker build fails

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257496#comment-16257496
 ] 

ASF GitHub Bot commented on MINIFICPP-310:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/192
  
reviewing


> Docker build fails
> --
>
> Key: MINIFICPP-310
> URL: https://issues.apache.org/jira/browse/MINIFICPP-310
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Blocker
> Fix For: 0.3.0
>
>
> The docker build is currently failing for a multitude of reasons, mainly to 
> do with compile-time dependencies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp issue #192: MINIFICPP-310 Move to stable 3.5 Alpine release ...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/192
  
reviewing


---

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257387#comment-16257387
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@calebj we're 100% golden on the licence.

We have:
- RapidJSON itself under MIT (Apache Category A)
- msinttypes r29 under BSD (Apache Category A)
- JSON_checker under JSON (Recently banned/put into to Apache Category X)

Upon closer inspection of the JSON_checker, the RapidJSON license says this:

"To avoid the problematic JSON license in your own projects, it's 
sufficient to exclude the bin/jsonchecker/ directory, as it's the only code 
under the JSON license."

So, strip out the bin/jsonchecker/ dir and we're fully in Category A 
territory.


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #190: MINIFI-308 Ensure that all core resources...

[achristianson]

Github user achristianson commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/190#discussion_r151761757
  
--- Diff: libminifi/test/script-tests/ExecuteScriptTests.cpp ---
@@ -1,640 +0,0 @@
-/**
--- End diff --

@phrocker Yes, these tests never should have been in there. The file was a 
relic from before Python & Lua were split into separate files.


---

[jira] [Updated] (NIFI-4166) Create toolkit module to generate and build Swagger API library for NiFi

[Michael Moser (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Moser updated NIFI-4166:

Status: Patch Available  (was: Open)

> Create toolkit module to generate and build Swagger API library for NiFi
> 
>
> Key: NIFI-4166
> URL: https://issues.apache.org/jira/browse/NIFI-4166
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Tools and Build
>Reporter: Joe Skora
>Assignee: Joe Skora
>Priority: Minor
>
> Create a new toolkit module to generate the Swagger API library based on the 
> current REST API annotations in the NiFi source by way of the Swagger Codegen 
> Maven Plugin.  This should make it easier access to access the REST API from 
> Java code or Groovy scripts.
> Swagger Codegen support other languages, so this could be expanded for 
> additional API client types.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-289) Support PutFile property: Create Missing Directories

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved MINIFICPP-289.
---
Resolution: Fixed

> Support PutFile property: Create Missing Directories 
> -
>
> Key: MINIFICPP-289
> URL: https://issues.apache.org/jira/browse/MINIFICPP-289
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>
> Creating missing directories when a file is put is particularly important 
> when using generated file names. This should be supported in MiNiFi - C++.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2269: NIFI-4400 - Advanced UI with code editor for...

[moranr]

Github user moranr commented on the issue:

https://github.com/apache/nifi/pull/2269
  
@yuri1969 the behavior of the code editor addition looks good! Changes made 
between the Script Engine/Body properties stay in place as changes are made and 
as you move between the standard/advanced editors. I did not experience 
anything odd there.

I agree with others about how closing it should return to point from which 
you came.

Regarding the save/close behavior - I would not expect 'SAVE' to close as 
well. It is, however, not very intuitive to save then have to go up the the 'X' 
button to close it out. Ideally I'd suggest an auto-save behavior that 
continuously notifies the user their work has been saved after a certain amount 
of time. Then place a close/done/ok button at the bottom right to close it out. 
Alternatively, and probably easier, group a separate 'Save' button with the 
code editor and add a close/done/ok button at the bottom right. There is more 
of a natural flow that way, working from the top left to the bottom right of 
the dialog.

Also, another idea, with the exception of Jolt these advanced UIs are 
pretty simple in that you're only choosing a type (engine) then entering code 
(body). It would be nice to simply have access the code editor directly from 
the property list when you click the cell to edit the value. This would 
eliminate the need for the advanced UI.


---

[GitHub] nifi issue #2269: NIFI-4400 - Advanced UI with code editor for...

[moranr]

Github user moranr commented on the issue:

https://github.com/apache/nifi/pull/2269
  
To add to my previous comments, I also notice some styling changes, not 
only in the advanced UI but other areas of the app as well. For example:

- Visible elements in the toolbar, status bar, and canvas palettes now have 
a border-radius being applied; previously they had square corners (i.e., no 
border-radius)

- Other areas such as shells and dialogs where the same canvas palette 
style buttons appear are being affected as well (e.g., 'Open in New Window', 
'Close', 'Refresh', etc.)

- Scott noted the fa-align icon sitting a pixel or two higher - I think 
this is occurring on many other 'fa-...' icons. I notice shifted positions in 
the canvas palette buttons, dialogs, and shells too

I would suggest that unless a new UI component is being introduced, we use 
established styles to maintain a consistent look. From what I've seen I don't 
believe there is a need to introduce anything new.

In the advanced UIs:

- the primary buttons (e.g., 'SAVE') have a border-radius now and also as 
Scott noted some position shifting occurs on hover

- select/combo box styling is completely different, including the menu that 
is shown when it is clicked on

- the 'Format' button should be square as are others that share the same 
look

I would also suggest capitalizing 'ruby', 'lua', and 'python' --> Ruby, 
Lua, Python


---

[GitHub] nifi-registry pull request #41: NIFIREG-52 Add Kerberos Support

[kevdoran]

GitHub user kevdoran opened a pull request:

https://github.com/apache/nifi-registry/pull/41

NIFIREG-52 Add Kerberos Support

**This builds upon #37 and should not be merged until that PR is closed.**

Changes include: 

- KerberosIdentityProvider: an IdentityProvider extension for 
username/password login
- KerberosSpnegoIdentityProvider: authenticates Kerberos tickets over 
SPNEGO exchange with client and mutual Kerberos server
- Adds NiFiRegistryProperties fields for configuring 
KerberosSpnegoIdentityProvider
- Adds a dedicated endpoint for clients to use to generate a JWT using a 
Kerberos Ticket (backed by KerberosSpnegoIP)
- Adds NotAllowedExceptionMapper that returns 405 for NotAllowedExceptions 
thrown in the Jersey framework
- Other misc cleanup

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kevdoran/nifi-registry NIFIREG-52

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-registry/pull/41.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 #41


commit 05ef1821455331279bc5761c45834a5474c72e63
Author: Kevin Doran 
Date:   2017-10-30T18:39:56Z

NIFIREG-45 Refactor LoginIdentityProvider interface as a more generic and 
flexible IdentityProvider interface

commit 673d06a703d19256a8f23ef020a64522d433ef2f
Author: Kevin Doran 
Date:   2017-11-16T15:30:42Z

NIFIREG-52 Add Kerberos Support

- KerberosIdentityProvider: an IdentityProvider extension for 
username/password login
- KerberosSpnegoIdentityProvider: authenticates Kerberos tickets over 
SPNEGO exchange with client and mutual Kerberos server
- Adds NiFiRegistryProperties fields for configuring 
KerberosSpnegoIdentityProvider
- Adds a dedicated endpoint for clients to use to generate a JWT using a 
Kerberos Ticket (backed by KerberosSpnegoIP)
- Adds NotAllowedExceptionMapper that returns 405 for NotAllowedExceptions 
thrown in the Jersey framework
- Other misc cleanup




---

[jira] [Commented] (NIFIREG-52) Kerberos Identity Provider

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257351#comment-16257351
 ] 

ASF GitHub Bot commented on NIFIREG-52:
---

GitHub user kevdoran opened a pull request:

https://github.com/apache/nifi-registry/pull/41

NIFIREG-52 Add Kerberos Support

**This builds upon #37 and should not be merged until that PR is closed.**

Changes include: 

- KerberosIdentityProvider: an IdentityProvider extension for 
username/password login
- KerberosSpnegoIdentityProvider: authenticates Kerberos tickets over 
SPNEGO exchange with client and mutual Kerberos server
- Adds NiFiRegistryProperties fields for configuring 
KerberosSpnegoIdentityProvider
- Adds a dedicated endpoint for clients to use to generate a JWT using a 
Kerberos Ticket (backed by KerberosSpnegoIP)
- Adds NotAllowedExceptionMapper that returns 405 for NotAllowedExceptions 
thrown in the Jersey framework
- Other misc cleanup

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kevdoran/nifi-registry NIFIREG-52

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi-registry/pull/41.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 #41


commit 05ef1821455331279bc5761c45834a5474c72e63
Author: Kevin Doran 
Date:   2017-10-30T18:39:56Z

NIFIREG-45 Refactor LoginIdentityProvider interface as a more generic and 
flexible IdentityProvider interface

commit 673d06a703d19256a8f23ef020a64522d433ef2f
Author: Kevin Doran 
Date:   2017-11-16T15:30:42Z

NIFIREG-52 Add Kerberos Support

- KerberosIdentityProvider: an IdentityProvider extension for 
username/password login
- KerberosSpnegoIdentityProvider: authenticates Kerberos tickets over 
SPNEGO exchange with client and mutual Kerberos server
- Adds NiFiRegistryProperties fields for configuring 
KerberosSpnegoIdentityProvider
- Adds a dedicated endpoint for clients to use to generate a JWT using a 
Kerberos Ticket (backed by KerberosSpnegoIP)
- Adds NotAllowedExceptionMapper that returns 405 for NotAllowedExceptions 
thrown in the Jersey framework
- Other misc cleanup




> Kerberos Identity Provider
> --
>
> Key: NIFIREG-52
> URL: https://issues.apache.org/jira/browse/NIFIREG-52
> Project: NiFi Registry
>  Issue Type: New Feature
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>
> Implement a new NiFi Registry IdentityProvider implementation backed by 
> Kerberos that will allow a JWT to be generated given a valid Kerberos ticket. 
> Will be similar to the NiFi implementation of KerberosProvider



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (MINIFICPP-310) Docker build fails

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved MINIFICPP-310.
---
Resolution: Fixed

> Docker build fails
> --
>
> Key: MINIFICPP-310
> URL: https://issues.apache.org/jira/browse/MINIFICPP-310
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Blocker
> Fix For: 0.3.0
>
>
> The docker build is currently failing for a multitude of reasons, mainly to 
> do with compile-time dependencies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MINIFICPP-310) Docker build fails

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257525#comment-16257525
 ] 

ASF GitHub Bot commented on MINIFICPP-310:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/192


> Docker build fails
> --
>
> Key: MINIFICPP-310
> URL: https://issues.apache.org/jira/browse/MINIFICPP-310
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Blocker
> Fix For: 0.3.0
>
>
> The docker build is currently failing for a multitude of reasons, mainly to 
> do with compile-time dependencies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257531#comment-16257531
 ] 

ASF subversion and git services commented on NIFI-4615:
---

Commit c89d79336435ee754c0f297a9fa78f059c321a59 in nifi's branch 
refs/heads/master from [~sbouc...@infovista.com]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=c89d793 ]

NIFI-4615
- processor status is set to the ProcessorStatusDTO object
- This closes #2276


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (NIFI-4615) Processor status is not reported with the API

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman resolved NIFI-4615.
---
   Resolution: Fixed
Fix Version/s: 1.5.0

> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
> Fix For: 1.5.0
>
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257534#comment-16257534
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/2276


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
> Fix For: 1.5.0
>
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2278: NIFI-4617: TestCSVRecordReader Test Failure

[mcgilman]

GitHub user mcgilman opened a pull request:

https://github.com/apache/nifi/pull/2278

NIFI-4617: TestCSVRecordReader Test Failure

NIFI-4617:
- Ensuring a charset is specified when converting a string into bytes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mcgilman/nifi NIFI-4617

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2278.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 #2278


commit bd9679899311b9592d93a9b4fb6d81811e3b3df2
Author: Matt Gilman 
Date:   2017-11-17T21:03:25Z

NIFI-4617:
- Ensuring a charset is specified when convert a string into bytes.




---

[GitHub] nifi-minifi-cpp issue #192: MINIFICPP-310 Move to stable 3.5 Alpine release ...

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/192
  
changes look good.  build and resulting image all work as anticipated.  
will get this merged in.  thank you!


---

[jira] [Commented] (MINIFICPP-310) Docker build fails

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257522#comment-16257522
 ] 

ASF GitHub Bot commented on MINIFICPP-310:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/192
  
changes look good.  build and resulting image all work as anticipated.  
will get this merged in.  thank you!


> Docker build fails
> --
>
> Key: MINIFICPP-310
> URL: https://issues.apache.org/jira/browse/MINIFICPP-310
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Blocker
> Fix For: 0.3.0
>
>
> The docker build is currently failing for a multitude of reasons, mainly to 
> do with compile-time dependencies.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257533#comment-16257533
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2276
  
Thanks @sbouchex! This has been merged to master.


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
> Fix For: 1.5.0
>
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp pull request #192: MINIFICPP-310 Move to stable 3.5 Alpine r...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/192


---

[GitHub] nifi issue #2276: NIFI-4615 processor status is set to the ProcessorStatusDT...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2276
  
Thanks @sbouchex! This has been merged to master.


---

[jira] [Created] (NIFI-4617) TestCSVRecordReader Test Failure

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-4617:
-

 Summary: TestCSVRecordReader Test Failure
 Key: NIFI-4617
 URL: https://issues.apache.org/jira/browse/NIFI-4617
 Project: Apache NiFi
  Issue Type: Bug
  Components: Tools and Build
Reporter: Matt Gilman
Assignee: Matt Gilman


Currently TestCSVRecordReader#testUTF8 fails with the following message:

Failed tests: 
  TestCSVRecordReader.testUTF8:81 expected:<[黃凱揚]> but was:<[???]>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4617) TestCSVRecordReader Test Failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257569#comment-16257569
 ] 

ASF GitHub Bot commented on NIFI-4617:
--

GitHub user mcgilman opened a pull request:

https://github.com/apache/nifi/pull/2278

NIFI-4617: TestCSVRecordReader Test Failure

NIFI-4617:
- Ensuring a charset is specified when converting a string into bytes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mcgilman/nifi NIFI-4617

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2278.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 #2278


commit bd9679899311b9592d93a9b4fb6d81811e3b3df2
Author: Matt Gilman 
Date:   2017-11-17T21:03:25Z

NIFI-4617:
- Ensuring a charset is specified when convert a string into bytes.




> TestCSVRecordReader Test Failure
> 
>
> Key: NIFI-4617
> URL: https://issues.apache.org/jira/browse/NIFI-4617
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>
> Currently TestCSVRecordReader#testUTF8 fails with the following message:
> Failed tests: 
>   TestCSVRecordReader.testUTF8:81 expected:<[黃凱揚]> but was:<[???]>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (NIFI-4617) TestCSVRecordReader Test Failure

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-4617:
--
Status: Patch Available  (was: In Progress)

> TestCSVRecordReader Test Failure
> 
>
> Key: NIFI-4617
> URL: https://issues.apache.org/jira/browse/NIFI-4617
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Tools and Build
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>
> Currently TestCSVRecordReader#testUTF8 fails with the following message:
> Failed tests: 
>   TestCSVRecordReader.testUTF8:81 expected:<[黃凱揚]> but was:<[???]>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2279: NIFI-4501 Changed request header handling logic.

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2279
  
Will review...


---

[jira] [Commented] (NIFI-4501) Refactor header parsing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257853#comment-16257853
 ] 

ASF GitHub Bot commented on NIFI-4501:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2279
  
Will review...


> Refactor header parsing
> ---
>
> Key: NIFI-4501
> URL: https://issues.apache.org/jira/browse/NIFI-4501
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.4.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: header
>
> In some places, the HTTP headers are not parsed correctly. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi-minifi-cpp issue #191: MINIFICPP-114 Consolidate JSON API use to RapidJ...

[calebj]

Github user calebj commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@achristianson something in the master branch is failing. Looks like 
something in the commit before the latest one, 
9b9c3354330d525cfdd50f656ae42fc3da80764c, broke it.

Regarding the LICENSE, there are a handful of them. IANAL, so can someone 
look over [rapidjson's 
license.txt](https://github.com/Tencent/rapidjson/blob/master/license.txt) and 
see what might have to be left out, if anything?


---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257009#comment-16257009
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2276
  
@sbouchex This is a great catch and thanks for the contribution! Reviewing 
the code it appears that the runStatus was moved into the status snapshot 
likely during the 0.x -> 1.x transtion. This value is being set currently and 
is what the UI uses to render the status. However, with the runStatus still 
being available in the status it makes sense to populate it as well. I'll 
continue the review by commenting on the code...


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2276: NIFI-4615 processor status is set to the ProcessorS...

[sbouchex]

Github user sbouchex commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151703532
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

So, something like target.setRunStatus(toMerge.getRunStatus()); ?


---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257079#comment-16257079
 ] 

ASF GitHub Bot commented on NIFI-4615:
--

Github user sbouchex commented on a diff in the pull request:

https://github.com/apache/nifi/pull/2276#discussion_r151703532
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/api/dto/DtoFactory.java
 ---
@@ -1083,13 +1083,15 @@ public ProcessorStatusDTO 
createProcessorStatusDto(final ProcessorStatus procSta
 dto.setGroupId(procStatus.getGroupId());
 dto.setName(procStatus.getName());
 dto.setStatsLastRefreshed(new Date());
+dto.setRunStatus(procStatus.getRunStatus().toString());
--- End diff --

So, something like target.setRunStatus(toMerge.getRunStatus()); ?


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4501) Refactor header parsing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257750#comment-16257750
 ] 

ASF GitHub Bot commented on NIFI-4501:
--

GitHub user alopresto opened a pull request:

https://github.com/apache/nifi/pull/2279

NIFI-4501 Changed request header handling logic.

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alopresto/nifi NIFI-4501-rebased-squashed

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2279.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 #2279


commit 403f72025d3aa50f5f281506c4b2321979a1d6b1
Author: Andy LoPresto 
Date:   2017-11-01T00:00:03Z

NIFI-4501 Changed request header handling logic.




> Refactor header parsing
> ---
>
> Key: NIFI-4501
> URL: https://issues.apache.org/jira/browse/NIFI-4501
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.4.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: header
>
> In some places, the HTTP headers are not parsed correctly. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2279: NIFI-4501 Changed request header handling logic.

[alopresto]

GitHub user alopresto opened a pull request:

https://github.com/apache/nifi/pull/2279

NIFI-4501 Changed request header handling logic.

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alopresto/nifi NIFI-4501-rebased-squashed

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/2279.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 #2279


commit 403f72025d3aa50f5f281506c4b2321979a1d6b1
Author: Andy LoPresto 
Date:   2017-11-01T00:00:03Z

NIFI-4501 Changed request header handling logic.




---

[jira] [Updated] (NIFI-4618) Add documentation for context path whitelisting

[Andy LoPresto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-4618:

Affects Version/s: (was: 1.4.0)
   1.5.0

> Add documentation for context path whitelisting
> ---
>
> Key: NIFI-4618
> URL: https://issues.apache.org/jira/browse/NIFI-4618
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.5.0
>Reporter: Andy LoPresto
>Priority: Minor
>  Labels: documentation, proxy
>
> In NIFI-4501 we introduced a new {{nifi.properties}} property 
> {{nifi.web.proxy.context.path}} to allow whitelisting context paths when 
> using a proxy. The use of this property and the expected formatting should be 
> documented in the Admin Guide. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi pull request #2279: NIFI-4501 Changed request header handling logic.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/2279


---

[jira] [Commented] (NIFI-4501) Refactor header parsing

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257887#comment-16257887
 ] 

ASF subversion and git services commented on NIFI-4501:
---

Commit 5d643edfaba4f5369c94ee1b4eaa5c59e3a9f37a in nifi's branch 
refs/heads/master from [~alopresto]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5d643ed ]

NIFI-4501
- Changed request header handling logic.
- Removed unnecessary Maven dependency.
- This closes #2279


> Refactor header parsing
> ---
>
> Key: NIFI-4501
> URL: https://issues.apache.org/jira/browse/NIFI-4501
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.4.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: header
>
> In some places, the HTTP headers are not parsed correctly. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-4501) Refactor header parsing

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFI-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257888#comment-16257888
 ] 

ASF GitHub Bot commented on NIFI-4501:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/2279


> Refactor header parsing
> ---
>
> Key: NIFI-4501
> URL: https://issues.apache.org/jira/browse/NIFI-4501
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.4.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: header
>
> In some places, the HTTP headers are not parsed correctly. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] nifi issue #2279: NIFI-4501 Changed request header handling logic.

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2279
  
Thanks @alopresto! This has been merged to master.


---

[jira] [Resolved] (NIFI-4501) Refactor header parsing

[Matt Gilman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman resolved NIFI-4501.
---
   Resolution: Fixed
Fix Version/s: 1.5.0

> Refactor header parsing
> ---
>
> Key: NIFI-4501
> URL: https://issues.apache.org/jira/browse/NIFI-4501
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 1.4.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: header
> Fix For: 1.5.0
>
>
> In some places, the HTTP headers are not parsed correctly. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)