date:20161122


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

Joseph Percivall updated NIFI-3086:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)
> testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.026 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:319)
> at 
>

[jira] [Commented] (NIFI-3086) TestTailFile failures

2016-11-22 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on NIFI-3086:
--

Github user asfgit closed the pull request at:

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


> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)
> testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.026 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:319)
> at

[jira] [Commented] (NIFI-3086) TestTailFile failures


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

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

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

NIFI-3086 Updated TailFile.java to deal with windows paths that were breaking 
the regex parsing Fixed documentation misspelling in TailFile.java Fixed 
assertions in several tests in TestTailFile that were dependent on the received 
order of flowfiles, this was differing between Windows and MacOS/Linux

This closes #1264

Signed-off-by: jpercivall 


> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)
>

[GitHub] nifi pull request #1264: NIFI-3086 Updated TailFile.java to deal with window...

Github user asfgit closed the pull request at:

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


---
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 issue #1264: NIFI-3086 Updated TailFile.java to deal with windows paths...

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1264
  
+1

Fixes the windows issues. Thanks @jtstorck! I will merge it in.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
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-3086) TestTailFile failures


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

ASF GitHub Bot commented on NIFI-3086:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1264
  
+1

Fixes the windows issues. Thanks @jtstorck! I will merge it in.


> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)
> testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.026 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
>

[jira] [Updated] (NIFI-3086) TestTailFile failures

2016-11-22 Thread Jeff Storck (JIRA)


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

Jeff Storck updated NIFI-3086:
--
Status: Patch Available  (was: Open)

> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)
> testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.026 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:319)
> at 
>

[GitHub] nifi-minifi-cpp pull request #24: MINIFI-114: Set default stateFile for Tail...

2016-11-22 Thread benqiu2016

GitHub user benqiu2016 opened a pull request:

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

MINIFI-114: Set default stateFile for TailFile



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

$ git pull https://github.com/benqiu2016/nifi-minifi-cpp master

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

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


commit dc96f2ad7dce8a6934516d4485ed92f38caf3de4
Author: Bin Qiu 
Date:   2016-10-28T16:48:57Z

Provenance Support

commit b0ee74792dd67b61d7e09d6abfb7d4eb05dfc2df
Author: Bin Qiu 
Date:   2016-10-28T16:53:20Z

Provenance Support

commit 351fab8f9a7b629ec16986f54e909e34e2cf0b1e
Author: Bin Qiu 
Date:   2016-11-14T17:21:31Z

MINIFI-131: Provenance Support

commit 4e6d1eec360bebd0b63422159ea1ef17b088b879
Author: Bin Qiu 
Date:   2016-11-14T17:26:21Z

MINIFI-131: Provenance Support

commit 836e4f3993aed01a647327b20212569527b66dbf
Author: Bin Qiu 
Date:   2016-11-23T04:51:12Z

MINIFI-114: Set default stateFile for TailFile




---
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-3086) TestTailFile failures


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

ASF GitHub Bot commented on NIFI-3086:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1264
  
Hey @jtstorck, couple of check style issues:

[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[581] 
(sizes) LineLength: Line is longer than 200 characters (found 224).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[584] 
(sizes) LineLength: Line is longer than 200 characters (found 224).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[587] 
(sizes) LineLength: Line is longer than 200 characters (found 214).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[689] 
(sizes) LineLength: Line is longer than 200 characters (found 228).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[692] 
(sizes) LineLength: Line is longer than 200 characters (found 214).


> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
>

[GitHub] nifi issue #1264: NIFI-3086 Updated TailFile.java to deal with windows paths...

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1264
  
Hey @jtstorck, couple of check style issues:

[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[581] 
(sizes) LineLength: Line is longer than 200 characters (found 224).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[584] 
(sizes) LineLength: Line is longer than 200 characters (found 224).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[587] 
(sizes) LineLength: Line is longer than 200 characters (found 214).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[689] 
(sizes) LineLength: Line is longer than 200 characters (found 228).
[WARNING] 
src/test/java/org/apache/nifi/processors/standard/TestTailFile.java[692] 
(sizes) LineLength: Line is longer than 200 characters (found 214).


---
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-3086) TestTailFile failures


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

ASF GitHub Bot commented on NIFI-3086:
--

GitHub user jtstorck opened a pull request:

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

NIFI-3086 Updated TailFile.java to deal with windows paths that were …

…breaking the regex parsing

Fixed documentation misspelling in TailFile.java
Fixed assertions in several tests in TestTailFile that were dependent on 
the received order of flowfiles, this was differing between Windows and 
MacOS/Linux

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

$ git pull https://github.com/jtstorck/nifi NIFI-3086

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

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


commit 86017751763300c372e95d5ec5e87f9e25338a11
Author: Jeff Storck 
Date:   2016-11-23T03:01:22Z

NIFI-3086 Updated TailFile.java to deal with windows paths that were 
breaking the regex parsing
Fixed documentation misspelling in TailFile.java
Fixed assertions in several tests in TestTailFile that were dependent on 
the received order of flowfiles, this was differing between Windows and 
MacOS/Linux




> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
>

[GitHub] nifi pull request #1264: NIFI-3086 Updated TailFile.java to deal with window...

2016-11-22 Thread jtstorck

GitHub user jtstorck opened a pull request:

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

NIFI-3086 Updated TailFile.java to deal with windows paths that were â¦

â¦breaking the regex parsing

Fixed documentation misspelling in TailFile.java
Fixed assertions in several tests in TestTailFile that were dependent on 
the received order of flowfiles, this was differing between Windows and 
MacOS/Linux

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

$ git pull https://github.com/jtstorck/nifi NIFI-3086

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

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


commit 86017751763300c372e95d5ec5e87f9e25338a11
Author: Jeff Storck 
Date:   2016-11-23T03:01:22Z

NIFI-3086 Updated TailFile.java to deal with windows paths that were 
breaking the regex parsing
Fixed documentation misspelling in TailFile.java
Fixed assertions in several tests in TestTailFile that were dependent on 
the received order of flowfiles, this was differing between Windows and 
MacOS/Linux




---
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-3088) NPE occurs on start-up if there are orphaned FlowFiles

Joseph Percivall created NIFI-3088:
--

 Summary: NPE occurs on start-up if there are orphaned FlowFiles
 Key: NIFI-3088
 URL: https://issues.apache.org/jira/browse/NIFI-3088
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Priority: Blocker
 Fix For: 1.1.0


The repo serialization was re-done in this commit: 
https://github.com/apache/nifi/commit/1be08714731f01347ac1f98e18047fe7d9ab8afd

It causes the following exception on start-up if there are orphaned FlowFiles 
(FlowFiles that are associated with a queue id that no longer exists in the 
Flow).


org.apache.nifi.web.NiFiCoreException: Unable to start Flow Controller.
at 
org.apache.nifi.web.contextlistener.ApplicationStartupContextListener.contextInitialized(ApplicationStartupContextListener.java:85)
 ~[na:na]
at 
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:837)
 ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:533)
 ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:810)
 ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:345)
 ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1404) 
~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1366) 
~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:772)
 ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:262)
 ~[jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:520) 
~[jetty-webapp-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
 ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
 ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart(GzipHandler.java:231) 
~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.Server.start(Server.java:411) 
~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:106)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
 ~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.eclipse.jetty.server.Server.doStart(Server.java:378) 
~[jetty-server-9.3.9.v20160517.jar:9.3.9.v20160517]
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
 ~[jetty-util-9.3.9.v20160517.jar:9.3.9.v20160517]
