[jira] [Commented] (NIFI-3036) Resource Claim can violate its "isInUse" assumption causing Null Pointer Exceptions

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-3036:
---

very possibly related to this fix 
https://issues.apache.org/jira/browse/NIFI-3671

> Resource Claim can violate its "isInUse" assumption causing Null Pointer 
> Exceptions
> ---
>
> Key: NIFI-3036
> URL: https://issues.apache.org/jira/browse/NIFI-3036
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> I hit a Null Pointer Exception when testing on the lastest master. After 
> digging I believe the root cause to be the assumption explained here[1] being 
> violated.
> Specifically I was replaying events on a disk that was over the threshold for 
> not archiving and seeing this[2] stacktrace. So the claimnant count was 
> increased from 0 when "isWritable" was false causing the ResourceClaim to 
> still be a key in the "writeableClaimStreams" map but have a value of null.
> I have tested on 1.0.0 and was not able to reproduce.
> [1] 
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/repository/claim/StandardResourceClaim.java#L142-L142
> [2] 2016-11-14 16:00:19,783 INFO [Flow Service Tasks Thread-2] 
> o.a.nifi.controller.StandardFlowService Saved flow controller 
> org.apache.nifi.controller.FlowController@6191c12d // Another save pending = 
> false
> 2016-11-14 16:00:21,016 INFO [StandardProcessScheduler Thread-4] 
> o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled 
> GenerateFlowFile[id=01581004-90ba-149c-7ccc-4fe3d2dcfe12] to run with 1 
> threads
> 2016-11-14 16:00:21,017 ERROR [Timer-Driven Process Thread-8] 
> o.a.n.p.standard.GenerateFlowFile 
> GenerateFlowFile[id=01581004-90ba-149c-7ccc-4fe3d2dcfe12] 
> GenerateFlowFile[id=01581004-90ba-149c-7ccc-4fe3d2dcfe12] failed to process 
> due to java.lang.NullPointerException; rolling back session: 
> java.lang.NullPointerException
> 2016-11-14 16:00:21,018 ERROR [Timer-Driven Process Thread-8] 
> o.a.n.p.standard.GenerateFlowFile
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.controller.repository.FileSystemRepository$2.write(FileSystemRepository.java:907)
>  ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.repository.io.DisableOnCloseOutputStream.write(DisableOnCloseOutputStream.java:49)
>  ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.repository.io.ByteCountingOutputStream.write(ByteCountingOutputStream.java:46)
>  ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.repository.io.ByteCountingOutputStream.write(ByteCountingOutputStream.java:41)
>  ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.repository.io.FlowFileAccessOutputStream.write(FlowFileAccessOutputStream.java:78)
>  ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.processors.standard.GenerateFlowFile$1.process(GenerateFlowFile.java:192)
>  ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2321)
>  ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.processors.standard.GenerateFlowFile.onTrigger(GenerateFlowFile.java:189)
>  ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  ~[nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1089)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_74]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_74]
> at 
> 

[jira] [Commented] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3995:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1873
  
i believe i can handle this two liner :-)


> Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated 
> header info
> -
>
> Key: NIFI-3995
> URL: https://issues.apache.org/jira/browse/NIFI-3995
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> The Hwx Schema Registry has changed the way that it serializes & deserializes 
> schema information in the header, so that the 14th byte is no longer used, 
> because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1873: NIFI-3995: No longer use the 14th byte in the header for h...

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/1873
  
i believe i can handle this two liner :-)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3996) MergeContent needs more AttributeStrategy implementations.

[Matthew Wilson (JIRA)]

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

Matthew Wilson updated NIFI-3996:
-
Attachment: (was: KeepFirstAttributeStrategy.txt)

> MergeContent needs more AttributeStrategy implementations.
> --
>
> Key: NIFI-3996
> URL: https://issues.apache.org/jira/browse/NIFI-3996
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Matthew Wilson
>Priority: Minor
>  Labels: features
> Attachments: KeepFirstAttributeStrategy.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The MergeContent processor currently has two strategies for merging 
> properties. We have the need to add a third. We could extend the class but 
> there is not an extension point to do so. Our only current option is to clone 
> and own the processor, which we would rather not do.
> What we need is a "Keep First" (or "Keep Last") implementation which keeps 
> all the properties using the the first property key/value found.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3996) MergeContent needs more AttributeStrategy implementations.

[Matthew Wilson (JIRA)]

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

Matthew Wilson updated NIFI-3996:
-
Attachment: KeepFirstAttributeStrategy.txt

> MergeContent needs more AttributeStrategy implementations.
> --
>
> Key: NIFI-3996
> URL: https://issues.apache.org/jira/browse/NIFI-3996
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Matthew Wilson
>Priority: Minor
>  Labels: features
> Attachments: KeepFirstAttributeStrategy.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The MergeContent processor currently has two strategies for merging 
> properties. We have the need to add a third. We could extend the class but 
> there is not an extension point to do so. Our only current option is to clone 
> and own the processor, which we would rather not do.
> What we need is a "Keep First" (or "Keep Last") implementation which keeps 
> all the properties using the the first property key/value found.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3996) MergeContent needs more AttributeStrategy implementations.

