Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

I don't object. I can review tonight. On Mon, Dec 7, 2015 at 10:12 AM, Mark Payne wrote: > Errr, actually, after thinking about it more - operators who are running > on Windows should probably expect \ to be used instead of / > > So I think the better solution is to get

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Tony, I think there are really two possible solutions to this: 1) Always use / in the path attributes instead of \ -- i generally prefer this approach, as windows has worked with forward slashes since Win 98 (I believe?). 2) Have unit test look for file.separator -- benefit here is that it is

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

I disagree Mark, mainly due to the flowfile attributes such as 'path' that processors like GetFile (and I assume ListFile) create. Windows supports the forward slash but Unixes do not support the back slash File.separator. What happens when a flowfile created on a Windows NiFi is sent over to a

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Errr, actually, after thinking about it more - operators who are running on Windows should probably expect \ to be used instead of / So I think the better solution is to get rid of the "/" anywhere in the processor and tests and always use File.separator. Will do so and create a patch, if

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Probably want a function to go from dos to unix filenames. That replace is a little dangerous. Although is this seriously a use case? On Dec 7, 2015 10:44 AM, "Mark Payne" wrote: > Mike, > > That is accurate that Linux will not recognize \ as a path separator. It > would

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

i mentioned i'd get the RC out tonight and that just doesn't look likely. We worked through a series of annoying bugs that popped up as we explored various environments folks have (root/non-root) and different OSes and different browsers. Fun stuff. Looks like there is one last worthy item to

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

I think the correct way to move forward is to go ahead and keep the file separator, as it is consistent with how the GetFile processor works and probably most intuitive for windows users. However, I do think that using a forward-slash instead does provide benefit as it is portable across

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Is the consensus to go ahead with the release vote and this known bug, or is this a blocker? In other words, should we continue to check this release or consider the vote canceled? rb On 12/06/2015 09:11 PM, Tony Kurc wrote: Joe - I'm putting a ticket in for a fix. Looks like it was

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

The RC1 cancellation notice went out earlier. I'll send out another vote thread in a couple hours as the bug fixes are in. Thanks Joe On Mon, Dec 7, 2015 at 3:41 PM, Ryan Blue wrote: > Is the consensus to go ahead with the release vote and this known bug, or is > this a

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Unless I'm misunderstanding Mark, we have a known bug for "inconsistent path behavior between windows and unix-like operating systems" for ListFile, which may cause a listing on a windows system not work on FetchFile on a unix-like system, On Mon, Dec 7, 2015 at 3:47 PM, Joe Witt

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Great, I must have missed that. Thanks, Joe! rb On 12/07/2015 12:47 PM, Joe Witt wrote: The RC1 cancellation notice went out earlier. I'll send out another vote thread in a couple hours as the bug fixes are in. Thanks Joe On Mon, Dec 7, 2015 at 3:41 PM, Ryan Blue wrote:

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Tony, I think that is accurate - but with the caveat that it is not necessarily FetchFile that would have problems. I could see potentially using ListFile -> FetchFile on a windows machine and then using site-to-site to push to a Linux Machine, which then does PutFile -- essentially a way to

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

For what it is worth I agree with Moser's preference, as I understand it, of having standard treatment of slashes within NiFi. We should def have that discussion for 1.x As it is now we're basically undefined and loosely it would be 'we use the slashes of the machine that made the data' but we

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Ran through the helper provided by Joe and everything worked as anticipated.  Release notes, upgrade and migration guides all look satisfactory. +1, Release as Apache NiFi 0.4.0. - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com On Saturday, December 5, 2015

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

I've gotten confirmation of CentOS 7.1.1503 x86_64, Oracle JDK 8u66 working fine. and Fedora 23 not working with the same error that Andre reported. On Sun, Dec 6, 2015 at 5:50 PM, Tony Kurc wrote: > I'll also try it on windows 10 (again x64_64) > > On Sun, Dec 6, 2015 at 5:36

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Signatures and hashes look good. Built fine on Ubuntu 14.04 x86_64. I even cursed a little bit less at TestJdbcHugeStream! LICENSE, NOTICE and README look good. Docs look good. Binary ran successfully. +1 Did anyone try building on windows? On Sat, Dec 5, 2015 at 11:46 PM, Aldrin Piri

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

I can run it on Windows 8 tonight if no one else has. Joe Sent from my phone > On Dec 6, 2015, at 4:09 PM, Tony Kurc wrote: > > Signatures and hashes look good. > > Built fine on Ubuntu 14.04 x86_64. I even cursed a little bit less at > TestJdbcHugeStream! > > LICENSE,

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

I'll also try it on windows 10 (again x64_64) On Sun, Dec 6, 2015 at 5:36 PM, wrote: > I can run it on Windows 8 tonight if no one else has. > > Joe > > Sent from my phone > > > On Dec 6, 2015, at 4:09 PM, Tony Kurc wrote: > > > > Signatures

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Windows 8 build fails with maven 3.3.3 and Java 1.8.0_65. I get these error messages: TestListFile.testRecurse:441 expected: but was: TestTailFile.testMultipleRolloversAfterHavingReadAllDataWhileStillRunning:381 expected:<[world]> but was:<[abc These

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Joe, I had this happen and it worked on a second try. On Dec 6, 2015 11:23 PM, "Joe Percivall" wrote: > Windows 8 build fails with maven 3.3.3 and Java 1.8.0_65. > > I get these error messages: > > > TestListFile.testRecurse:441 expected: but >

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Yup I saw the same behavior. On the second try (doing mvn clean install -rf :nifi-standard-processors) the tailfile error went away. The listFile error still occurred though. Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On Sunday, December 6, 2015

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Er, just the tailfile error On Dec 6, 2015 11:31 PM, "Tony Kurc" wrote: > Joe, I had this happen and it worked on a second try. > On Dec 6, 2015 11:23 PM, "Joe Percivall" > wrote: > >> Windows 8 build fails with maven 3.3.3 and Java 1.8.0_65. >>

Re: [VOTE] Release Apache NiFi 0.4.0 (rc1)

Joe - I'm putting a ticket in for a fix. Looks like it was introduced by the NIFI-1246 patch. On Sun, Dec 6, 2015 at 11:36 PM, Joe Percivall < joeperciv...@yahoo.com.invalid> wrote: > Yup I saw the same behavior. > > On the second try (doing mvn clean install -rf :nifi-standard-processors) > the