at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:675) 
~[nifi-jetty-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at org.apache.nifi.NiFi.(NiFi.java:156) 
[nifi-runtime-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at org.apache.nifi.NiFi.main(NiFi.java:262) 
[nifi-runtime-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
Caused by: java.io.IOException: Failed to write field

[jira] [Commented] (NIFI-3024) Encrypted configuration migrator should be able to update sensitive properties key and migrate flow.xml.gz


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

ASF GitHub Bot commented on NIFI-3024:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1261
  
@YolandaMDavis found test errors when running in JCE **limited** mode, 
which I always forget to check for (seriously, I had a `TODO` in the test). I 
have resolved the issue (known issue documented in 
[NIFI-1465](https://issues.apache.org/jira/browse/NIFI-1465) and 
[NIFI-1255](https://issues.apache.org/jira/browse/NIFI-1255)). 

```

hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
 1680s @ 19:00:43 $ mci
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] 

[INFO] Building nifi-toolkit-encrypt-config 1.1.0-SNAPSHOT
[INFO] 

...
---
 T E S T S
---
Running org.apache.nifi.properties.ConfigEncryptionToolTest
Tests run: 89, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 6.637 sec 
- in org.apache.nifi.properties.ConfigEncryptionToolTest

Results :

Tests run: 89, Failures: 0, Errors: 0, Skipped: 6

[INFO]
...
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 15.805 s
[INFO] Finished at: 2016-11-22T19:01:01-08:00
[INFO] Final Memory: 33M/1062M
[INFO] 


hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
 18s @ 19:01:02 $ jce_unlimited
Enabling JCE unlimited strength crypto policy
/Users/alopresto/Desktop/security/unlimited/US_export_policy.jar -> 
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/security/./US_export_policy.jar
/Users/alopresto/Desktop/security/unlimited/local_policy.jar -> 
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/security/./local_policy.jar

hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
 19s @ 19:01:22 $ mci
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] 

[INFO] Building nifi-toolkit-encrypt-config 1.1.0-SNAPSHOT
[INFO] 

[INFO]
...
---
 T E S T S
---
Running org.apache.nifi.properties.ConfigEncryptionToolTest
Tests run: 89, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 6.668 sec 
- in org.apache.nifi.properties.ConfigEncryptionToolTest

Results :

Tests run: 89, Failures: 0, Errors: 0, Skipped: 6

[INFO]
...
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 15.041 s
[INFO] Finished at: 2016-11-22T19:01:43-08:00
[INFO] Final Memory: 33M/1068M
[INFO] 


hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
 21s @ 19:01:44 $
```


> Encrypted configuration migrator should be able to update sensitive 
> properties key and migrate flow.xml.gz
> --
>
> Key: NIFI-3024
> URL: https://issues.apache.org/jira/browse/NIFI-3024
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>Assignee: Andy LoPresto
>  Labels: config, encryption, security, serialization

[GitHub] nifi issue #1261: NIFI-3024 Added key migration for sensitive processor prop...

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1261
  
@YolandaMDavis found test errors when running in JCE **limited** mode, 
which I always forget to check for (seriously, I had a `TODO` in the test). I 
have resolved the issue (known issue documented in 
[NIFI-1465](https://issues.apache.org/jira/browse/NIFI-1465) and 
[NIFI-1255](https://issues.apache.org/jira/browse/NIFI-1255)). 

```

hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
ð 1680s @ 19:00:43 $ mci
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] 

[INFO] Building nifi-toolkit-encrypt-config 1.1.0-SNAPSHOT
[INFO] 

...
---
 T E S T S
---
Running org.apache.nifi.properties.ConfigEncryptionToolTest
Tests run: 89, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 6.637 sec 
- in org.apache.nifi.properties.ConfigEncryptionToolTest

Results :

Tests run: 89, Failures: 0, Errors: 0, Skipped: 6

[INFO]
...
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 15.805 s
[INFO] Finished at: 2016-11-22T19:01:01-08:00
[INFO] Final Memory: 33M/1062M
[INFO] 


hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
ð 18s @ 19:01:02 $ jce_unlimited
Enabling JCE unlimited strength crypto policy
/Users/alopresto/Desktop/security/unlimited/US_export_policy.jar -> 
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/security/./US_export_policy.jar
/Users/alopresto/Desktop/security/unlimited/local_policy.jar -> 
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/security/./local_policy.jar

hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
ð 19s @ 19:01:22 $ mci
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with 
nexus-staging-maven-plugin
[INFO]
[INFO] 

[INFO] Building nifi-toolkit-encrypt-config 1.1.0-SNAPSHOT
[INFO] 

[INFO]
...
---
 T E S T S
---
Running org.apache.nifi.properties.ConfigEncryptionToolTest
Tests run: 89, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 6.668 sec 
- in org.apache.nifi.properties.ConfigEncryptionToolTest

Results :

Tests run: 89, Failures: 0, Errors: 0, Skipped: 6

[INFO]
...
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 15.041 s
[INFO] Finished at: 2016-11-22T19:01:43-08:00
[INFO] Final Memory: 33M/1068M
[INFO] 


hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-encrypt-config
 (NIFI-3024-rebased-squashed) alopresto
ð 21s @ 19:01:44 $
```


---
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-2958) Missing Error Message in PutElasticsearchHttp


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

Matt Burgess commented on NIFI-2958:


Fair enough. NIFI-3082 changed from just throwing ProcessExceptions (and thus 
re-queueing the flow files) to handling them like the other ES processors (5xx 
to retry, the rest to failure). Hopefully that resolves that part of your 
issue? If not, please feel free to comment on that Jira as well, thanks! 

> Missing Error Message in PutElasticsearchHttp
> -
>
> Key: NIFI-2958
> URL: https://issues.apache.org/jira/browse/NIFI-2958
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Justin M Cavinee
>Priority: Minor
>
> Error messages are not being shown properly when the push to Elastic Search 
> fails.  
> When I get a failure, it just reads:
> Failed to Insert StandardFlowFileRecord[..] into Elastic Search due to , 
> transferring to failure.
> With nothing following the due to.  If I use curl to directly push to content 
> to ElasticSearch then I do get a proper error message, which should be put 
> into the Elastic Search log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-2958) Missing Error Message in PutElasticsearchHttp

2016-11-22 Thread Justin M Cavinee (JIRA)


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

Justin M Cavinee commented on NIFI-2958:


Definitely seems related, although I think I was getting 400 errors, not
5xx.  I'll run some tests tomorrow and copy the responses here.




> Missing Error Message in PutElasticsearchHttp
> -
>
> Key: NIFI-2958
> URL: https://issues.apache.org/jira/browse/NIFI-2958
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Justin M Cavinee
>Priority: Minor
>
> Error messages are not being shown properly when the push to Elastic Search 
> fails.  
> When I get a failure, it just reads:
> Failed to Insert StandardFlowFileRecord[..] into Elastic Search due to , 
> transferring to failure.
> With nothing following the due to.  If I use curl to directly push to content 
> to ElasticSearch then I do get a proper error message, which should be put 
> into the Elastic Search log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3087) PutElasticsearch(Http) processors not correctly handling partial failure

2016-11-22 Thread Joseph Witt (JIRA)


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

Joseph Witt updated NIFI-3087:
--
Fix Version/s: 1.1.0

> PutElasticsearch(Http) processors not correctly handling partial failure
> 
>
> Key: NIFI-3087
> URL: https://issues.apache.org/jira/browse/NIFI-3087
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> If a Bulk Insert is performed by PutElasticsearch and/or 
> PutElasticsearchHttp, and some records fail while others succeed, the 
> processor fails with an IndexOutOfBoundsException.
> This appears to be a negative logic/iteration bug in the code for handling 
> failures in the response with respect to the incoming flow files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3087) PutElasticsearch(Http) processors not correctly handling partial failure


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

ASF GitHub Bot commented on NIFI-3087:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-3087: Fixed issue with partial failure responses in 
PutElasticsearch(Http)



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

$ git pull https://github.com/mattyb149/nifi NIFI-3087

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

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


commit d87219e73e61bb6b6f06c2273e58f5976672aa43
Author: Matt Burgess 
Date:   2016-11-23T01:07:31Z

NIFI-3087: Added unit tests to PutElasticsearch(Http) to illustrate issue

commit 3f4e389cb82d69d39bb6bfd2d4c9ebb4584aacd1
Author: Matt Burgess 
Date:   2016-11-23T01:08:17Z

NIFI-3087: Fixed issue with partial failure responses in 
PutElasticsearch(Http)




> PutElasticsearch(Http) processors not correctly handling partial failure
> 
>
> Key: NIFI-3087
> URL: https://issues.apache.org/jira/browse/NIFI-3087
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> If a Bulk Insert is performed by PutElasticsearch and/or 
> PutElasticsearchHttp, and some records fail while others succeed, the 
> processor fails with an IndexOutOfBoundsException.
> This appears to be a negative logic/iteration bug in the code for handling 
> failures in the response with respect to the incoming flow files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1263: NIFI-3087: Fixed issue with partial failure respons...

2016-11-22 Thread mattyb149

GitHub user mattyb149 opened a pull request:

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

NIFI-3087: Fixed issue with partial failure responses in 
PutElasticsearch(Http)



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

$ git pull https://github.com/mattyb149/nifi NIFI-3087

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

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


commit d87219e73e61bb6b6f06c2273e58f5976672aa43
Author: Matt Burgess 
Date:   2016-11-23T01:07:31Z

NIFI-3087: Added unit tests to PutElasticsearch(Http) to illustrate issue

commit 3f4e389cb82d69d39bb6bfd2d4c9ebb4584aacd1
Author: Matt Burgess 
Date:   2016-11-23T01:08:17Z

NIFI-3087: Fixed issue with partial failure responses in 
PutElasticsearch(Http)




---
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-3087) PutElasticsearch(Http) processors not correctly handling partial failure


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

Matt Burgess updated NIFI-3087:
---
Status: Patch Available  (was: In Progress)

> PutElasticsearch(Http) processors not correctly handling partial failure
> 
>
> Key: NIFI-3087
> URL: https://issues.apache.org/jira/browse/NIFI-3087
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> If a Bulk Insert is performed by PutElasticsearch and/or 
> PutElasticsearchHttp, and some records fail while others succeed, the 
> processor fails with an IndexOutOfBoundsException.
> This appears to be a negative logic/iteration bug in the code for handling 
> failures in the response with respect to the incoming flow files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3087) PutElasticsearch(Http) processors not correctly handling partial failure

Matt Burgess created NIFI-3087:
--

 Summary: PutElasticsearch(Http) processors not correctly handling 
partial failure
 Key: NIFI-3087
 URL: https://issues.apache.org/jira/browse/NIFI-3087
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Reporter: Matt Burgess
Assignee: Matt Burgess


If a Bulk Insert is performed by PutElasticsearch and/or PutElasticsearchHttp, 
and some records fail while others succeed, the processor fails with an 
IndexOutOfBoundsException.

This appears to be a negative logic/iteration bug in the code for handling 
failures in the response with respect to the incoming flow files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (NIFI-3086) TestTailFile failures

2016-11-22 Thread Jeff Storck (JIRA)


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

Jeff Storck reassigned NIFI-3086:
-

Assignee: Jeff Storck

> TestTailFile failures
> -
>
> Key: NIFI-3086
> URL: https://issues.apache.org/jira/browse/NIFI-3086
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Jeff Storck
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Changes to TailFile since 1.0.0:
> https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
> https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4
> Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec 
> <<< FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
> testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.014 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
> near index 7
> target\log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.escape(Pattern.java:2471)
> at java.util.regex.Pattern.atom(Pattern.java:2198)
> at java.util.regex.Pattern.sequence(Pattern.java:2130)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)
> testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.157 sec  <<< ERROR!
> java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
> target\(testDir/)?log(ging)?.txt
>    ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.compile(Pattern.java:1700)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at 
> org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
> at 
> org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
> at 
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
> at 
> org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
> at 
> org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
> at 
> org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)
> testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
>   Time elapsed: 0.026 sec  <<< FAILURE!
> java.lang.AssertionError: expected:<2> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:645)
> at org.junit.Assert.assertEquals(Assert.java:631)
> at 
> org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:319)
> at 
>