[Matthew Wilson (JIRA)]

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

Matthew Wilson updated NIFI-3996:
-
Description: 
The MergeContent processor currently has two strategies for merging properties. 
We have the need to add a third. We could extend the class but there is not an 
extension point to do so. Our only current option is to clone and own the 
processor, which we would rather not do.

What we need is a "Keep First" implementation which keeps all the properties 
using the the first (or any) property key/value found.


  was:
The MergeContent processor currently has only two strategies for merging 
properties. We have the need to add a third. We could extend the class but 
there is not an extension point to do so. Our only current option is to clone 
and own the processor, which we would rather not do.

What we need is a "Keep First" implementation which keeps all the properties 
using the the first property key/value found.



> MergeContent needs more AttributeStrategy implementations.
> --
>
> Key: NIFI-3996
> URL: https://issues.apache.org/jira/browse/NIFI-3996
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Matthew Wilson
>Priority: Minor
>  Labels: features
> Attachments: KeepFirstAttributeStrategy.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The MergeContent processor currently has two strategies for merging 
> properties. We have the need to add a third. We could extend the class but 
> there is not an extension point to do so. Our only current option is to clone 
> and own the processor, which we would rather not do.
> What we need is a "Keep First" implementation which keeps all the properties 
> using the the first (or any) property key/value found.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3996) MergeContent needs more AttributeStrategy implementations.

[Matthew Wilson (JIRA)]

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

Matthew Wilson updated NIFI-3996:
-
Description: 
The MergeContent processor currently has two strategies for merging properties. 
We have the need to add a third. We could extend the class but there is not an 
extension point to do so. Our only current option is to clone and own the 
processor, which we would rather not do.

What we need is a "Keep First" (or "Keep Last") implementation which keeps all 
the properties using the the first property key/value found.


  was:
The MergeContent processor currently has two strategies for merging properties. 
We have the need to add a third. We could extend the class but there is not an 
extension point to do so. Our only current option is to clone and own the 
processor, which we would rather not do.

What we need is a "Keep First" implementation which keeps all the properties 
using the the first (or any) property key/value found.



> MergeContent needs more AttributeStrategy implementations.
> --
>
> Key: NIFI-3996
> URL: https://issues.apache.org/jira/browse/NIFI-3996
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.2.0
>Reporter: Matthew Wilson
>Priority: Minor
>  Labels: features
> Attachments: KeepFirstAttributeStrategy.txt
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The MergeContent processor currently has two strategies for merging 
> properties. We have the need to add a third. We could extend the class but 
> there is not an extension point to do so. Our only current option is to clone 
> and own the processor, which we would rather not do.
> What we need is a "Keep First" (or "Keep Last") implementation which keeps 
> all the properties using the the first property key/value found.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1873: NIFI-3995: No longer use the 14th byte in the heade...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-3995: No longer use the 14th byte in the header for hwx content-…

…encoded schema reference

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/markap14/nifi NIFI-3995

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

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


commit a7913693c0d7103fd357a6f279ad2203c756
Author: Mark Payne 
Date:   2017-05-31T16:20:02Z

NIFI-3995: No longer use the 14th byte in the header for hwx 
content-encoded schema reference




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp pull request #104: MINIFI-296 - Configurable logging, spdlog...

[apiri]

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

https://github.com/apache/nifi-minifi-cpp/pull/104#discussion_r119173661
  
--- Diff: thirdparty/spdlog-0.13.0/include/spdlog/fmt/bundled/format.h ---
@@ -1,29 +1,29 @@
 /*
-Formatting library for C++
-
-Copyright (c) 2012 - 2016, Victor Zverovich
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-1. Redistributions of source code must retain the above copyright notice, 
this
-list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright 
notice,
-this list of conditions and the following disclaimer in the documentation
-and/or other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS 
IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 
IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE 
LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 
DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
-ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 
THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-*/
+ Formatting library for C++
+
+ Copyright (c) 2012 - 2016, Victor Zverovich
--- End diff --

This is currently listed in our LICENSE file as 2015.  Should update to 
reflect 2016.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-3995:
-
Fix Version/s: 1.3.0
   Status: Patch Available  (was: Open)

> Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated 
> header info
> -
>
> Key: NIFI-3995
> URL: https://issues.apache.org/jira/browse/NIFI-3995
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> The Hwx Schema Registry has changed the way that it serializes & deserializes 
> schema information in the header, so that the 14th byte is no longer used, 
> because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3995:
--

GitHub user markap14 opened a pull request:

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

NIFI-3995: No longer use the 14th byte in the header for hwx content-…

…encoded schema reference

Thank you for submitting a contribution to Apache NiFi.

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

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

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

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

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

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

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

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


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