[jira] [Commented] (NIFI-3024) Encrypted configuration migrator should be able to update sensitive properties key and migrate flow.xml.gz


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

ASF GitHub Bot commented on NIFI-3024:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/1261
  
@alopresto reviewing


> Encrypted configuration migrator should be able to update sensitive 
> properties key and migrate flow.xml.gz
> --
>
> Key: NIFI-3024
> URL: https://issues.apache.org/jira/browse/NIFI-3024
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>Assignee: Andy LoPresto
>  Labels: config, encryption, security, serialization
> Fix For: 1.1.0
>
>
> In order to allow changing of nifi.sensitive.props.key and updating of the 
> flow.xml.gz, the ConfigEncryptionTool should be able to accept a new value 
> for that field and update encrypted values in the flow.xml.gz appropriately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1261: NIFI-3024 Added key migration for sensitive processor prop...

2016-11-22 Thread YolandaMDavis

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/1261
  
@alopresto reviewing


---
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-2958) Missing Error Message in PutElasticsearchHttp


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

Matt Burgess commented on NIFI-2958:


Your comment (not this issue's description) seems related to NIFI-3082, do you 
agree?

For the error messages, can you share where the proper error message occurs in 
the response? Currently the code uses "//error/reason" to find the message, 
perhaps that is the root cause of this issue?

> Missing Error Message in PutElasticsearchHttp
> -
>
> Key: NIFI-2958
> URL: https://issues.apache.org/jira/browse/NIFI-2958
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Justin M Cavinee
>Priority: Minor
>
> Error messages are not being shown properly when the push to Elastic Search 
> fails.  
> When I get a failure, it just reads:
> Failed to Insert StandardFlowFileRecord[..] into Elastic Search due to , 
> transferring to failure.
> With nothing following the due to.  If I use curl to directly push to content 
> to ElasticSearch then I do get a proper error message, which should be put 
> into the Elastic Search log.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3086) TestTailFile failures


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

Joseph Percivall updated NIFI-3086:
---
Description: 
Changes to TailFile since 1.0.0:
https://github.com/apache/nifi/commit/930e95aa0023b12e5618068ea144808e5627cea7
https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4

Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec <<< 
FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
  Time elapsed: 0.014 sec  <<< ERROR!
java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
near index 7
target\log(ging)?.txt
   ^
at java.util.regex.Pattern.error(Pattern.java:1955)
at java.util.regex.Pattern.escape(Pattern.java:2471)
at java.util.regex.Pattern.atom(Pattern.java:2198)
at java.util.regex.Pattern.sequence(Pattern.java:2130)
at java.util.regex.Pattern.expr(Pattern.java:1996)
at java.util.regex.Pattern.compile(Pattern.java:1696)
at java.util.regex.Pattern.(Pattern.java:1351)
at java.util.regex.Pattern.compile(Pattern.java:1028)
at 
org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
at 
org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
at 
org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
at 
org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
at 
org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
at 
org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)

testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
  Time elapsed: 0.157 sec  <<< ERROR!
java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
target\(testDir/)?log(ging)?.txt
   ^
at java.util.regex.Pattern.error(Pattern.java:1955)
at java.util.regex.Pattern.compile(Pattern.java:1700)
at java.util.regex.Pattern.(Pattern.java:1351)
at java.util.regex.Pattern.compile(Pattern.java:1028)
at 
org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
at 
org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
at 
org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
at 
org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
at 
org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
at 
org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)

testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
  Time elapsed: 0.026 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at 
org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:319)
at 
org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:314)
at 
org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesChangingNameStrategy(TestTailFile.java:738)

testMultipleFiles(org.apache.nifi.processors.standard.TestTailFile)  Time 
elapsed: 0.139 sec  <<< ERROR!
java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
target\(testDir/)?log(ging)?.txt
   ^
at java.util.regex.Pattern.error(Pattern.java:1955)
at java.util.regex.Pattern.compile(Pattern.java:1700)
at java.util.regex.Pattern.(Pattern.java:1351)

[jira] [Updated] (NIFI-2655) Encrypted config tool should handle absence of "-n" flag

2016-11-22 Thread Andy LoPresto (JIRA)


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

Andy LoPresto updated NIFI-2655:

Fix Version/s: (was: 1.2.0)
   1.1.0
   Status: Patch Available  (was: In Progress)

> Encrypted config tool should handle absence of "-n" flag
> 
>
> Key: NIFI-2655
> URL: https://issues.apache.org/jira/browse/NIFI-2655
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
>  Labels: config, security
> Fix For: 1.1.0
>
>
> The {{encrypt-config}} tool will fail if the source {{-n nifi.properties}} 
> flag is not present. However, it first looks for {{./conf/nifi.properties}} 
> before failing. Either {{-n}} should be a required flag or a default 
> {{nifi.properties}} template file should be populated within the tool. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3024) Encrypted configuration migrator should be able to update sensitive properties key and migrate flow.xml.gz


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

ASF GitHub Bot commented on NIFI-3024:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1221
  
I have created [PR 1261](https://github.com/apache/nifi/pull/1261) to 
implement this. Recommend this PR be closed. 


> Encrypted configuration migrator should be able to update sensitive 
> properties key and migrate flow.xml.gz
> --
>
> Key: NIFI-3024
> URL: https://issues.apache.org/jira/browse/NIFI-3024
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>Assignee: Andy LoPresto
>  Labels: config, encryption, security, serialization
> Fix For: 1.1.0
>
>
> In order to allow changing of nifi.sensitive.props.key and updating of the 
> flow.xml.gz, the ConfigEncryptionTool should be able to accept a new value 
> for that field and update encrypted values in the flow.xml.gz appropriately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3024) Encrypted configuration migrator should be able to update sensitive properties key and migrate flow.xml.gz

2016-11-22 Thread Andy LoPresto (JIRA)


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

Andy LoPresto updated NIFI-3024:

Status: Patch Available  (was: In Progress)

> Encrypted configuration migrator should be able to update sensitive 
> properties key and migrate flow.xml.gz
> --
>
> Key: NIFI-3024
> URL: https://issues.apache.org/jira/browse/NIFI-3024
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>Assignee: Andy LoPresto
>  Labels: config, encryption, security, serialization
> Fix For: 1.1.0
>
>
> In order to allow changing of nifi.sensitive.props.key and updating of the 
> flow.xml.gz, the ConfigEncryptionTool should be able to accept a new value 
> for that field and update encrypted values in the flow.xml.gz appropriately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1221: NIFI-3024 - Encrypt-toolkit flow.xml.gz support

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1221
  
I have created [PR 1261](https://github.com/apache/nifi/pull/1261) to 
implement this. Recommend this PR be closed. 


---
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-2655) Encrypted config tool should handle absence of "-n" flag


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

ASF GitHub Bot commented on NIFI-2655:
--

GitHub user alopresto opened a pull request:

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

[WIP] NIFI-2655

This PR is already rebased against [PR 
1261](https://github.com/apache/nifi/pull/1261) so it should not be merged to 
`master` until after that PR is merged. Once that occurs, this PR will drop to 
a much [smaller 
changeset](https://github.com/apache/nifi/commit/0633cbac5d27b41ce232e11ea96592e19218445e).
 


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-2655

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

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


commit 1b2d79010ef50d54ec01fad4318c2889acee0b42
Author: Andy LoPresto 
Date:   2016-11-22T05:19:18Z

NIFI-3024 Added key migration for sensitive processor properties contained 
in flow.xml.gz. (nifi.sensitive.props.key)

commit 0633cbac5d27b41ce232e11ea96592e19218445e
Author: Andy LoPresto 
Date:   2016-11-22T22:49:33Z

NIFI-2655 Implemented logic check for missing -n or -l arguments.
Added and updated unit tests.
Cleaned up unnecessary and commented code.
Removed ignored unit tests.




> Encrypted config tool should handle absence of "-n" flag
> 
>
> Key: NIFI-2655
> URL: https://issues.apache.org/jira/browse/NIFI-2655
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Minor
>  Labels: config, security
> Fix For: 1.2.0
>
>
> The {{encrypt-config}} tool will fail if the source {{-n nifi.properties}} 
> flag is not present. However, it first looks for {{./conf/nifi.properties}} 
> before failing. Either {{-n}} should be a required flag or a default 
> {{nifi.properties}} template file should be populated within the tool. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1262: [WIP] NIFI-2655

2016-11-22 Thread ASF subversion and git services (JIRA)

GitHub user alopresto opened a pull request:

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

[WIP] NIFI-2655

This PR is already rebased against [PR 
1261](https://github.com/apache/nifi/pull/1261) so it should not be merged to 
`master` until after that PR is merged. Once that occurs, this PR will drop to 
a much [smaller 
changeset](https://github.com/apache/nifi/commit/0633cbac5d27b41ce232e11ea96592e19218445e).
 


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-2655

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

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


commit 1b2d79010ef50d54ec01fad4318c2889acee0b42
Author: Andy LoPresto 
Date:   2016-11-22T05:19:18Z

NIFI-3024 Added key migration for sensitive processor properties contained 
in flow.xml.gz. (nifi.sensitive.props.key)

commit 0633cbac5d27b41ce232e11ea96592e19218445e
Author: Andy LoPresto 
Date:   2016-11-22T22:49:33Z

NIFI-2655 Implemented logic check for missing -n or -l arguments.
Added and updated unit tests.
Cleaned up unnecessary and commented code.
Removed ignored unit tests.




---
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-3084) Provenance Repo Build Failures on Windows


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

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

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

NIFI-3084 Fixing TestPersistentProvenanceRepository and closing a stream leak 
in RecordReaders.

This closes #1260.


> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
>

[jira] [Updated] (NIFI-3084) Provenance Repo Build Failures on Windows

2016-11-22 Thread Mark Payne (JIRA)


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

Mark Payne updated NIFI-3084:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 8.39 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\c8c56a43-c930-4f64-a496-66edcce8e39d\0.prov.gz
> at

[jira] [Commented] (NIFI-3084) Provenance Repo Build Failures on Windows


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

ASF GitHub Bot commented on NIFI-3084:
--

Github user asfgit closed the pull request at:

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


> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 8.39 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
>

[GitHub] nifi issue #1260: NIFI-3084 Fixing TestPersistentProvenanceRepository and cl...

2016-11-22 Thread markap14

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1260
  
@JPercivall thanks for catching the issue and addressing it. Changes look 
fine. Tests all pass now. +1 merged to master.


---
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 pull request #1260: NIFI-3084 Fixing TestPersistentProvenanceRepository...

Github user asfgit closed the pull request at:

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


---
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-3024) Encrypted configuration migrator should be able to update sensitive properties key and migrate flow.xml.gz


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

ASF GitHub Bot commented on NIFI-3024:
--

GitHub user alopresto opened a pull request:

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

NIFI-3024 Added key migration for sensitive processor properties cont…

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:
- [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.

…ained in flow.xml.gz. (nifi.sensitive.props.key)

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

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

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

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


commit 1b2d79010ef50d54ec01fad4318c2889acee0b42
Author: Andy LoPresto 
Date:   2016-11-22T05:19:18Z

NIFI-3024 Added key migration for sensitive processor properties contained 
in flow.xml.gz. (nifi.sensitive.props.key)




> Encrypted configuration migrator should be able to update sensitive 
> properties key and migrate flow.xml.gz
> --
>
> Key: NIFI-3024
> URL: https://issues.apache.org/jira/browse/NIFI-3024
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Configuration, Tools and Build
>Affects Versions: 1.0.0
>Reporter: Bryan Rosander
>Assignee: Andy LoPresto
>  Labels: config, encryption, security, serialization
> Fix For: 1.1.0
>
>
> In order to allow changing of nifi.sensitive.props.key and updating of the 
> flow.xml.gz, the ConfigEncryptionTool should be able to accept a new value 
> for that field and update encrypted values in the flow.xml.gz appropriately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1261: NIFI-3024 Added key migration for sensitive process...

GitHub user alopresto opened a pull request:

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

NIFI-3024 Added key migration for sensitive processor properties contâ¦

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:
- [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.

â¦ained in flow.xml.gz. (nifi.sensitive.props.key)

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

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

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

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


commit 1b2d79010ef50d54ec01fad4318c2889acee0b42
Author: Andy LoPresto 
Date:   2016-11-22T05:19:18Z

NIFI-3024 Added key migration for sensitive processor properties contained 
in flow.xml.gz. (nifi.sensitive.props.key)




---
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-3084) Provenance Repo Build Failures on Windows


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

ASF GitHub Bot commented on NIFI-3084:
--

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1260
  
Reviewing...


> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 8.39 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
>

[GitHub] nifi issue #1260: NIFI-3084 Fixing TestPersistentProvenanceRepository and cl...

2016-11-22 Thread markap14

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/1260
  
Reviewing...


---
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-3084) Provenance Repo Build Failures on Windows


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

ASF GitHub Bot commented on NIFI-3084:
--

GitHub user JPercivall opened a pull request:

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

NIFI-3084 Fixing TestPersistentProvenanceRepository and closing a str…

…eam leak in RecordReaders

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

$ git pull https://github.com/JPercivall/nifi NIFI-3083

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

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


commit 60a7c33eb8279589534621d1497523ed900b4535
Author: Joseph Percivall 
Date:   2016-11-22T22:11:13Z

NIFI-3084 Fixing TestPersistentProvenanceRepository and closing a stream 
leak in RecordReaders




> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
>

[GitHub] nifi pull request #1260: NIFI-3084 Fixing TestPersistentProvenanceRepository...

GitHub user JPercivall opened a pull request:

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

NIFI-3084 Fixing TestPersistentProvenanceRepository and closing a strâ¦

â¦eam leak in RecordReaders

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

$ git pull https://github.com/JPercivall/nifi NIFI-3083

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

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


commit 60a7c33eb8279589534621d1497523ed900b4535
Author: Joseph Percivall 
Date:   2016-11-22T22:11:13Z

NIFI-3084 Fixing TestPersistentProvenanceRepository and closing a stream 
leak in RecordReaders




---
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] [Resolved] (NIFI-3085) TestGetFile failures


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

Joseph Percivall resolved NIFI-3085.

Resolution: Fixed
  Assignee: Oleg Zhurakousky

Closed via: 
https://github.com/apache/nifi/commit/913ae91614b25dfd3fd668c475acd712d00de5a2

> TestGetFile failures
> 
>
> Key: NIFI-3085
> URL: https://issues.apache.org/jira/browse/NIFI-3085
> Project: Apache NiFi
>  Issue Type: Sub-task
> Environment: Windows 8
>Reporter: Joseph Percivall
>Assignee: Oleg Zhurakousky
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails on TestGetFile due to 
> https://github.com/apache/nifi/commit/611cadd231309126a0a7737391f6e07730bb3864
> Tests run: 7, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.075 sec <<< 
> FAILURE! - in org.apache.nifi.processors.standard.TestGetFile
> testWithUnreadableDir(org.apache.nifi.processors.standard.TestGetFile)  Time 
> elapsed: 0.004 sec  <<< ERROR!
> java.lang.UnsupportedOperationException: null
> at java.nio.file.Files.setPosixFilePermissions(Files.java:2044)
> at 
> org.apache.nifi.processors.standard.TestGetFile.testWithUnreadableDir(TestGetFile.java:75)
> testWithInaccessibleDir(org.apache.nifi.processors.standard.TestGetFile)  
> Time elapsed: 0 sec  <<< ERROR!
> java.lang.UnsupportedOperationException: null
> at java.nio.file.Files.setPosixFilePermissions(Files.java:2044)
> at 
> org.apache.nifi.processors.standard.TestGetFile.testWithInaccessibleDir(TestGetFile.java:51)
> testWithUnwritableDir(org.apache.nifi.processors.standard.TestGetFile)  Time 
> elapsed: 0.001 sec  <<< ERROR!
> java.lang.UnsupportedOperationException: null
> at java.nio.file.Files.setPosixFilePermissions(Files.java:2044)
> at 
> org.apache.nifi.processors.standard.TestGetFile.testWithUnwritableDir(TestGetFile.java:99)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1259: Added posix guard to ignore tests on windows

Github user asfgit closed the pull request at:

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


---
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] [Assigned] (NIFI-3084) Provenance Repo Build Failures on Windows

2016-11-22 Thread ASF subversion and git services (JIRA)


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

Joseph Percivall reassigned NIFI-3084:
--

Assignee: Joseph Percivall

> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Assignee: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 8.39 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\c8c56a43-c930-4f64-a496-66edcce8e39d\0.prov.gz
> at

[jira] [Resolved] (NIFI-3041) Remove references to Windows start-nifi.bat tool in Admin Guide

2016-11-22 Thread Pierre Villard (JIRA)


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

Pierre Villard resolved NIFI-3041.
--
   Resolution: Fixed
Fix Version/s: 0.8.0
   1.1.0

Merged PR#1257 to master and 0.x.
Merged PR#8 on nifi-site and deployed change.

> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
> Fix For: 1.1.0, 0.8.0
>
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3041) Remove references to Windows start-nifi.bat tool in Admin Guide


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

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

Commit c87c93d7676aacf378c76b3e2b1caa1344b009d3 in nifi's branch refs/heads/0.x 
from [~andrewmlim]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=c87c93d ]

NIFI-3041 Removed references to Windows start-nifi.bat and stop-nifi.bat in 
Admin Guide

This closes #1257.


> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1259: Added posix guard to ignore tests on windows

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/1259
  
+1

These tests are being ignored instead of "fixed" because Windows does not 
support POSIX[1] and these tests rely on them in order to test some specific 
scenarios. Thanks @olegz I will merge it in (I am also going to add a couple 
comments to the code as well).

[1] 
http://stackoverflow.com/questions/14415960/java-lang-unsupportedoperationexception-posixpermissions-not-supported-as-in


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
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-3068) NiFi can not reliably support multiple HDFS clusters in the same flow


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

Bryan Bende updated NIFI-3068:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> NiFi can not reliably support multiple HDFS clusters in the same flow
> -
>
> Key: NIFI-3068
> URL: https://issues.apache.org/jira/browse/NIFI-3068
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Sam Hjelmfelt
>Assignee: Bryan Bende
>  Labels: HDFS
> Fix For: 1.1.0
>
> Attachments: NIFI-3068.patch
>
>
> The HDFS configurations in PutHDFS are not respected when two (or more) 
> PutHDFS processors exist with different configurations. The second processor 
> to run will use the configurations from the first processor. This can cause 
> data to be written to the wrong cluster.
> This appears to be caused by configuration caching in 
> AbstractHadoopProcessor, which would affect all HDFS processors.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L144



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3068) NiFi can not reliably support multiple HDFS clusters in the same flow

2016-11-22 Thread Oleg Zhurakousky (JIRA)


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

Oleg Zhurakousky commented on NIFI-3068:


[~bende] +1

> NiFi can not reliably support multiple HDFS clusters in the same flow
> -
>
> Key: NIFI-3068
> URL: https://issues.apache.org/jira/browse/NIFI-3068
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Sam Hjelmfelt
>Assignee: Bryan Bende
>  Labels: HDFS
> Fix For: 1.1.0
>
> Attachments: NIFI-3068.patch
>
>
> The HDFS configurations in PutHDFS are not respected when two (or more) 
> PutHDFS processors exist with different configurations. The second processor 
> to run will use the configurations from the first processor. This can cause 
> data to be written to the wrong cluster.
> This appears to be caused by configuration caching in 
> AbstractHadoopProcessor, which would affect all HDFS processors.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L144



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3068) NiFi can not reliably support multiple HDFS clusters in the same flow

2016-11-22 Thread Oleg Zhurakousky (JIRA)


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

Oleg Zhurakousky commented on NIFI-3068:


[~bende] +1

> NiFi can not reliably support multiple HDFS clusters in the same flow
> -
>
> Key: NIFI-3068
> URL: https://issues.apache.org/jira/browse/NIFI-3068
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Sam Hjelmfelt
>Assignee: Bryan Bende
>  Labels: HDFS
> Fix For: 1.1.0
>
> Attachments: NIFI-3068.patch
>
>
> The HDFS configurations in PutHDFS are not respected when two (or more) 
> PutHDFS processors exist with different configurations. The second processor 
> to run will use the configurations from the first processor. This can cause 
> data to be written to the wrong cluster.
> This appears to be caused by configuration caching in 
> AbstractHadoopProcessor, which would affect all HDFS processors.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L144



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3068) NiFi can not reliably support multiple HDFS clusters in the same flow


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

Bryan Bende updated NIFI-3068:
--
Fix Version/s: 1.1.0

> NiFi can not reliably support multiple HDFS clusters in the same flow
> -
>
> Key: NIFI-3068
> URL: https://issues.apache.org/jira/browse/NIFI-3068
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Sam Hjelmfelt
>Assignee: Bryan Bende
>  Labels: HDFS
> Fix For: 1.1.0
>
> Attachments: NIFI-3068.patch
>
>
> The HDFS configurations in PutHDFS are not respected when two (or more) 
> PutHDFS processors exist with different configurations. The second processor 
> to run will use the configurations from the first processor. This can cause 
> data to be written to the wrong cluster.
> This appears to be caused by configuration caching in 
> AbstractHadoopProcessor, which would affect all HDFS processors.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L144



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1259: Added posix guard to ignore tests on windows

2016-11-22 Thread olegz

GitHub user olegz opened a pull request:

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

Added posix guard to ignore tests on windows

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/olegz/nifi GetFile

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

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


commit 6296242acdd38bedcf7298664743e28a6c90c78b
Author: Oleg Zhurakousky 
Date:   2016-11-22T21:31:52Z

Added posix guard to ignore tests on windows




---
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-site pull request #8: NIFI-3041 Removed references to Windows start-nif...

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-site/pull/8


---
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-3041) Remove references to Windows start-nifi.bat tool in Admin Guide


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

ASF GitHub Bot commented on NIFI-3041:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-site/pull/8


> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3041) Remove references to Windows start-nifi.bat tool in Admin Guide


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

ASF GitHub Bot commented on NIFI-3041:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1257
  
+1. Merging to master


> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3041) Remove references to Windows start-nifi.bat tool in Admin Guide


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

ASF GitHub Bot commented on NIFI-3041:
--

Github user asfgit closed the pull request at:

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


> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1257: NIFI-3041 Removed references to Windows start-nifi....

2016-11-22 Thread ASF subversion and git services (JIRA)

Github user asfgit closed the pull request at:

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


---
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-3041) Remove references to Windows start-nifi.bat tool in Admin Guide


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

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

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

NIFI-3041 Removed references to Windows start-nifi.bat and stop-nifi.bat in 
Admin Guide

This closes #1257.


> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1257: NIFI-3041 Removed references to Windows start-nifi.bat and...

2016-11-22 Thread pvillard31

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1257
  
+1. Merging to master


---
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-3084) Provenance Repo Build Failures on Windows


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

Joseph Percivall updated NIFI-3084:
---
Summary: Provenance Repo Build Failures on Windows  (was: Provenance Repo 
Failures)

> Provenance Repo Build Failures on Windows
> -
>
> Key: NIFI-3084
> URL: https://issues.apache.org/jira/browse/NIFI-3084
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: Joseph Percivall
>Priority: Blocker
> Fix For: 1.1.0
>
>
> Build fails with the following errors on the current master when built on 
> Windows 8. When running the units tests from Intellij I see a subset of the 
> below errors. Typically it is:  
> "testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
> and "testIndexOnRolloverAndSubsequentSearch"
> ---
>  T E S T S
> ---
> Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - 
> in org.apache.nifi.provenance.lucene.TestCachingIndexManager
> Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - 
> in org.apache.nifi.provenance.lucene.TestSimpleIndexManager
> Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
> Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
> <<< FAILURE! - in 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository
> testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.047 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 10.031 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.11 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 5.141 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
> at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
> at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
> at 
> org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)
> testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
>   Time elapsed: 8.39 sec  <<< ERROR!
> java.io.IOException: Unable to delete 
> C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\c8c56a43-c930-4f64-a496-66edcce8e39d\0.prov.gz
> at

[jira] [Updated] (NIFI-3083) Build fails on Windows 8


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

Joseph Percivall updated NIFI-3083:
---
Description: Build fails for multiple different reasons on Windows 8  (was: 
Build fails with the following errors on the current master when built on 
Windows 8. When running the units tests from Intellij I see a subset of the 
below errors. Typically it is:  
"testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
and "testIndexOnRolloverAndSubsequentSearch"

---
 T E S T S
---
Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - in 
org.apache.nifi.provenance.lucene.TestCachingIndexManager
Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - in 
org.apache.nifi.provenance.lucene.TestSimpleIndexManager
Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
<<< FAILURE! - in org.apache.nifi.provenance.TestPersistentProvenanceRepository
testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.047 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 10.031 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.11 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.141 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 8.39 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\c8c56a43-c930-4f64-a496-66edcce8e39d\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testBackPressure(org.apache.nifi.provenance.TestPersistentProvenanceRepository) 
 Time elapsed: 4.391 sec  <<< ERROR!
java.io.IOException: Unable to

[jira] [Updated] (NIFI-3078) Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)

2016-11-22 Thread Pierre Villard (JIRA)


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

Pierre Villard updated NIFI-3078:
-
   Resolution: Fixed
Fix Version/s: 1.1.0
   Status: Resolved  (was: Patch Available)

> Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)
> 
>
> Key: NIFI-3078
> URL: https://issues.apache.org/jira/browse/NIFI-3078
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.1.0
>
>
> As a partial improvement of providing more examples for 
> InvokeScriptedProcessor as described in NIFI-1954 , I'd like to contribute 
> TestInvokeJavascript unit test class that I wrote to understand how to use 
> the processor with Javascript.
> Currently there are test classes available for Groovy and Jython.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3086) TestTailFile failures

Joseph Percivall created NIFI-3086:
--

 Summary: TestTailFile failures
 Key: NIFI-3086
 URL: https://issues.apache.org/jira/browse/NIFI-3086
 Project: Apache NiFi
  Issue Type: Sub-task
 Environment: Windows 8
Reporter: Joseph Percivall
Priority: Blocker
 Fix For: 1.1.0


TestTailFile fails due to 
https://github.com/apache/nifi/commit/cc2fbcaac457ebbfeaada4a0fba84db784bfc9a4

Tests run: 18, Failures: 1, Errors: 3, Skipped: 0, Time elapsed: 10.394 sec <<< 
FAILURE! - in org.apache.nifi.processors.standard.TestTailFile
testMultipleFilesInSameDirectory(org.apache.nifi.processors.standard.TestTailFile)
  Time elapsed: 0.014 sec  <<< ERROR!