$ git pull https://github.com/markap14/nifi NIFI-3995

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

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


commit a7913693c0d7103fd357a6f279ad2203c756
Author: Mark Payne 
Date:   2017-05-31T16:20:02Z

NIFI-3995: No longer use the 14th byte in the header for hwx 
content-encoded schema reference




> Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated 
> header info
> -
>
> Key: NIFI-3995
> URL: https://issues.apache.org/jira/browse/NIFI-3995
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> The Hwx Schema Registry has changed the way that it serializes & deserializes 
> schema information in the header, so that the 14th byte is no longer used, 
> because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-minifi-cpp pull request #104: MINIFI-296 - Configurable logging, spdlog...

[apiri]

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

https://github.com/apache/nifi-minifi-cpp/pull/104#discussion_r119377373
  
--- Diff: thirdparty/spdlog-0.13.0/cmake/Config.cmake.in ---
@@ -0,0 +1,24 @@
+# 
*/
+# * Copyright (c) 2015 Ruslan Baratov.
*/
--- End diff --

Looks like we missed inclusion of Ruslan in our LICENSE for spdlog.  This 
was overlooked prior but we can address now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp pull request #104: MINIFI-296 - Configurable logging, spdlog...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3036) Resource Claim can violate its "isInUse" assumption causing Null Pointer Exceptions

[Azrael Seoeun (JIRA)]

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

Azrael Seoeun commented on NIFI-3036:
-

I am not sure this is the right place to comment. If not, let me know where I 
can write the issue.

I am still facing the same Null Pointer Exception.
I am using nifi-1.1.1 and CRON driven scheduling.
Here are the logs:

{code}
2017-05-31 15:01:00,002 ERROR [Timer-Driven Process Thread-5] 
o.a.n.p.standard.GenerateFlowFile 
GenerateFlowFile[id=015a100f-d6ec-1675-aab1-303cd2e1b5fe] 
GenerateFlowFile[id=015a100f-d6ec-1675-aab1-303cd2e1b5fe] failed to process due 
to java.lang.NullPointerException; rolling back session: 
java.lang.NullPointerException
2017-05-31 15:01:00,003 ERROR [Timer-Driven Process Thread-5] 
o.a.n.p.standard.GenerateFlowFile
java.lang.NullPointerException: null
at 
org.apache.nifi.controller.repository.FileSystemRepository$2.write(FileSystemRepository.java:907)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.io.DisableOnCloseOutputStream.write(DisableOnCloseOutputStream.java:49)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.stream.io.ByteCountingOutputStream.write(ByteCountingOutputStream.java:49)
 ~[nifi-utils-1.1.1.jar:1.1.1]
at 
org.apache.nifi.stream.io.ByteCountingOutputStream.write(ByteCountingOutputStream.java:44)
 ~[nifi-utils-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.io.FlowFileAccessOutputStream.write(FlowFileAccessOutputStream.java:78)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processors.standard.GenerateFlowFile$1.process(GenerateFlowFile.java:222)
 ~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2329)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processors.standard.GenerateFlowFile.onTrigger(GenerateFlowFile.java:219)
 ~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 ~[nifi-api-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.scheduling.QuartzSchedulingAgent$2.run(QuartzSchedulingAgent.java:165)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_121]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_121]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_121]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_121]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_121]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
Suppressed: java.lang.NullPointerException: null
at 
org.apache.nifi.controller.repository.FileSystemRepository$2.flush(FileSystemRepository.java:923)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
  
{code}





> Resource Claim can violate its "isInUse" assumption causing Null Pointer 
> Exceptions
> ---
>
> Key: NIFI-3036
> URL: https://issues.apache.org/jira/browse/NIFI-3036
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Mark Payne
>Priority: Blocker
> Fix For: 1.1.0
>
>
> I hit a Null Pointer Exception when testing on the lastest master. After 
> digging I believe the root cause to be the assumption explained here[1] being 
> violated.
> Specifically I was replaying events on a disk that was over the threshold for 
> not archiving and seeing this[2] stacktrace. So the claimnant count was 
> increased from 0 when "isWritable" was false causing the ResourceClaim to 
> still be a key in the "writeableClaimStreams" map but have a value of null.
> I have tested on 1.0.0 and was not able to reproduce.
> [1] 
> 

[jira] [Comment Edited] (NIFI-3036) Resource Claim can violate its "isInUse" assumption causing Null Pointer Exceptions

[Azrael Seoeun (JIRA)]

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

Azrael Seoeun edited comment on NIFI-3036 at 5/31/17 3:49 PM:
--

I am not sure this is the right place to comment. If not, let me know where I 
can write the issue.

I am still facing the same Null Pointer Exception.
I am using nifi-1.1.1 (1 instance) and CRON driven scheduling.
Here are the logs:

{code}
2017-05-31 15:01:00,002 ERROR [Timer-Driven Process Thread-5] 
o.a.n.p.standard.GenerateFlowFile 
GenerateFlowFile[id=015a100f-d6ec-1675-aab1-303cd2e1b5fe] 
GenerateFlowFile[id=015a100f-d6ec-1675-aab1-303cd2e1b5fe] failed to process due 
to java.lang.NullPointerException; rolling back session: 
java.lang.NullPointerException
2017-05-31 15:01:00,003 ERROR [Timer-Driven Process Thread-5] 
o.a.n.p.standard.GenerateFlowFile
java.lang.NullPointerException: null
at 
org.apache.nifi.controller.repository.FileSystemRepository$2.write(FileSystemRepository.java:907)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.io.DisableOnCloseOutputStream.write(DisableOnCloseOutputStream.java:49)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.stream.io.ByteCountingOutputStream.write(ByteCountingOutputStream.java:49)
 ~[nifi-utils-1.1.1.jar:1.1.1]
at 
org.apache.nifi.stream.io.ByteCountingOutputStream.write(ByteCountingOutputStream.java:44)
 ~[nifi-utils-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.io.FlowFileAccessOutputStream.write(FlowFileAccessOutputStream.java:78)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processors.standard.GenerateFlowFile$1.process(GenerateFlowFile.java:222)
 ~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2329)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processors.standard.GenerateFlowFile.onTrigger(GenerateFlowFile.java:219)
 ~[nifi-standard-processors-1.1.1.jar:1.1.1]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 ~[nifi-api-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.scheduling.QuartzSchedulingAgent$2.run(QuartzSchedulingAgent.java:165)
 [nifi-framework-core-1.1.1.jar:1.1.1]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_121]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_121]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_121]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_121]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_121]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
Suppressed: java.lang.NullPointerException: null
at 
org.apache.nifi.controller.repository.FileSystemRepository$2.flush(FileSystemRepository.java:923)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
  
{code}






was (Author: seoeun25):
I am not sure this is the right place to comment. If not, let me know where I 
can write the issue.

I am still facing the same Null Pointer Exception.
I am using nifi-1.1.1 and CRON driven scheduling.
Here are the logs:

{code}
2017-05-31 15:01:00,002 ERROR [Timer-Driven Process Thread-5] 
o.a.n.p.standard.GenerateFlowFile 
GenerateFlowFile[id=015a100f-d6ec-1675-aab1-303cd2e1b5fe] 
GenerateFlowFile[id=015a100f-d6ec-1675-aab1-303cd2e1b5fe] failed to process due 
to java.lang.NullPointerException; rolling back session: 
java.lang.NullPointerException
2017-05-31 15:01:00,003 ERROR [Timer-Driven Process Thread-5] 
o.a.n.p.standard.GenerateFlowFile
java.lang.NullPointerException: null
at 
org.apache.nifi.controller.repository.FileSystemRepository$2.write(FileSystemRepository.java:907)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 
org.apache.nifi.controller.repository.io.DisableOnCloseOutputStream.write(DisableOnCloseOutputStream.java:49)
 ~[nifi-framework-core-1.1.1.jar:1.1.1]
at 

[GitHub] nifi-minifi-cpp pull request #103: MINIFI-177 Incorporating Apache RAT to bu...

[brosander]

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

https://github.com/apache/nifi-minifi-cpp/pull/103#discussion_r119398420
  
--- Diff: cmake/RunApacheRAT.cmake ---
@@ -0,0 +1,44 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+# Find the preferred Apache mirror to use for the download by querying the 
list of mirrors and filtering out 'preferred'
+execute_process(COMMAND curl -s 
https://www.apache.org/dyn/closer.lua/?asjson=1
+COMMAND grep preferred
+COMMAND awk "{print $2}"
+COMMAND tr -d "\""
+TIMEOUT 10
+OUTPUT_STRIP_TRAILING_WHITESPACE
+OUTPUT_VARIABLE MIRROR_URL )
+
+ExternalProject_Add(
--- End diff --

@apiri can we make it so this is only downloaded when we run the rat target?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp pull request #103: MINIFI-177 Incorporating Apache RAT to bu...

[brosander]

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

https://github.com/apache/nifi-minifi-cpp/pull/103#discussion_r119398723
  
--- Diff: cmake/RunApacheRAT.cmake ---
@@ -0,0 +1,44 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+# Find the preferred Apache mirror to use for the download by querying the 
list of mirrors and filtering out 'preferred'
+execute_process(COMMAND curl -s 
https://www.apache.org/dyn/closer.lua/?asjson=1
+COMMAND grep preferred
+COMMAND awk "{print $2}"
+COMMAND tr -d "\""
+TIMEOUT 10
+OUTPUT_STRIP_TRAILING_WHITESPACE
+OUTPUT_VARIABLE MIRROR_URL )
+
+ExternalProject_Add(
+rat-binary
+PREFIX "apache-rat"
+URL 
"${MIRROR_URL}creadur/apache-rat-0.12/apache-rat-0.12-bin.tar.gz"
+URL_HASH SHA1=e84dffe8b354871c29f5078b823a726508474a6c
--- End diff --

@apiri can we use sha256 or sha512? if it's not available from the apache 
mirror, we could precalculate it since it shouldn't change until we upgrade rat


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3996) MergeContent needs more AttributeStrategy implementations.

[Matthew Wilson (JIRA)]

Matthew Wilson created NIFI-3996:


 Summary: MergeContent needs more AttributeStrategy implementations.
 Key: NIFI-3996
 URL: https://issues.apache.org/jira/browse/NIFI-3996
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.2.0
Reporter: Matthew Wilson
Priority: Minor
 Attachments: KeepFirstAttributeStrategy.txt

The MergeContent processor currently has only two strategies for merging 
properties. We have the need to add a third. We could extend the class but 
there is not an extension point to do so. Our only current option is to clone 
and own the processor, which we would rather not do.

What we need is a "Keep First" implementation which keeps all the properties 
using the the first property key/value found.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-4000) Auto-Incremental For GetFTP processor