java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence 
near index 7
target\log(ging)?.txt
   ^
at java.util.regex.Pattern.error(Pattern.java:1955)
at java.util.regex.Pattern.escape(Pattern.java:2471)
at java.util.regex.Pattern.atom(Pattern.java:2198)
at java.util.regex.Pattern.sequence(Pattern.java:2130)
at java.util.regex.Pattern.expr(Pattern.java:1996)
at java.util.regex.Pattern.compile(Pattern.java:1696)
at java.util.regex.Pattern.(Pattern.java:1351)
at java.util.regex.Pattern.compile(Pattern.java:1028)
at 
org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
at 
org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
at 
org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
at 
org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
at 
org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
at 
org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesInSameDirectory(TestTailFile.java:656)

testMultipleFilesWithBasedirAndFilenameEL(org.apache.nifi.processors.standard.TestTailFile)
  Time elapsed: 0.157 sec  <<< ERROR!
java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
target\(testDir/)?log(ging)?.txt
   ^
at java.util.regex.Pattern.error(Pattern.java:1955)
at java.util.regex.Pattern.compile(Pattern.java:1700)
at java.util.regex.Pattern.(Pattern.java:1351)
at java.util.regex.Pattern.compile(Pattern.java:1028)
at 
org.apache.nifi.processors.standard.TailFile.getFilesToTail(TailFile.java:419)
at 
org.apache.nifi.processors.standard.TailFile.customValidate(TailFile.java:296)
at 
org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:126)
at 
org.apache.nifi.util.MockProcessContext.validate(MockProcessContext.java:226)
at 
org.apache.nifi.util.MockProcessContext.assertValid(MockProcessContext.java:243)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:161)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:152)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:147)
at 
org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:142)
at 
org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesWithBasedirAndFilenameEL(TestTailFile.java:634)

testMultipleFilesChangingNameStrategy(org.apache.nifi.processors.standard.TestTailFile)
  Time elapsed: 0.026 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<0>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at 
org.apache.nifi.util.StandardProcessorTestRunner.assertTransferCount(StandardProcessorTestRunner.java:319)
at 
org.apache.nifi.util.StandardProcessorTestRunner.assertAllFlowFilesTransferred(StandardProcessorTestRunner.java:314)
at 
org.apache.nifi.processors.standard.TestTailFile.testMultipleFilesChangingNameStrategy(TestTailFile.java:738)

testMultipleFiles(org.apache.nifi.processors.standard.TestTailFile)  Time 
elapsed: 0.139 sec  <<< ERROR!
java.util.regex.PatternSyntaxException: Unmatched closing ')' near index 15
target\(testDir/)?log(ging)?.txt
   ^
at java.util.regex.Pattern.error(Pattern.java:1955)
at

[jira] [Commented] (NIFI-3078) Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)


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

ASF GitHub Bot commented on NIFI-3078:
--

Github user asfgit closed the pull request at:

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


> Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)
> 
>
> Key: NIFI-3078
> URL: https://issues.apache.org/jira/browse/NIFI-3078
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
> Fix For: 1.1.0
>
>
> As a partial improvement of providing more examples for 
> InvokeScriptedProcessor as described in NIFI-1954 , I'd like to contribute 
> TestInvokeJavascript unit test class that I wrote to understand how to use 
> the processor with Javascript.
> Currently there are test classes available for Groovy and Jython.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1255: NIFI-3078: Test InvokeScriptedProcessor with JS.

Github user asfgit closed the pull request at:

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


---
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-3078) Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)

2016-11-22 Thread ASF subversion and git services (JIRA)


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

ASF GitHub Bot commented on NIFI-3078:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1255
  
LGTM, tests are checking a large set of cases, ran a contrib-check, I'm a 
+1. Merging to master.


> Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)
> 
>
> Key: NIFI-3078
> URL: https://issues.apache.org/jira/browse/NIFI-3078
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
>
> As a partial improvement of providing more examples for 
> InvokeScriptedProcessor as described in NIFI-1954 , I'd like to contribute 
> TestInvokeJavascript unit test class that I wrote to understand how to use 
> the processor with Javascript.
> Currently there are test classes available for Groovy and Jython.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3078) Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)


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

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

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

NIFI-3078: Test InvokeScriptedProcessor with JS.

This closes #1255.


> Add unit test class for InvokeScriptedProcessor with ECMAScript (Javascript)
> 
>
> Key: NIFI-3078
> URL: https://issues.apache.org/jira/browse/NIFI-3078
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Minor
>
> As a partial improvement of providing more examples for 
> InvokeScriptedProcessor as described in NIFI-1954 , I'd like to contribute 
> TestInvokeJavascript unit test class that I wrote to understand how to use 
> the processor with Javascript.
> Currently there are test classes available for Groovy and Jython.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3084) Provenance Repo Failures

2016-11-22 Thread ASF subversion and git services (JIRA)

Joseph Percivall created NIFI-3084:
--

 Summary: Provenance Repo Failures
 Key: NIFI-3084
 URL: https://issues.apache.org/jira/browse/NIFI-3084
 Project: Apache NiFi
  Issue Type: Sub-task
Reporter: Joseph Percivall
Priority: Blocker
 Fix For: 1.1.0


Build fails with the following errors on the current master when built on 
Windows 8. When running the units tests from Intellij I see a subset of the 
below errors. Typically it is:  
"testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
and "testIndexOnRolloverAndSubsequentSearch"

---
 T E S T S
---
Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - in 
org.apache.nifi.provenance.lucene.TestCachingIndexManager
Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - in 
org.apache.nifi.provenance.lucene.TestSimpleIndexManager
Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
<<< FAILURE! - in org.apache.nifi.provenance.TestPersistentProvenanceRepository
testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.047 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 10.031 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.11 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.141 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 8.39 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\c8c56a43-c930-4f64-a496-66edcce8e39d\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

[jira] [Updated] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response

2016-11-22 Thread Pierre Villard (JIRA)


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

Pierre Villard updated NIFI-3082:
-
   Resolution: Fixed
Fix Version/s: 1.1.0
   Status: Resolved  (was: Patch Available)

> PutElasticsearchHttp fails to dequeue item on 5xx response
> --
>
> Key: NIFI-3082
> URL: https://issues.apache.org/jira/browse/NIFI-3082
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Carson Gaspar
>Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match 
> the index format), PutElasticsearchHttp does not dequeue the item, causing it 
> to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed 
> outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response


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

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

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

NIFI-3082: Fixed status code handling in PutElasticsearchHttp

This closes #1258.


> PutElasticsearchHttp fails to dequeue item on 5xx response
> --
>
> Key: NIFI-3082
> URL: https://issues.apache.org/jira/browse/NIFI-3082
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Carson Gaspar
>Assignee: Matt Burgess
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match 
> the index format), PutElasticsearchHttp does not dequeue the item, causing it 
> to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed 
> outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1258: NIFI-3082: Fixed status code handling in PutElastic...

Github user asfgit closed the pull request at:

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


---
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-3082) PutElasticsearchHttp fails to dequeue item on 5xx response


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

ASF GitHub Bot commented on NIFI-3082:
--

Github user asfgit closed the pull request at:

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


> PutElasticsearchHttp fails to dequeue item on 5xx response
> --
>
> Key: NIFI-3082
> URL: https://issues.apache.org/jira/browse/NIFI-3082
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Carson Gaspar
>Assignee: Matt Burgess
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match 
> the index format), PutElasticsearchHttp does not dequeue the item, causing it 
> to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed 
> outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response


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

ASF GitHub Bot commented on NIFI-3082:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1258
  
+1 LGTM, checked the code and ran contrib check. Merging to master.


> PutElasticsearchHttp fails to dequeue item on 5xx response
> --
>
> Key: NIFI-3082
> URL: https://issues.apache.org/jira/browse/NIFI-3082
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Carson Gaspar
>Assignee: Matt Burgess
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match 
> the index format), PutElasticsearchHttp does not dequeue the item, causing it 
> to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed 
> outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1258: NIFI-3082: Fixed status code handling in PutElasticsearchH...

2016-11-22 Thread pvillard31

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/1258
  
+1 LGTM, checked the code and ran contrib check. Merging to master.


---
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-3068) NiFi can not reliably support multiple HDFS clusters in the same flow


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

Bryan Bende updated NIFI-3068:
--
Status: Patch Available  (was: Open)

> NiFi can not reliably support multiple HDFS clusters in the same flow
> -
>
> Key: NIFI-3068
> URL: https://issues.apache.org/jira/browse/NIFI-3068
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Sam Hjelmfelt
>Assignee: Bryan Bende
>  Labels: HDFS
> Attachments: NIFI-3068.patch
>
>
> The HDFS configurations in PutHDFS are not respected when two (or more) 
> PutHDFS processors exist with different configurations. The second processor 
> to run will use the configurations from the first processor. This can cause 
> data to be written to the wrong cluster.
> This appears to be caused by configuration caching in 
> AbstractHadoopProcessor, which would affect all HDFS processors.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L144



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3068) NiFi can not reliably support multiple HDFS clusters in the same flow


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

Bryan Bende commented on NIFI-3068:
---

Using the latest code from master (1.1-SNAPSHOT) I have been unable to 
reproduce a scenario where a PutHDFS processor writes to the wrong cluster. 

I did determine that there appears to be some shared state in the Hadoop client 
related to security. The scenario was the following:

- One PutHDFS processor writing to a kerberized HDFS
- Start a second PutHDFS processor writing to a non-secure HDFS, writes 
successfully
- The first PutHDFS processor now gets an error:

{code}
2016-11-21 22:05:43,610 ERROR [Timer-Driven Process Thread-2] 
o.apache.nifi.processors.hadoop.PutHDFS 
PutHDFS[id=01581004-7069-19ef-5ec2-87b728465117] Failed to write to HDFS due to 
org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not 
enabled.  Available:[TOKEN, KERBEROS]: 
org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not 
enabled.  Available:[TOKEN, KERBEROS]
2016-11-21 22:05:43,612 ERROR [Timer-Driven Process Thread-2] 
o.apache.nifi.processors.hadoop.PutHDFS
org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not 
enabled.  Available:[TOKEN, KERBEROS]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method) ~[na:1.8.0_74]
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
 ~[na:1.8.0_74]
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 ~[na:1.8.0_74]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) 
~[na:1.8.0_74]
at 
org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
 ~[hadoop-common-2.7.3.jar:na]
at 
org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73)
 ~[hadoop-common-2.7.3.jar:na]
at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2110) 
~[hadoop-hdfs-2.7.3.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1305)
 ~[hadoop-hdfs-2.7.3.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1301)
 ~[hadoop-hdfs-2.7.3.jar:na]
at 
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
 ~[hadoop-common-2.7.3.jar:na]
at 
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1317)
 ~[hadoop-hdfs-2.7.3.jar:na]
at 
org.apache.nifi.processors.hadoop.PutHDFS.onTrigger(PutHDFS.java:255) 
~[nifi-hdfs-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]
{code}

If the processor with the error is started and stopped it gets back to a 
working state, and both processors are working at the same time again.

I've tested adding the @RequiresInstanceClassLoading to PutHDFS which will 
guarantee that each instance of the processor has its own ClassLoader and thus 
can't share any state between instances, and this resolves the problem. 

I will attach a patch adding the annotation.

> NiFi can not reliably support multiple HDFS clusters in the same flow
> -
>
> Key: NIFI-3068
> URL: https://issues.apache.org/jira/browse/NIFI-3068
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.0.0
>Reporter: Sam Hjelmfelt
>Assignee: Bryan Bende
>  Labels: HDFS
>
> The HDFS configurations in PutHDFS are not respected when two (or more) 
> PutHDFS processors exist with different configurations. The second processor 
> to run will use the configurations from the first processor. This can cause 
> data to be written to the wrong cluster.
> This appears to be caused by configuration caching in 
> AbstractHadoopProcessor, which would affect all HDFS processors.
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/AbstractHadoopProcessor.java#L144



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response


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

ASF GitHub Bot commented on NIFI-3082:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-3082: Fixed status code handling in PutElasticsearchHttp

For consistency, the status code handling is now the same as 
FetchElasticsearchHttp with respect to status codes and transfer relationships.


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

$ git pull https://github.com/mattyb149/nifi NIFI-3082

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

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


commit ef04a496c2c6bc51d02ba025954ca1d98698515c
Author: Matt Burgess 
Date:   2016-11-22T17:53:45Z

NIFI-3082: Fixed status code handling in PutElasticsearchHttp




> PutElasticsearchHttp fails to dequeue item on 5xx response
> --
>
> Key: NIFI-3082
> URL: https://issues.apache.org/jira/browse/NIFI-3082
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Carson Gaspar
>Assignee: Matt Burgess
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match 
> the index format), PutElasticsearchHttp does not dequeue the item, causing it 
> to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed 
> outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1258: NIFI-3082: Fixed status code handling in PutElastic...

2016-11-22 Thread mattyb149

GitHub user mattyb149 opened a pull request:

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

NIFI-3082: Fixed status code handling in PutElasticsearchHttp

For consistency, the status code handling is now the same as 
FetchElasticsearchHttp with respect to status codes and transfer relationships.


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

$ git pull https://github.com/mattyb149/nifi NIFI-3082

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

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


commit ef04a496c2c6bc51d02ba025954ca1d98698515c
Author: Matt Burgess 
Date:   2016-11-22T17:53:45Z

NIFI-3082: Fixed status code handling in PutElasticsearchHttp




---
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] [Assigned] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response


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

Matt Burgess reassigned NIFI-3082:
--

Assignee: Matt Burgess

> PutElasticsearchHttp fails to dequeue item on 5xx response
> --
>
> Key: NIFI-3082
> URL: https://issues.apache.org/jira/browse/NIFI-3082
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Carson Gaspar
>Assignee: Matt Burgess
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match 
> the index format), PutElasticsearchHttp does not dequeue the item, causing it 
> to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed 
> outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2854) Enable repositories to support upgrades and rollback in well defined scenarios

2016-11-22 Thread Joseph Witt (JIRA)

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

Joseph Witt updated NIFI-2854:
--
Description:
The flowfile, swapfile, provenance, and content repositories play a very
important roll in NiFi's ability to be safely upgraded and rolled back. We
need to have well documented behaviors, designs, and version adherence so that
users can safely rely on these mechanisms.

Once this is formalized and in place we should update our versioning guidance
to reflect this as well.

The following would be true from NiFi 1.2.0 onward

* No changes to how the repositories are persisted to disk can be made which
will break forward/backward compatibility and specifically this means that
things like the way each is serialized to disk cannot change.
* If changes are made which impact forward or backward compatibility they
should be reserved for major releases only and should include a utility to help
users with pre-existing data convert from some older format to the newer
format. It may not be feasible to have rollback on major releases.
* The content repository should not be changed within a major release cycle in
any way that will harm forward or backward compatibility.
* The flow file repository can change in that new fields can be added to
existing write ahead log record types but no fields can be removed nor can any
new types be added. Once a field is considered required it must remain
required. Changes may only be made across minor version changes - not
incremental.
* Swap File storage should follow very similar rules to the flow file
repository. Adding a schema to the swap file header may allow some variation
there but the variation should only be hints to optimize how they're processed
and not change their behavior otherwise. Changes are only permitted during
minor version releases.
* Provenance repository changes are only permitted during minor version
releases. These changes may include adding or removing fields from existing
event types. If a field is considered required it must always be considered
required. If a field is removed then it must not be a required field and there
must be a sensible default an older version could use if that value is not
found in new data once rolled back. New event types may be added. Fields or
event types not known to older version, if seen after a rollback, will simply
be ignored.

The following also would be true:
* Apache NiFi 1.0.0 repositories should work just fine when applied to an
Apache NiFi 1.1.0 installation.
* Repositories made/updated in Apache NiFi 1.1.0 onward would not work in older
Apache NiFi releases (such as 1.0.0)

was:
The flowfile, swapfile, provenance, and content repositories play a very
important roll in NiFi's ability to be safely upgraded and rolled back. We
need to have well documented behaviors, designs, and version adherence so that
users can safely rely on these mechanisms.

Once this is formalized and in place we should update our versioning guidance
to reflect this as well.

The following would be true from NiFi 1.2.0 onward

[jira] [Updated] (NIFI-3064) ExecuteSQL convert to Avro fails when a MySQL query returns two columns with the same name even with different aliases


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

Matt Burgess updated NIFI-3064:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> ExecuteSQL convert to Avro fails when a MySQL query returns two columns with 
> the same name even with different aliases
> --
>
> Key: NIFI-3064
> URL: https://issues.apache.org/jira/browse/NIFI-3064
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.0.0, 0.7.0, 0.6.1
>Reporter: Karthik Narayanan
>Assignee: Karthik Narayanan
> Fix For: 1.1.0
>
>
> For the following query:
> select A.host as host1,B.host as host from `hosts` A  join host2 B on 
> B.hostid=A.hostid;
> A.host and B.host are columns that have same name, but come from different 
> tables, and have a different alias name. But looks like Avro conversion is 
> ignoring the alias and just looking at the column name. This causes the query 
> to fail with this error
> Duplicate Field Name in any.data.hosts ; name type UNION pos:1 and name type 
> UNION pos:0.
> I have attached a screenshot for the same. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1251: NiFI-3064 convert to Avro fails when a MySQL query ...

Github user asfgit closed the pull request at:

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


---
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-3083) Build fails on Windows 8

Joseph Percivall created NIFI-3083:
--

 Summary: Build fails on Windows 8
 Key: NIFI-3083
 URL: https://issues.apache.org/jira/browse/NIFI-3083
 Project: Apache NiFi
  Issue Type: Bug
 Environment: Windows 8
Reporter: Joseph Percivall
Priority: Blocker
 Fix For: 1.1.0


Build fails with the following errors on the current master when built on 
Windows 8. When running the units tests from Intellij I see a subset of the 
below errors. Typically it is:  
"testIndexAndCompressOnRolloverAndSubsequentEmptySearch", "testBackPressure" 
and "testIndexOnRolloverAndSubsequentSearch"

---
 T E S T S