[YANGFEIRAN (JIRA)]

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

YANGFEIRAN updated NIFI-4000:
-
Description: 
Hello, 

I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 

However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor (it is just a 
property in the JAVA class, can not see it in the UI) in order to record the 
last-modified time for files I have imported. And next time this value can be 
used to filter out those files that I have imported. Never the less, if I 
restart the NIFI, this value will be set back to the beginning. 

I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 

Can anyone add a set function, so the property in the UI can change by it self 
as the processor is running? Or it is only me that missing something that can 
achieve this?

Sorry for my poor English, if I am not clear, just leave comments below.

Best regards,

Feiran

  was:
Hello, 
I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 
However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor (it is just a 
property in the JAVA class, can not see it in the UI) in order to record the 
last-modified time for files I have imported. And next time this value can be 
used to filter out those files that I have imported. Never the less, if I 
restart the NIFI, this value will be set back to the beginning. 
I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 
Can anyone add a set function, so the property in the UI can change by it self 
as the processor is running? Or it is only me that missing something that can 
achieve this?

Best regards,

Feiran


> Auto-Incremental For GetFTP processor 
> --
>
> Key: NIFI-4000
> URL: https://issues.apache.org/jira/browse/NIFI-4000
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: linux
>Reporter: YANGFEIRAN
>  Labels: features
>
> Hello, 
> I am a NIFI user. When I am using the GetFTP processor, I realized that the 
> processor can auto-incrementally import files from FTP only if I configure 
> the processor "Delete Original" as "true". 
> However, sometimes it is forbidden for me to delete any file in the FTP. So, 
> I added a property in the GetFTP and  GetFileTransfer processor (it is just a 
> property in the JAVA class, can not see it in the UI) in order to record the 
> last-modified time for files I have imported. And next time this value can be 
> used to filter out those files that I have imported. Never the less, if I 
> restart the NIFI, this value will be set back to the beginning. 
> I figured out that if I wanted to make it stay still even if NIFI is 
> restarted, I have to set this property back to the processor, as those 
> properties in the UI. But there is no such a set function, those properties 
> as initialized as the processor init. 
> Can anyone add a set function, so the property in the UI can change by it 
> self as the processor is running? Or it is only me that missing something 
> that can achieve this?
> Sorry for my poor English, if I am not clear, just leave comments below.
> Best regards,
> Feiran



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-4000) Auto-Incremental For GetFTP processor

[YANGFEIRAN (JIRA)]

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

YANGFEIRAN updated NIFI-4000:
-
Description: 
Hello, 
I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 
However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor (it is just a 
property in the JAVA class, can not see it in the UI) in order to record the 
last-modified time for files I have imported. And next time this value can be 
used to filter out those files that I have imported. Never the less, if I 
restart the NIFI, this value will be set back to the beginning. 
I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 
Can anyone add a set function, so the property in the UI can change by it self 
as the processor is running? Or it is only me that missing something that can 
achieve this?

Best regards,

Feiran

  was:
Hello, 
I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 
However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor (it is just a 
property in the JAVA class, can not see it in the UI) in order to record the 
last-modified time for files I have imported. And next time this value can be 
used to filter out those files that I have imported. Never the less, if I 
restart the NIFI, this value will be set back to the beginning. 
I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 
Can anyone add a set function, so the property in the UI can change as the 
processor is running? Or it is only me that missing something that can achieve 
this?

Best regards,

Feiran


> Auto-Incremental For GetFTP processor 
> --
>
> Key: NIFI-4000
> URL: https://issues.apache.org/jira/browse/NIFI-4000
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: linux
>Reporter: YANGFEIRAN
>  Labels: features
>
> Hello, 
> I am a NIFI user. When I am using the GetFTP processor, I realized that the 
> processor can auto-incrementally import files from FTP only if I configure 
> the processor "Delete Original" as "true". 
> However, sometimes it is forbidden for me to delete any file in the FTP. So, 
> I added a property in the GetFTP and  GetFileTransfer processor (it is just a 
> property in the JAVA class, can not see it in the UI) in order to record the 
> last-modified time for files I have imported. And next time this value can be 
> used to filter out those files that I have imported. Never the less, if I 
> restart the NIFI, this value will be set back to the beginning. 
> I figured out that if I wanted to make it stay still even if NIFI is 
> restarted, I have to set this property back to the processor, as those 
> properties in the UI. But there is no such a set function, those properties 
> as initialized as the processor init. 
> Can anyone add a set function, so the property in the UI can change by it 
> self as the processor is running? Or it is only me that missing something 
> that can achieve this?
> Best regards,
> Feiran



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-minifi-cpp pull request #109: MINIFI-330: convert const char* to std::s...

[phrocker]

GitHub user phrocker opened a pull request:

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

MINIFI-330: convert const char* to std::string

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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

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

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

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

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

### For code changes:
- [ ] 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?
- [ ] If applicable, have you updated the NOTICE file?

### 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/phrocker/nifi-minifi-cpp MINIFI-330

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

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


commit 07e1d7ce207706d5c53822f4b1a9674f4e28decc
Author: Marc Parisi 
Date:   2017-05-31T23:49:14Z

MINIFI-330: convert const char* to std::string




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3999) DeleteSQS Should Allow Receipt Handle Configuration

[James Wing (JIRA)]

James Wing created NIFI-3999:


 Summary: DeleteSQS Should Allow Receipt Handle Configuration
 Key: NIFI-3999
 URL: https://issues.apache.org/jira/browse/NIFI-3999
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: James Wing
Priority: Trivial


DeleteSQS deletes an SQS message identified by its RECEIPT_HANDLE property.  
However, RECEIPT_HANDLE is not added to the processor to be configured by the 
user.  It works because the default value "$\{sqs.receipt.handle}" matches the 
attribute written by GetSQS, which is likely the 99% use case.  Nonetheless, 
the property descriptor should be added to processor to make this transparent 
and optionally configurable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-4000) Auto-Incremental For GetFTP processor

[YANGFEIRAN (JIRA)]

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

YANGFEIRAN updated NIFI-4000:
-
Description: 
Hello, 
I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 
However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor (it is just a 
property in the JAVA class, can not see it in the UI) in order to record the 
last-modified time for files I have imported. And next time this value can be 
used to filter out those files that I have imported. Never the less, if I 
restart the NIFI, this value will be set back to the beginning. 
I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 
Can anyone add a set function, so the property in the UI can change as the 
processor is running? Or it is only me that missing something that can achieve 
this?

Best regards,

Feiran

  was:
Hello, 
I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 
However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor in order to 
record the last-modified time for files I have imported. And next time this 
value can be used to filter out those files that I have imported. Never the 
less, if I restart the NIFI, this value will be set back to the beginning. 
I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 
Can anyone add a set function, so the property in the UI can change as the 
processor is running? Or it is only me that missing something that can achieve 
this?

Best regards,

Feiran


> Auto-Incremental For GetFTP processor 
> --
>
> Key: NIFI-4000
> URL: https://issues.apache.org/jira/browse/NIFI-4000
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.1.1
> Environment: linux
>Reporter: YANGFEIRAN
>  Labels: features
>
> Hello, 
> I am a NIFI user. When I am using the GetFTP processor, I realized that the 
> processor can auto-incrementally import files from FTP only if I configure 
> the processor "Delete Original" as "true". 
> However, sometimes it is forbidden for me to delete any file in the FTP. So, 
> I added a property in the GetFTP and  GetFileTransfer processor (it is just a 
> property in the JAVA class, can not see it in the UI) in order to record the 
> last-modified time for files I have imported. And next time this value can be 
> used to filter out those files that I have imported. Never the less, if I 
> restart the NIFI, this value will be set back to the beginning. 
> I figured out that if I wanted to make it stay still even if NIFI is 
> restarted, I have to set this property back to the processor, as those 
> properties in the UI. But there is no such a set function, those properties 
> as initialized as the processor init. 
> Can anyone add a set function, so the property in the UI can change as the 
> processor is running? Or it is only me that missing something that can 
> achieve this?
> Best regards,
> Feiran



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-4000) Auto-Incremental For GetFTP processor

[YANGFEIRAN (JIRA)]

YANGFEIRAN created NIFI-4000:


 Summary: Auto-Incremental For GetFTP processor 
 Key: NIFI-4000
 URL: https://issues.apache.org/jira/browse/NIFI-4000
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Affects Versions: 1.1.1
 Environment: linux
Reporter: YANGFEIRAN