---
Running org.apache.nifi.provenance.lucene.TestCachingIndexManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.391 sec - in 
org.apache.nifi.provenance.lucene.TestCachingIndexManager
Running org.apache.nifi.provenance.lucene.TestSimpleIndexManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.046 sec - in 
org.apache.nifi.provenance.lucene.TestSimpleIndexManager
Running org.apache.nifi.provenance.TestPersistentProvenanceRepository
Tests run: 30, Failures: 1, Errors: 23, Skipped: 2, Time elapsed: 160.653 sec 
<<< FAILURE! - in org.apache.nifi.provenance.TestPersistentProvenanceRepository
testNotAuthorizedGetSpecificEvent(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.047 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\1ec64b68-d0b3-41a9-8c22-ae272e889ea1\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testModifyIndexWhileSearching(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 10.031 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\99589698-4b40-443f-9aaf-cac69807c243\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testNotAuthorizedQuery(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.11 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\107b3965-7143-429c-a4e3-8f40dde92250\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testIndexOnRolloverWithImmenseAttribute(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 5.141 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\5b5b1185-d38a-4284-91f1-cde93bfabebb\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

testIndexAndCompressOnRolloverAndSubsequentEmptySearch(org.apache.nifi.provenance.TestPersistentProvenanceRepository)
  Time elapsed: 8.39 sec  <<< ERROR!
java.io.IOException: Unable to delete 
C:\nifi\nifi-nar-bundles\nifi-provenance-repository-bundle\nifi-persistent-provenance-repository\target\storage\c8c56a43-c930-4f64-a496-66edcce8e39d\0.prov.gz
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:252)
at org.apache.nifi.util.file.FileUtils.deleteFiles(FileUtils.java:242)
at org.apache.nifi.util.file.FileUtils.deleteFile(FileUtils.java:248)
at 
org.apache.nifi.provenance.TestPersistentProvenanceRepository.closeRepo(TestPersistentProvenanceRepository.java:149)

[jira] [Commented] (NIFI-3079) Regression in session read counting


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

ASF GitHub Bot commented on NIFI-3079:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1256
  
@markap14 can you close this when you get a chance? I put the JIRA number 
instead of the PR number in the "This closes..." statement.


> Regression in session read counting
> ---
>
> Key: NIFI-3079
> URL: https://issues.apache.org/jira/browse/NIFI-3079
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
> Attachments: Screen Shot 2016-11-21 at 11.26.28 PM.png
>
>
> See attached screenshot.  The count for bytes read should not be zero on 
> compress content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3079) Regression in session read counting

2016-11-22 Thread ASF subversion and git services (JIRA)


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

Bryan Bende updated NIFI-3079:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Regression in session read counting
> ---
>
> Key: NIFI-3079
> URL: https://issues.apache.org/jira/browse/NIFI-3079
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
> Attachments: Screen Shot 2016-11-21 at 11.26.28 PM.png
>
>
> See attached screenshot.  The count for bytes read should not be zero on 
> compress content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3079) Regression in session read counting


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

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

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

NIFI-3079: Ensure that in all cases we increment session's bytesRead count when 
finished reading from Content Repo

This closes #3079.

Signed-off-by: Bryan Bende 


> Regression in session read counting
> ---
>
> Key: NIFI-3079
> URL: https://issues.apache.org/jira/browse/NIFI-3079
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
> Attachments: Screen Shot 2016-11-21 at 11.26.28 PM.png
>
>
> See attached screenshot.  The count for bytes read should not be zero on 
> compress content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3076) ExecuteSQL error when table uses unsigned MEDIUMINT


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

Matt Burgess updated NIFI-3076:
---
Assignee: Matt Burgess
  Status: Patch Available  (was: Open)

> ExecuteSQL error when table uses unsigned MEDIUMINT
> ---
>
> Key: NIFI-3076
> URL: https://issues.apache.org/jira/browse/NIFI-3076
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>
> When using a MySQL table with a column defined as an unsigned MEDIUMINT, the 
> following error occurs:
> ExecuteSQL[id=fa363402-bbc0-1802--96aa31f4] 
> ExecuteSQL[id=fa363402-bbc0-1802--96aa31f4] failed to process session 
> due to org.apache.avro.file.DataFileWriter$AppendWriteException: 
> org.apache.avro.UnresolvedUnionException: Not in union ["null","long"]: 
> 141419: org.apache.avro.file.DataFileWriter$AppendWriteException: 
> org.apache.avro.UnresolvedUnionException: Not in union ["null","long"]: 141419



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response

2016-11-22 Thread Carson Gaspar (JIRA)

Carson Gaspar created NIFI-3082:
---

 Summary: PutElasticsearchHttp fails to dequeue item on 5xx response
 Key: NIFI-3082
 URL: https://issues.apache.org/jira/browse/NIFI-3082
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Carson Gaspar


When Elasticsearch returns a 5xx response (e.g. when a field doesn't match the 
index format), PutElasticsearchHttp does not dequeue the item, causing it to 
infinitely retry and cause a backlog.

Expected behaviour would be to route the item to either the retry or failed 
outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3081) add property to set ignoring hostname verification check in ssl context service

2016-11-22 Thread Karthik Narayanan (JIRA)


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

Karthik Narayanan commented on NIFI-3081:
-

To get this implemented I was thinking of adding the logic in the 
SSLContextFactory class in wifi-security-utils. The hope is that adding it here 
would make it available to any processor that uses the sslcontextservice. The 
particular use case for this change is with connecting to a jus provider via 
ssl. The development environment hostname does not match with the certificate 
and the connection is failing. 

The property would be set to true / false ,and should be EL enabled. If the EL 
value is not set then the property would default to true, thus forcing the user 
to explicitly set it , knowing the risks.



> add property to set ignoring hostname verification check in ssl context 
> service
> ---
>
> Key: NIFI-3081
> URL: https://issues.apache.org/jira/browse/NIFI-3081
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Karthik Narayanan
>Assignee: Karthik Narayanan
>
> In development environments it is pretty normal for users to use self signed 
> certificates, which may not always match the domain name of the service. It 
> would be useful to have a property that disables hostname verification. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1256: NIFI-3079: Ensure that in all cases we increment session's...

2016-11-22 Thread bbende

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1256
  
Reviewing...


---
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-3079) Regression in session read counting


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

ASF GitHub Bot commented on NIFI-3079:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/1256
  
Reviewing...


> Regression in session read counting
> ---
>
> Key: NIFI-3079
> URL: https://issues.apache.org/jira/browse/NIFI-3079
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Joseph Witt
>Assignee: Mark Payne
>Priority: Critical
> Fix For: 1.1.0
>
> Attachments: Screen Shot 2016-11-21 at 11.26.28 PM.png
>
>
> See attached screenshot.  The count for bytes read should not be zero on 
> compress content.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3041) Remove references to Windows start-nifi.bat tool in Admin Guide


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

ASF GitHub Bot commented on NIFI-3041:
--

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi-site/pull/8

NIFI-3041 Removed references to Windows start-nifi.bat and stop-nifi.…

…bat in Quickstart guide

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

$ git pull https://github.com/andrewmlim/nifi-site NIFI-3041

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

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


commit 114094353cd46bd1b1b5ed2c74a7694372230387
Author: Andrew Lim 
Date:   2016-11-22T15:16:14Z

NIFI-3041 Removed references to Windows start-nifi.bat and stop-nifi.bat in 
Quickstart guide




> Remove references to Windows start-nifi.bat tool in Admin Guide
> ---
>
> Key: NIFI-3041
> URL: https://issues.apache.org/jira/browse/NIFI-3041
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0, 0.7.1
>Reporter: Andy LoPresto
>Assignee: Andrew Lim
>  Labels: documentation, windows
>
> As documented by this question on HCC [1], there are references in the NiFi 
> quick start guide [2] and admin guide [3] that reference Windows shell script 
> artifacts that no longer exist for running NiFi in the foreground/background. 
> The documentation should be updated to be correct, and new documentation or a 
> new tool should be provided to allow users to run NiFi in the background on 
> Windows [4]. 
> [1] 
> https://community.hortonworks.com/questions/66408/nifis-start-nifibat-documentation.html
> [2] https://nifi.apache.org/quickstart.html
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
> [3] 
> https://nifi.apache.org/docs/nifi-docs/html/getting-started.html#for-windows-users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi-site pull request #8: NIFI-3041 Removed references to Windows start-nif...

2016-11-22 Thread andrewmlim

GitHub user andrewmlim opened a pull request:

https://github.com/apache/nifi-site/pull/8

NIFI-3041 Removed references to Windows start-nifi.bat and stop-nifi.â¦

â¦bat in Quickstart guide

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

$ git pull https://github.com/andrewmlim/nifi-site NIFI-3041

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

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


commit 114094353cd46bd1b1b5ed2c74a7694372230387
Author: Andrew Lim 
Date:   2016-11-22T15:16:14Z

NIFI-3041 Removed references to Windows start-nifi.bat and stop-nifi.bat in 
Quickstart guide




---
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 pull request #1256: NIFI-3079: Ensure that in all cases we increment se...

2016-11-22 Thread markap14

GitHub user markap14 opened a pull request:

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

NIFI-3079: Ensure that in all cases we increment session's bytesRead â¦

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.

â¦count when finished reading from Content Repo

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

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

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

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


commit 7b6dad16e6852f01ffc32212e4e8a8143ff100ff
Author: Mark Payne 
Date:   2016-11-22T14:41:34Z

NIFI-3079: Ensure that in all cases we increment session's bytesRead count 
when finished reading from Content Repo




---
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-3041) Remove references to Windows start-nifi.bat tool in Admin Guide