Hello, 
I am a NIFI user. When I am using the GetFTP processor, I realized that the 
processor can auto-incrementally import files from FTP only if I configure the 
processor "Delete Original" as "true". 
However, sometimes it is forbidden for me to delete any file in the FTP. So, I 
added a property in the GetFTP and  GetFileTransfer processor in order to 
record the last-modified time for files I have imported. And next time this 
value can be used to filter out those files that I have imported. Never the 
less, if I restart the NIFI, this value will be set back to the beginning. 
I figured out that if I wanted to make it stay still even if NIFI is restarted, 
I have to set this property back to the processor, as those properties in the 
UI. But there is no such a set function, those properties as initialized as the 
processor init. 
Can anyone add a set function, so the property in the UI can change as the 
processor is running? Or it is only me that missing something that can achieve 
this?

Best regards,

Feiran



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-106) Processor Counters should be included in the Status Reports

[Pierre Villard (JIRA)]

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

Pierre Villard commented on NIFI-106:
-

[~jgresock], is NIFI-3293 what you are looking for? Probably not exactly but...

> Processor Counters should be included in the Status Reports
> ---
>
> Key: NIFI-106
> URL: https://issues.apache.org/jira/browse/NIFI-106
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.3.0
>
>
> This would allow a Processor's Status HIstory to show counters that were 
> maintained over time periods instead of having only a single count since 
> system start.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi issue #1696: NIFI-1655 - Add .gitattributes to specifically define

[trixpan]

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1696
  
@jfrazee this seems to be passing tests now. Let me know what you think 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-1655) create .gitattributes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1655:
--

Github user trixpan commented on the issue:

https://github.com/apache/nifi/pull/1696
  
@jfrazee this seems to be passing tests now. Let me know what you think 


> create .gitattributes
> -
>
> Key: NIFI-1655
> URL: https://issues.apache.org/jira/browse/NIFI-1655
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Reporter: Tony Kurc
>Assignee: Andre F de Miranda
>Priority: Minor
>  Labels: cross-platform, environment, git, line-endings
>
> Create a .gitattributes file for the repository for consistent build 
> environment, less dependent on individual environment settings
> https://help.github.com/articles/dealing-with-line-endings/



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3907) Web Api - Response headers

[ASF subversion and git services (JIRA)]

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

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

Commit a4401258a403809b712388fd33ac63af5ee1f385 in nifi's branch 
refs/heads/support/nifi-0.7.x from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a440125 ]

NIFI-3907 Added response headers.

Signed-off-by: Andy LoPresto 


> Web Api - Response headers
> --
>
> Key: NIFI-3907
> URL: https://issues.apache.org/jira/browse/NIFI-3907
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 0.8.0, 1.3.0, 0.7.4
>
>
> Introduce additional response headers to provide necessary instructions to 
> client browsers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3906) UI - Additional user input validation

[ASF subversion and git services (JIRA)]

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

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

Commit 58d2ca2e2c2a54f4709422470f8303e8398c768c in nifi's branch 
refs/heads/support/nifi-0.7.x from [~scottyaslan]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=58d2ca2 ]

NIFI-3906 Added formatting to tables.

Signed-off-by: Andy LoPresto 


> UI - Additional user input validation
> -
>
> Key: NIFI-3906
> URL: https://issues.apache.org/jira/browse/NIFI-3906
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 0.8.0, 1.3.0, 0.7.4
>
>
> Introduce additional validation when handling user-supplied input to ensure 
> appropriate values and output encoding. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3995: This closes #1873. No longer use the 14th byte in the header for hwx 
content-encoded schema reference

Signed-off-by: joewitt 


> Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated 
> header info
> -
>
> Key: NIFI-3995
> URL: https://issues.apache.org/jira/browse/NIFI-3995
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> The Hwx Schema Registry has changed the way that it serializes & deserializes 
> schema information in the header, so that the 14th byte is no longer used, 
> because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1874: NiFi 3973 - Create a new Kudu Processor to ingest d...

[cammachusa]

GitHub user cammachusa opened a pull request:

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

NiFi 3973 - Create a new Kudu Processor to ingest data  

NiFi 3973 - Create a new Kudu Processor to ingest data into Kudu data 
storage. 

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

$ git pull https://github.com/InspurUSA/nifi kudu-processor

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

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


commit d86afc8bdee940d613e7890aa7e4407d7b865a76
Author: cam 
Date:   2017-05-27T00:53:56Z

create Kudu processor

commit fe99b9ebf80c39fb4042fdf5cebc89c8dc69a819
Author: cam 
Date:   2017-05-27T00:57:08Z

Create Kudu processor

commit 96ac872f9d5cb2e75c1affe9fa0a1d95e07d7f2d
Author: cam 
Date:   2017-05-30T18:42:07Z

added more test cases

commit a31c9c2f0e0a9b85ce00921f732a912e29c41c13
Author: cam 
Date:   2017-05-31T19:15:10Z

add 2 more test cases




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3995:
--

Github user asfgit closed the pull request at:

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


> Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated 
> header info
> -
>
> Key: NIFI-3995
> URL: https://issues.apache.org/jira/browse/NIFI-3995
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> The Hwx Schema Registry has changed the way that it serializes & deserializes 
> schema information in the header, so that the 14th byte is no longer used, 
> because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi pull request #1873: NIFI-3995: No longer use the 14th byte in the heade...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3907) Web Api - Response headers

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-3907:
--
Fix Version/s: 0.7.4

> Web Api - Response headers
> --
>
> Key: NIFI-3907
> URL: https://issues.apache.org/jira/browse/NIFI-3907
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 0.8.0, 1.3.0, 0.7.4
>
>
> Introduce additional response headers to provide necessary instructions to 
> client browsers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3906) UI - Additional user input validation

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-3906:
--
Fix Version/s: 0.7.4

> UI - Additional user input validation
> -
>
> Key: NIFI-3906
> URL: https://issues.apache.org/jira/browse/NIFI-3906
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 0.8.0, 1.3.0, 0.7.4
>
>
> Introduce additional validation when handling user-supplied input to ensure 
> appropriate values and output encoding. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (NIFI-106) Processor Counters should be included in the Status Reports

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-106:
--

[~markap14] can we bump this back off 1.3.0.  I think gilman highlighted a very 
good point that needs discussion.
[~jgresock] perhaps file a JIRA to do that as well and connect it to this JIRA?

> Processor Counters should be included in the Status Reports
> ---
>
> Key: NIFI-106
> URL: https://issues.apache.org/jira/browse/NIFI-106
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.3.0
>
>
> This would allow a Processor's Status HIstory to show counters that were 
> maintained over time periods instead of having only a single count since 
> system start.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-3995:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

+1 merged to master.  thanks for adjusting that

> Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated 
> header info
> -
>
> Key: NIFI-3995
> URL: https://issues.apache.org/jira/browse/NIFI-3995
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.3.0
>
>
> The Hwx Schema Registry has changed the way that it serializes & deserializes 
> schema information in the header, so that the 14th byte is no longer used, 
> because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3997) Release Management for 1.3.0

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-3997:
-

 Summary: Release Management for 1.3.0
 Key: NIFI-3997
 URL: https://issues.apache.org/jira/browse/NIFI-3997
 Project: Apache NiFi
  Issue Type: Task
Reporter: Matt Gilman
Assignee: Matt Gilman
 Fix For: 1.3.0






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-3998) Release Management for 0.7.4

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-3998:
-

 Summary: Release Management for 0.7.4
 Key: NIFI-3998
 URL: https://issues.apache.org/jira/browse/NIFI-3998
 Project: Apache NiFi
  Issue Type: Task
Reporter: Matt Gilman
Assignee: Matt Gilman
 Fix For: 0.7.4






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (NIFI-3719) Timezone error in 5-minute statistics processing time

[Matt Gilman (JIRA)]

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

Matt Gilman updated NIFI-3719:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Timezone error in 5-minute statistics processing time
> -
>
> Key: NIFI-3719
> URL: https://issues.apache.org/jira/browse/NIFI-3719
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.2.0, 1.1.1
> Environment: Windows 10 and Java 1.8.0_121.
> Also CentOS 7 with unknown Java version, but at least 1.7.
>Reporter: Michael Hopton
>Assignee: Matt Gilman
>Priority: Minor
>  Labels: patch
> Fix For: 1.3.0
>
> Attachments: 0001-Nifi-3719-Fix-timezone-for-durations.patch
>
>
> With timezone set to Australia\Sydney (AEST, UCT+10), each processor shows 
> Task / Time of 0 / 00:00:00.000.
> With timezone set to Australia\Adelaide (ACST, UCT+9:30), each processor 
> shows Task / Time of 0 / 00:30:00.000.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] nifi-minifi-cpp pull request #108: MINIFI-329: Ensure boolean value is check...

[phrocker]

GitHub user phrocker opened a pull request:

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

MINIFI-329: Ensure boolean value is checked before creating a secure …

…socket

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

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

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

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

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

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

### For code changes:
- [ ] 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?
- [ ] If applicable, have you updated the NOTICE file?

### 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/phrocker/nifi-minifi-cpp MINIFI-329

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

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


commit da83bfd4d0952a541acfca86276e45784adf5cd6
Author: Marc Parisi 
Date:   2017-05-31T13:20:49Z

MINIFI-329: Ensure boolean value is checked before creating a secure socket




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3995) Update 'Schema Access Strategy' for Hwx Content Encoded Schema to use updated header info

[Mark Payne (JIRA)]

Mark Payne created NIFI-3995:


 Summary: Update 'Schema Access Strategy' for Hwx Content Encoded 
Schema to use updated header info
 Key: NIFI-3995
 URL: https://issues.apache.org/jira/browse/NIFI-3995
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Mark Payne
Assignee: Mark Payne


The Hwx Schema Registry has changed the way that it serializes & deserializes 
schema information in the header, so that the 14th byte is no longer used, 
because it was not really needed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)