[GitHub] nifi pull request: NIFI-1180: Modify PutS3Object to enable encrypt...

[adamonduty]

GitHub user adamonduty opened a pull request:

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

NIFI-1180: Modify PutS3Object to enable encryption

This adds a property to set server side encryption on PutS3Object. In 
addition, it adds `s3.sseAlgorithm` to `FetchS3Object` so users of that 
processor will know if object encryption is turned on.

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

$ git pull https://github.com/adamonduty/nifi NIFI-1180

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

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


commit 522787dd5f6a11a0e6b8e97266106dfc66d9c09e
Author: Adam Lamar 
Date:   2016-02-21T06:12:56Z

NIFI-1180: Modify PutS3Object to enable encryption




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

Apache NiFi 0.5.1 RC helper

[Tony Kurc]

Hello Apache NiFi community,

Here again is guidance to help those interested in validating/verifying the
release so they can vote.

# Download latest KEYS file:
  https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
  gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-0.5.1 source release artifacts for review:

  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.1/nifi-0.5.1-source-release.zip
  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.1/nifi-0.5.1-source-release.zip.asc
  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.1/nifi-0.5.1-source-release.zip.md5
  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.1/nifi-0.5.1-source-release.zip.sha1

# Verify the signature
  gpg --verify nifi-0.5.1-source-release.zip.asc

# Verify the hashes (md5 and sha1) match the source and what was provided
in the vote email thread
  md5sum nifi-0.5.1-source-release.zip
  sha1sum nifi-0.5.1-source-release.zip

# Unzip nifi-0.5.1-source-release.zip

# Verify the build works including release audit tool (RAT) checks
  cd nifi-0.5.1
  mvn clean install -Pcontrib-check

# Verify the contents contain a good readme, notice, and license.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the readme, license, notice are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!

[GitHub] nifi pull request: NIFI-840: Create ListS3 processor

[adamonduty]

Github user adamonduty commented on the pull request:

https://github.com/apache/nifi/pull/238#issuecomment-187523459
  
@jskora Nice catch, I fixed the state issue and it seemed to work in my 
tests. I also rebased against master, added the recent proxy attributes, and 
changed the attribute `s3.storageClass` to `s3.storeClass` since that is the 
attribute used by `PutS3Object`.


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

Re: [DISCUSS] NiFi 0.5.1 release

[Tony Kurc]

Yes, now working off 2a459fe21c708c8316dd255c3dc7f8254e7940f1

On Mon, Feb 22, 2016 at 9:48 PM, Joe Witt  wrote:

> Tony,
>
> Went through all commits on the support/nifi-0.5.x branch and all
> JIRAs on 0.5.1.  It appears all are good except [1] and [2].  These
> did get applied to master but not to the support branch.
>
> Can you please apply them?
>
> [1] https://issues.apache.org/jira/browse/NIFI-1514
> [2] https://issues.apache.org/jira/browse/NIFI-1282
>
> Thanks
> Joe
>
> On Mon, Feb 22, 2016 at 9:18 PM, Joe Witt  wrote:
> > Confirmed that is the expected commit.  I'll check each commit id
> > against all JIRAs for 0.5.1 now too.
> >
> > Thanks Tony!
> >
> > On Mon, Feb 22, 2016 at 9:16 PM, Tony Kurc  wrote:
> >> Starting rc1 build off of 280714942097b0703a1f8f92913d95159cd89bfa
> >>
> >> On Mon, Feb 22, 2016 at 9:12 PM, Matt Gilman 
> >> wrote:
> >>
> >>> Patch has been incorporated into master and support/nifi-0.5.x. Thanks.
> >>>
> >>> On Mon, Feb 22, 2016 at 7:34 PM, Joe Witt  wrote:
> >>>
> >>> > Would like to get james wing patch incorporated.  Will ping asap.
> >>> >
> >>> > Thanks
> >>> > Joe
> >>> > On Feb 22, 2016 7:22 PM, "Tony Kurc"  wrote:
> >>> >
> >>> > > All, I've started building nifi-0.5.1-RC1 from commit
> >>> > > f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you
> believe
> >>> > this
> >>> > > is erroneous
> >>> > >
> >>> > > On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc 
> wrote:
> >>> > >
> >>> > > > Yes.
> >>> > > > On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
> >>> > > >
> >>> > > >> Tony,
> >>> > > >>
> >>> > > >> I believe 0.5.1 is ready to roll with the exception of
> NIFI-1542 and
> >>> > > >> NIFI-1545 needing to be merged in.  They appear ready to roll.
> Can
> >>> > > >> you do that as part of kicking off the RC?
> >>> > > >>
> >>> > > >> Thanks
> >>> > > >> Joe
> >>> > > >>
> >>> > > >> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
> >>> > > >>  wrote:
> >>> > > >> > 1536 will be in shortly
> >>> > > >> >
> >>> > > >> > Sent from my iPhone
> >>> > > >> >
> >>> > > >> >> On Feb 21, 2016, at 14:17, Joe Witt 
> wrote:
> >>> > > >> >>
> >>> > > >> >> Tony,
> >>> > > >> >>
> >>> > > >> >> Just chatted with Oleg.  Sounds like he has a potential
> solution
> >>> > for
> >>> > > >> >> NIFI-1536.  I did some testing for NIFI-1527 that I've
> reopened
> >>> so
> >>> > we
> >>> > > >> >> can validate what was observed.  NIFI-1542 is open.
> >>> > > >> >>
> >>> > > >> >> NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but
> NIFI-1527
> >>> > > >> should not be.
> >>> > > >> >>
> >>> > > >> >> So looks like we're not quite ready yet.
> >>> > > >> >>
> >>> > > >> >> Thanks
> >>> > > >> >> Joe
> >>> > > >> >>
> >>> > > >> >>> On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc <
> trk...@gmail.com>
> >>> > > wrote:
> >>> > > >> >>> sunday works for me.
> >>> > > >> >>>
> >>> > > >>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt <
> joe.w...@gmail.com>
> >>> > > >> wrote:
> >>> > > >> 
> >>> > > >>  Ok so looks like the major players for the 0.5.1 release
> are
> >>> in.
> >>> > > >>  Today during some testing it was discovered that there can
> be
> >>> > > issues
> >>> > > >>  with multiple HDFS processors with differing
> configurations and
> >>> > > >>  yesterday on StackOverflow it was reported that there are
> some
> >>> > > issues
> >>> > > >>  talking to Kafka but there is a viable workaround for
> now.  I
> >>> > > >>  personally feel like what we have for an 0.5.1 is good
> right
> >>> now
> >>> > > >>  without those two JIRAs and that we could do an 0.5.2 if
> those
> >>> > get
> >>> > > >>  sorted soon or they can go in 0.6.0 which if we stick to
> the
> >>> > > >>  previously discussed idea would be mid-March.
> >>> > > >> 
> >>> > > >>  What do ya'll think?
> >>> > > >> 
> >>> > > >>  If we did a kick-off of RC say late Sunday (assuming RM is
> on
> >>> > board
> >>> > > >>  too of course) we'd be looking at a midweek release for
> 0.5.1
> >>> > > >> 
> >>> > > >>  Thanks
> >>> > > >>  Joe
> >>> > > >> 
> >>> > > >> > On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt <
> joe.w...@gmail.com
> >>> >
> >>> > > >> wrote:
> >>> > > >> > +1
> >>> > > >> >
> >>> > > >> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <
> >>> trk...@gmail.com>
> >>> > > >> wrote:
> >>> > > >> >> All,
> >>> > > >> >> Just so we're clear, my expectations is that the fixes we
> >>> need
> >>> > > >> above
> >>> > > >>  will
> >>> > > >> >> go into master (0.6.0-SNAPSHOT). I (or the contributor)
> will
> >>> > > >> attempt to
> >>> > > >> >> also apply those fixes to a branch I made off of
> nifi-0.5.0,
> >>> > > called
> >>> > > >> >> "support/nifi-0.5.x", and when done we can test 

Re: [DISCUSS] NiFi 0.5.1 release

[Joe Witt]

Tony,

Went through all commits on the support/nifi-0.5.x branch and all
JIRAs on 0.5.1.  It appears all are good except [1] and [2].  These
did get applied to master but not to the support branch.

Can you please apply them?

[1] https://issues.apache.org/jira/browse/NIFI-1514
[2] https://issues.apache.org/jira/browse/NIFI-1282

Thanks
Joe

On Mon, Feb 22, 2016 at 9:18 PM, Joe Witt  wrote:
> Confirmed that is the expected commit.  I'll check each commit id
> against all JIRAs for 0.5.1 now too.
>
> Thanks Tony!
>
> On Mon, Feb 22, 2016 at 9:16 PM, Tony Kurc  wrote:
>> Starting rc1 build off of 280714942097b0703a1f8f92913d95159cd89bfa
>>
>> On Mon, Feb 22, 2016 at 9:12 PM, Matt Gilman 
>> wrote:
>>
>>> Patch has been incorporated into master and support/nifi-0.5.x. Thanks.
>>>
>>> On Mon, Feb 22, 2016 at 7:34 PM, Joe Witt  wrote:
>>>
>>> > Would like to get james wing patch incorporated.  Will ping asap.
>>> >
>>> > Thanks
>>> > Joe
>>> > On Feb 22, 2016 7:22 PM, "Tony Kurc"  wrote:
>>> >
>>> > > All, I've started building nifi-0.5.1-RC1 from commit
>>> > > f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you believe
>>> > this
>>> > > is erroneous
>>> > >
>>> > > On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc  wrote:
>>> > >
>>> > > > Yes.
>>> > > > On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
>>> > > >
>>> > > >> Tony,
>>> > > >>
>>> > > >> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
>>> > > >> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
>>> > > >> you do that as part of kicking off the RC?
>>> > > >>
>>> > > >> Thanks
>>> > > >> Joe
>>> > > >>
>>> > > >> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
>>> > > >>  wrote:
>>> > > >> > 1536 will be in shortly
>>> > > >> >
>>> > > >> > Sent from my iPhone
>>> > > >> >
>>> > > >> >> On Feb 21, 2016, at 14:17, Joe Witt  wrote:
>>> > > >> >>
>>> > > >> >> Tony,
>>> > > >> >>
>>> > > >> >> Just chatted with Oleg.  Sounds like he has a potential solution
>>> > for
>>> > > >> >> NIFI-1536.  I did some testing for NIFI-1527 that I've reopened
>>> so
>>> > we
>>> > > >> >> can validate what was observed.  NIFI-1542 is open.
>>> > > >> >>
>>> > > >> >> NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527
>>> > > >> should not be.
>>> > > >> >>
>>> > > >> >> So looks like we're not quite ready yet.
>>> > > >> >>
>>> > > >> >> Thanks
>>> > > >> >> Joe
>>> > > >> >>
>>> > > >> >>> On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc 
>>> > > wrote:
>>> > > >> >>> sunday works for me.
>>> > > >> >>>
>>> > > >>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt 
>>> > > >> wrote:
>>> > > >> 
>>> > > >>  Ok so looks like the major players for the 0.5.1 release are
>>> in.
>>> > > >>  Today during some testing it was discovered that there can be
>>> > > issues
>>> > > >>  with multiple HDFS processors with differing configurations and
>>> > > >>  yesterday on StackOverflow it was reported that there are some
>>> > > issues
>>> > > >>  talking to Kafka but there is a viable workaround for now.  I
>>> > > >>  personally feel like what we have for an 0.5.1 is good right
>>> now
>>> > > >>  without those two JIRAs and that we could do an 0.5.2 if those
>>> > get
>>> > > >>  sorted soon or they can go in 0.6.0 which if we stick to the
>>> > > >>  previously discussed idea would be mid-March.
>>> > > >> 
>>> > > >>  What do ya'll think?
>>> > > >> 
>>> > > >>  If we did a kick-off of RC say late Sunday (assuming RM is on
>>> > board
>>> > > >>  too of course) we'd be looking at a midweek release for 0.5.1
>>> > > >> 
>>> > > >>  Thanks
>>> > > >>  Joe
>>> > > >> 
>>> > > >> > On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt >> >
>>> > > >> wrote:
>>> > > >> > +1
>>> > > >> >
>>> > > >> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <
>>> trk...@gmail.com>
>>> > > >> wrote:
>>> > > >> >> All,
>>> > > >> >> Just so we're clear, my expectations is that the fixes we
>>> need
>>> > > >> above
>>> > > >>  will
>>> > > >> >> go into master (0.6.0-SNAPSHOT). I (or the contributor) will
>>> > > >> attempt to
>>> > > >> >> also apply those fixes to a branch I made off of nifi-0.5.0,
>>> > > called
>>> > > >> >> "support/nifi-0.5.x", and when done we can test and when
>>> > > satisfied,
>>> > > >>  start
>>> > > >> >> the 0.5.1 release process.
>>> > > >> >>
>>> > > >> >>
>>> > > >> >>> On Wed, Feb 17, 2016 at 8:28 PM, Tony Kurc <
>>> trk...@gmail.com>
>>> > > >> wrote:
>>> > > >> >>>
>>> > > >> >>> I lieu of a decision on a git branching strategy, does
>>> anyone
>>> > > >> object
>>> > > >>  to me
>>> > > >> >>> naming a branch "support/0.5.x" so I 

Re: [DISCUSS] NiFi 0.5.1 release

[Tony Kurc]

Starting rc1 build off of 280714942097b0703a1f8f92913d95159cd89bfa

On Mon, Feb 22, 2016 at 9:12 PM, Matt Gilman 
wrote:

> Patch has been incorporated into master and support/nifi-0.5.x. Thanks.
>
> On Mon, Feb 22, 2016 at 7:34 PM, Joe Witt  wrote:
>
> > Would like to get james wing patch incorporated.  Will ping asap.
> >
> > Thanks
> > Joe
> > On Feb 22, 2016 7:22 PM, "Tony Kurc"  wrote:
> >
> > > All, I've started building nifi-0.5.1-RC1 from commit
> > > f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you believe
> > this
> > > is erroneous
> > >
> > > On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc  wrote:
> > >
> > > > Yes.
> > > > On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
> > > >
> > > >> Tony,
> > > >>
> > > >> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
> > > >> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
> > > >> you do that as part of kicking off the RC?
> > > >>
> > > >> Thanks
> > > >> Joe
> > > >>
> > > >> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
> > > >>  wrote:
> > > >> > 1536 will be in shortly
> > > >> >
> > > >> > Sent from my iPhone
> > > >> >
> > > >> >> On Feb 21, 2016, at 14:17, Joe Witt  wrote:
> > > >> >>
> > > >> >> Tony,
> > > >> >>
> > > >> >> Just chatted with Oleg.  Sounds like he has a potential solution
> > for
> > > >> >> NIFI-1536.  I did some testing for NIFI-1527 that I've reopened
> so
> > we
> > > >> >> can validate what was observed.  NIFI-1542 is open.
> > > >> >>
> > > >> >> NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527
> > > >> should not be.
> > > >> >>
> > > >> >> So looks like we're not quite ready yet.
> > > >> >>
> > > >> >> Thanks
> > > >> >> Joe
> > > >> >>
> > > >> >>> On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc 
> > > wrote:
> > > >> >>> sunday works for me.
> > > >> >>>
> > > >>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt 
> > > >> wrote:
> > > >> 
> > > >>  Ok so looks like the major players for the 0.5.1 release are
> in.
> > > >>  Today during some testing it was discovered that there can be
> > > issues
> > > >>  with multiple HDFS processors with differing configurations and
> > > >>  yesterday on StackOverflow it was reported that there are some
> > > issues
> > > >>  talking to Kafka but there is a viable workaround for now.  I
> > > >>  personally feel like what we have for an 0.5.1 is good right
> now
> > > >>  without those two JIRAs and that we could do an 0.5.2 if those
> > get
> > > >>  sorted soon or they can go in 0.6.0 which if we stick to the
> > > >>  previously discussed idea would be mid-March.
> > > >> 
> > > >>  What do ya'll think?
> > > >> 
> > > >>  If we did a kick-off of RC say late Sunday (assuming RM is on
> > board
> > > >>  too of course) we'd be looking at a midweek release for 0.5.1
> > > >> 
> > > >>  Thanks
> > > >>  Joe
> > > >> 
> > > >> > On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt  >
> > > >> wrote:
> > > >> > +1
> > > >> >
> > > >> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <
> trk...@gmail.com>
> > > >> wrote:
> > > >> >> All,
> > > >> >> Just so we're clear, my expectations is that the fixes we
> need
> > > >> above
> > > >>  will
> > > >> >> go into master (0.6.0-SNAPSHOT). I (or the contributor) will
> > > >> attempt to
> > > >> >> also apply those fixes to a branch I made off of nifi-0.5.0,
> > > called
> > > >> >> "support/nifi-0.5.x", and when done we can test and when
> > > satisfied,
> > > >>  start
> > > >> >> the 0.5.1 release process.
> > > >> >>
> > > >> >>
> > > >> >>> On Wed, Feb 17, 2016 at 8:28 PM, Tony Kurc <
> trk...@gmail.com>
> > > >> wrote:
> > > >> >>>
> > > >> >>> I lieu of a decision on a git branching strategy, does
> anyone
> > > >> object
> > > >>  to me
> > > >> >>> naming a branch "support/0.5.x" so I can start pulling
> > together
> > > >> 0.5.1?
> > > >> >>>
> > > >>  On Wed, Feb 17, 2016 at 8:17 PM, Joe Witt <
> > joe.w...@gmail.com>
> > > >> wrote:
> > > >> 
> > > >>  Team,
> > > >> 
> > > >>  First, congrats on getting 0.5.0 out the door.  Very nice
> > > >> release with
> > > >>  excellent new features, enhancements, and bug fixes with
> > > >> involvement
> > > >>  of many new contributors.
> > > >> 
> > > >>  The effort toward 0.6.0 is well underway and if we are
> > shooting
> > > >> for
> > > >>  our original target would still arrive around mid
> march-ish.
> > > >> Seems
> > > >>  reasonable given progress so far.
> > > >> 
> > > >>  That said, I'd like to propose we go ahead and put out an
> > 0.5.1
> > > >> as
> > > >> 

[GitHub] nifi pull request: NIFI-1548 Fixing Controller Service Usage Butto...

[mcgilman]

Github user mcgilman commented on the pull request:

https://github.com/apache/nifi/pull/245#issuecomment-187482738
  
@jvwing Thanks for the contribution! Merged to master and 0.5.1.


---
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: NIFI-1548 Fixing Controller Service Usage Butto...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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: NIFI-1548 Fixing Controller Service Usage Butto...

[mcgilman]

Github user mcgilman commented on the pull request:

https://github.com/apache/nifi/pull/245#issuecomment-187468431
  
reviewing now


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

Re: [DISCUSS] NiFi 0.5.1 release

[Tony Kurc]

All, I've started building nifi-0.5.1-RC1 from commit
f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you believe this
is erroneous

On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc  wrote:

> Yes.
> On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
>
>> Tony,
>>
>> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
>> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
>> you do that as part of kicking off the RC?
>>
>> Thanks
>> Joe
>>
>> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
>>  wrote:
>> > 1536 will be in shortly
>> >
>> > Sent from my iPhone
>> >
>> >> On Feb 21, 2016, at 14:17, Joe Witt  wrote:
>> >>
>> >> Tony,
>> >>
>> >> Just chatted with Oleg.  Sounds like he has a potential solution for
>> >> NIFI-1536.  I did some testing for NIFI-1527 that I've reopened so we
>> >> can validate what was observed.  NIFI-1542 is open.
>> >>
>> >> NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527
>> should not be.
>> >>
>> >> So looks like we're not quite ready yet.
>> >>
>> >> Thanks
>> >> Joe
>> >>
>> >>> On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc  wrote:
>> >>> sunday works for me.
>> >>>
>>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt 
>> wrote:
>> 
>>  Ok so looks like the major players for the 0.5.1 release are in.
>>  Today during some testing it was discovered that there can be issues
>>  with multiple HDFS processors with differing configurations and
>>  yesterday on StackOverflow it was reported that there are some issues
>>  talking to Kafka but there is a viable workaround for now.  I
>>  personally feel like what we have for an 0.5.1 is good right now
>>  without those two JIRAs and that we could do an 0.5.2 if those get
>>  sorted soon or they can go in 0.6.0 which if we stick to the
>>  previously discussed idea would be mid-March.
>> 
>>  What do ya'll think?
>> 
>>  If we did a kick-off of RC say late Sunday (assuming RM is on board
>>  too of course) we'd be looking at a midweek release for 0.5.1
>> 
>>  Thanks
>>  Joe
>> 
>> > On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt 
>> wrote:
>> > +1
>> >
>> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc 
>> wrote:
>> >> All,
>> >> Just so we're clear, my expectations is that the fixes we need
>> above
>>  will
>> >> go into master (0.6.0-SNAPSHOT). I (or the contributor) will
>> attempt to
>> >> also apply those fixes to a branch I made off of nifi-0.5.0, called
>> >> "support/nifi-0.5.x", and when done we can test and when satisfied,
>>  start
>> >> the 0.5.1 release process.
>> >>
>> >>
>> >>> On Wed, Feb 17, 2016 at 8:28 PM, Tony Kurc 
>> wrote:
>> >>>
>> >>> I lieu of a decision on a git branching strategy, does anyone
>> object
>>  to me
>> >>> naming a branch "support/0.5.x" so I can start pulling together
>> 0.5.1?
>> >>>
>>  On Wed, Feb 17, 2016 at 8:17 PM, Joe Witt 
>> wrote:
>> 
>>  Team,
>> 
>>  First, congrats on getting 0.5.0 out the door.  Very nice
>> release with
>>  excellent new features, enhancements, and bug fixes with
>> involvement
>>  of many new contributors.
>> 
>>  The effort toward 0.6.0 is well underway and if we are shooting
>> for
>>  our original target would still arrive around mid march-ish.
>> Seems
>>  reasonable given progress so far.
>> 
>>  That said, I'd like to propose we go ahead and put out an 0.5.1
>> as
>>  soon as the patches are addressed.  The finding that Lars helped
>>  expose and that Mark Payne is now working  [1] in my view
>> warrants a
>>  release by itself as it is data loss related.  Also, we can
>> address
>>  the work Matt Gilman is doing to ensure properly authorized
>> users can
>>  access resources they're being blocked by [2] and the
>> license/notice
>>  findings Sean discovered during the last release [3].  There are
>> a
>>  couple odd/ends in the list as well [4].  Purely a bug fix
>> release as
>>  spec'd out in release notes [5].
>> 
>>  I checked with Tony and he is happy to continue performing RM
>> tasks on
>>  the 0.5.x line.
>> 
>>  [1] https://issues.apache.org/jira/browse/NIFI-1527
>>  [2] https://issues.apache.org/jira/browse/NIFI-1497
>>  [3] https://issues.apache.org/jira/browse/NIFI-1520
>>  [4] https://s.apache.org/nifi-0.5.1-candidate
>>  [5]
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
>> 
>>  Thanks
>>  Joe
>> >>
>>
>

[GitHub] nifi pull request: NIFI-1548 Fixing Controller Service Usage Butto...

[jvwing]

GitHub user jvwing opened a pull request:

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

NIFI-1548 Fixing Controller Service Usage Button

Recovering the event handling code for the Controller Service and Reporting 
Task usage buttons.

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

$ git pull https://github.com/jvwing/nifi NIFI-1548-controller-service-usage

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

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


commit 85b29a26c645bbee3eb734ccb99202b6f02ece3f
Author: James Wing 
Date:   2016-02-22T23:49:03Z

NIFI-1548 Fixing Controller Service Usage Button




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

Re: [DISCUSS] NiFi 0.5.1 release

[Tony Kurc]

Yes.
On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:

> Tony,
>
> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
> you do that as part of kicking off the RC?
>
> Thanks
> Joe
>
> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
>  wrote:
> > 1536 will be in shortly
> >
> > Sent from my iPhone
> >
> >> On Feb 21, 2016, at 14:17, Joe Witt  wrote:
> >>
> >> Tony,
> >>
> >> Just chatted with Oleg.  Sounds like he has a potential solution for
> >> NIFI-1536.  I did some testing for NIFI-1527 that I've reopened so we
> >> can validate what was observed.  NIFI-1542 is open.
> >>
> >> NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527
> should not be.
> >>
> >> So looks like we're not quite ready yet.
> >>
> >> Thanks
> >> Joe
> >>
> >>> On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc  wrote:
> >>> sunday works for me.
> >>>
>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  wrote:
> 
>  Ok so looks like the major players for the 0.5.1 release are in.
>  Today during some testing it was discovered that there can be issues
>  with multiple HDFS processors with differing configurations and
>  yesterday on StackOverflow it was reported that there are some issues
>  talking to Kafka but there is a viable workaround for now.  I
>  personally feel like what we have for an 0.5.1 is good right now
>  without those two JIRAs and that we could do an 0.5.2 if those get
>  sorted soon or they can go in 0.6.0 which if we stick to the
>  previously discussed idea would be mid-March.
> 
>  What do ya'll think?
> 
>  If we did a kick-off of RC say late Sunday (assuming RM is on board
>  too of course) we'd be looking at a midweek release for 0.5.1
> 
>  Thanks
>  Joe
> 
> > On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt 
> wrote:
> > +1
> >
> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc 
> wrote:
> >> All,
> >> Just so we're clear, my expectations is that the fixes we need above
>  will
> >> go into master (0.6.0-SNAPSHOT). I (or the contributor) will
> attempt to
> >> also apply those fixes to a branch I made off of nifi-0.5.0, called
> >> "support/nifi-0.5.x", and when done we can test and when satisfied,
>  start
> >> the 0.5.1 release process.
> >>
> >>
> >>> On Wed, Feb 17, 2016 at 8:28 PM, Tony Kurc 
> wrote:
> >>>
> >>> I lieu of a decision on a git branching strategy, does anyone
> object
>  to me
> >>> naming a branch "support/0.5.x" so I can start pulling together
> 0.5.1?
> >>>
>  On Wed, Feb 17, 2016 at 8:17 PM, Joe Witt 
> wrote:
> 
>  Team,
> 
>  First, congrats on getting 0.5.0 out the door.  Very nice release
> with
>  excellent new features, enhancements, and bug fixes with
> involvement
>  of many new contributors.
> 
>  The effort toward 0.6.0 is well underway and if we are shooting
> for
>  our original target would still arrive around mid march-ish.
> Seems
>  reasonable given progress so far.
> 
>  That said, I'd like to propose we go ahead and put out an 0.5.1 as
>  soon as the patches are addressed.  The finding that Lars helped
>  expose and that Mark Payne is now working  [1] in my view
> warrants a
>  release by itself as it is data loss related.  Also, we can
> address
>  the work Matt Gilman is doing to ensure properly authorized users
> can
>  access resources they're being blocked by [2] and the
> license/notice
>  findings Sean discovered during the last release [3].  There are a
>  couple odd/ends in the list as well [4].  Purely a bug fix
> release as
>  spec'd out in release notes [5].
> 
>  I checked with Tony and he is happy to continue performing RM
> tasks on
>  the 0.5.x line.
> 
>  [1] https://issues.apache.org/jira/browse/NIFI-1527
>  [2] https://issues.apache.org/jira/browse/NIFI-1497
>  [3] https://issues.apache.org/jira/browse/NIFI-1520
>  [4] https://s.apache.org/nifi-0.5.1-candidate
>  [5]
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
> 
>  Thanks
>  Joe
> >>
>

Re: [DISCUSS] NiFi 0.5.1 release

[Joe Witt]

Tony,

I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
you do that as part of kicking off the RC?

Thanks
Joe

On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
 wrote:
> 1536 will be in shortly
>
> Sent from my iPhone
>
>> On Feb 21, 2016, at 14:17, Joe Witt  wrote:
>>
>> Tony,
>>
>> Just chatted with Oleg.  Sounds like he has a potential solution for
>> NIFI-1536.  I did some testing for NIFI-1527 that I've reopened so we
>> can validate what was observed.  NIFI-1542 is open.
>>
>> NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527 should not 
>> be.
>>
>> So looks like we're not quite ready yet.
>>
>> Thanks
>> Joe
>>
>>> On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc  wrote:
>>> sunday works for me.
>>>
 On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  wrote:

 Ok so looks like the major players for the 0.5.1 release are in.
 Today during some testing it was discovered that there can be issues
 with multiple HDFS processors with differing configurations and
 yesterday on StackOverflow it was reported that there are some issues
 talking to Kafka but there is a viable workaround for now.  I
 personally feel like what we have for an 0.5.1 is good right now
 without those two JIRAs and that we could do an 0.5.2 if those get
 sorted soon or they can go in 0.6.0 which if we stick to the
 previously discussed idea would be mid-March.

 What do ya'll think?

 If we did a kick-off of RC say late Sunday (assuming RM is on board
 too of course) we'd be looking at a midweek release for 0.5.1

 Thanks
 Joe

> On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt  wrote:
> +1
>
>> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  wrote:
>> All,
>> Just so we're clear, my expectations is that the fixes we need above
 will
>> go into master (0.6.0-SNAPSHOT). I (or the contributor) will attempt to
>> also apply those fixes to a branch I made off of nifi-0.5.0, called
>> "support/nifi-0.5.x", and when done we can test and when satisfied,
 start
>> the 0.5.1 release process.
>>
>>
>>> On Wed, Feb 17, 2016 at 8:28 PM, Tony Kurc  wrote:
>>>
>>> I lieu of a decision on a git branching strategy, does anyone object
 to me
>>> naming a branch "support/0.5.x" so I can start pulling together 0.5.1?
>>>
 On Wed, Feb 17, 2016 at 8:17 PM, Joe Witt  wrote:

 Team,

 First, congrats on getting 0.5.0 out the door.  Very nice release with
 excellent new features, enhancements, and bug fixes with involvement
 of many new contributors.

 The effort toward 0.6.0 is well underway and if we are shooting for
 our original target would still arrive around mid march-ish.  Seems
 reasonable given progress so far.

 That said, I'd like to propose we go ahead and put out an 0.5.1 as
 soon as the patches are addressed.  The finding that Lars helped
 expose and that Mark Payne is now working  [1] in my view warrants a
 release by itself as it is data loss related.  Also, we can address
 the work Matt Gilman is doing to ensure properly authorized users can
 access resources they're being blocked by [2] and the license/notice
 findings Sean discovered during the last release [3].  There are a
 couple odd/ends in the list as well [4].  Purely a bug fix release as
 spec'd out in release notes [5].

 I checked with Tony and he is happy to continue performing RM tasks on
 the 0.5.x line.

 [1] https://issues.apache.org/jira/browse/NIFI-1527
 [2] https://issues.apache.org/jira/browse/NIFI-1497
 [3] https://issues.apache.org/jira/browse/NIFI-1520
 [4] https://s.apache.org/nifi-0.5.1-candidate
 [5] https://cwiki.apache.org/confluence/display/NIFI/Release+Notes

 Thanks
 Joe
>>

[GitHub] nifi pull request: NIFI-1536 ensured that UserGroupInformation is ...

[asfgit]

Github user asfgit closed the pull request at:

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


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

Re: Logging issue in Jira

[Matt Gilman]

Devin,

Thanks for reporting and showing interest in NiFi!

There should be a button in the toolbar at the top that says Create. I
believe this button is only visible if you are logged in. Have you created
a JIRA account?

Matt

On Mon, Feb 22, 2016 at 3:02 PM, Devin Fisher <
devin.fis...@perfectsearchcorp.com> wrote:

> I noticed a small copy and past error in LdapProvider class. (the error
> message is not using the right variable) I tried to create a ticket in Jira
> but don't see how to do so. Look through the Contributor Guide and did not
> see info on how to log a bug. What is the best approach to log an issue?
>
> Devin
>

Logging issue in Jira

[Devin Fisher]

I noticed a small copy and past error in LdapProvider class. (the error
message is not using the right variable) I tried to create a ticket in Jira
but don't see how to do so. Look through the Contributor Guide and did not
see info on how to log a bug. What is the best approach to log an issue?

Devin

[GitHub] nifi pull request: NIFI-1539 - Add normalization of content type f...

[mcgilman]

Github user mcgilman commented on the pull request:

https://github.com/apache/nifi/pull/242#issuecomment-187358663
  
Overall, the changes look good. Just need to clarify the point about the 
Java version and verify it works now that NIFI-1546 is addressed. 

Thanks!


---
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: NIFI-1539 - Add normalization of content type f...

[mcgilman]

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

https://github.com/apache/nifi/pull/242#discussion_r53682786
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-content-viewer/pom.xml
 ---
@@ -104,6 +104,14 @@
 
 
 
+
--- End diff --

NiFi requires Java 1.7. Is there any reason that is being overridden here?


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

Re: Issue connecting to Oracle-HPSM using NIFI

[Bryan Bende]

Naveen,

Can you check nifi_home/logs/nifi-app.log to see if there is a full stack
trace beyond the message that says "unsupported feature"?

Would be curious to see what the full stack trace looks like.

-Bryan


On Mon, Feb 22, 2016 at 2:26 PM, Kilaru, Naveen Kumar <
naveenkumar.kil...@capitalone.com> wrote:

>
> Hi Apache-Nifi Dev Team,
>
>
> We are validating NIFI for our business solution and while we do a POC e
> are facing a strange issue using "nifi-1.1.1.0"
>
>
> We are trying to load the data from Oracle HPSM source system and we see
> below error message we are getting while we try to execute the flow.
>
>
> Query used : select query SELECT * FROM SERVICEMANAGER.DEVICE2M1
>
>
> Unable to execute SQL select query SELECT * FROM SERVICEMANAGER.DEVICE2M1
> due to org.apache.nifi.processor.exception.ProcessException:
> java.sql.SQLException: Unsupported feature. No incoming flow file to route
> to failure:
>
> org.apache.nifi.processor.exception.ProcessException:
> java.sql.SQLException: Unsupported feature
>
> Please help us with this issue as we would like to use NIFI in our tech
> stack for current implementation.
>
> Note: Same flow was executed successfully with the query  "select * from
> sample"
>
> Thanks,
> Naveen
> 7326667677
> 
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>

[GitHub] nifi pull request: NIFI-840: Create ListS3 processor

[jskora]

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

https://github.com/apache/nifi/pull/238#discussion_r53674055
  
--- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/ListS3.java
 ---
@@ -0,0 +1,230 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.aws.s3;
+
+import com.amazonaws.services.s3.AmazonS3;
+import com.amazonaws.services.s3.model.ListObjectsRequest;
+import com.amazonaws.services.s3.model.ObjectListing;
+import com.amazonaws.services.s3.model.S3ObjectSummary;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
+import org.apache.nifi.annotation.behavior.Stateful;
+import org.apache.nifi.annotation.behavior.TriggerSerially;
+import org.apache.nifi.annotation.behavior.TriggerWhenEmpty;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.state.Scope;
+import org.apache.nifi.components.state.StateMap;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.concurrent.TimeUnit;
+
+@TriggerSerially
+@TriggerWhenEmpty
+@InputRequirement(Requirement.INPUT_FORBIDDEN)
+@Tags({"Amazon", "S3", "AWS", "list"})
+@CapabilityDescription("Retrieves a listing of objects from an S3 bucket. 
For each object that is listed, creates a FlowFile that represents \"\n" +
+"+ \"the object so that it can be fetched in conjunction 
with FetchS3Object. This Processor is designed to run on Primary Node only 
\"\n" +
+"+ \"in a cluster. If the primary node changes, the new 
Primary Node will pick up where the previous node left off without duplicating 
\"\n" +
+"+ \"all of the data.")
+@Stateful(scopes = Scope.CLUSTER, description = "After performing a 
listing of keys, the timestamp of the newest key is stored, "
++ "along with the keys that share that same timestamp. This allows 
the Processor to list only keys that have been added or modified after "
++ "this date the next time that the Processor is run. State is 
stored across the cluster so that this Processor can be run on Primary Node 
only and if a new Primary "
++ "Node is selected, the new node can pick up where the previous 
node left off, without duplicating the data.")
+@WritesAttributes({
+@WritesAttribute(attribute = "s3.bucket", description = "The name 
of the S3 bucket"),
+@WritesAttribute(attribute = "filename", description = "The name 
of the file"),
+@WritesAttribute(attribute = "s3.etag", description = "The ETag 
that can be used to see if the file has changed"),
+@WritesAttribute(attribute = "s3.lastModified", description = "The 
last modified time in milliseconds since epoch in UTC time"),
+@WritesAttribute(attribute = "s3.length", description = "The size 
of the object in bytes"),
+@WritesAttribute(attribute = "s3.storageClass", description = "The 
storage class of the object"),})
+@SeeAlso({FetchS3Object.class, PutS3Object.class, DeleteS3Object.class})
+public class ListS3 

[GitHub] nifi pull request: NIFI-786 AWS credential refactoring and enhance...

[jvwing]

GitHub user jvwing opened a pull request:

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

NIFI-786 AWS credential refactoring and enhancements

Changes to AWS credential handling:

* Refactoring the creation of AWS Credentials into a factory class for use 
by AWSCredentialsProviderControllerService (included) and future shared use by 
processors or other components.
* Centralized the PropertyDescriptors used for AWS Credential configuration 
to standardize behavior and improve documentation.
* Improved self-documentation by making Default Credentials an explicit and 
visible option, while preserving the behavior of using it implicity if no other 
credential type is configured.
 * In this commit, the explicit Use Default Credential option defaults to 
"false", to maintain backward compatibility upgrading to this implementation.
* Credential enhancements
 * New credential option - Named Profile
 * New credential option - Anonymous
 * Added External ID as an optional parameter for Assume Role

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

$ git pull https://github.com/jvwing/nifi NIFI-786-refactor-aws-credentials

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

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


commit 164ebcd9c89a28ae6c1b40fb009044bc04de3195
Author: James Wing 
Date:   2016-02-22T18:14:47Z

NIFI-786 AWS credential refactoring and enhancements




---
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: NIFI-1545 Update AWS S3 IT tests for new proxy ...

[jskora]

GitHub user jskora opened a pull request:

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

NIFI-1545 Update AWS S3 IT tests for new proxy properties

Adjust integration tests ITDeleteS3Object, ITFetchS3Object, and 
ITPutS3Object to account for AWS new proxy properties.  Correct typo in 
AbstractS3Processor.createClient() log message.

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

$ git pull https://github.com/jskora/nifi NIFI-1489-itfixes

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

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


commit 61d9b71dcea5c45cc84b4b7b873c6b2fe337c164
Author: Joe Skora 
Date:   2016-02-22T13:22:58Z

Adjust integration tests ITDeleteS3Object, ITFetchS3Object, and 
ITPutS3Object to account for AWS new proxy properties.  Correct typo in 
AbstractS3Processor.createClient() log message.




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

Re: 3rd Party Dependencies

[Joe Witt]

Jeremy

You now have two different answers to the same question so let's apply
some context to avoid misleading others.

If the question is about 'How during build time can I create artifacts
which pull in all the dependencies I need even when some may not be
available in public repositories or repositories already known by the
NiFi build?'

  -- Then follow my response.

If the question is about 'If I create custom extensions or use
extensions which support binding to a dependency at runtime what is
the recommended way to do that?'

  -- Then follow Oleg's response and keep in mind that this concept is
purely a function of the given extension and what it was built to
support.

Thanks
Joe

On Mon, Feb 22, 2016 at 8:25 AM, Jeremy Dyer  wrote:
> Joe and Oleg,
>
> Thank you both for the information. Joe I agree with your point that maven
> should be leveraged as much as possible. I will have to check with the
> original author of the code to see if publishing to some maven repository
> would be allowed. Fingers crossed.
>
> Oleg that is very helpful information for sure and if the maven repository
> publishing becomes a road block I will certainly fall back to this approach.
>
> Thanks
>
> On Mon, Feb 22, 2016 at 8:18 AM, Oleg Zhurakousky <
> ozhurakou...@hortonworks.com> wrote:
>
>> Jeremy
>>
>> Actually the new JMS support which is going in 0.6 answers your exact
>> question since with this new support we are supporting non-OS JMS providers
>> (e.g., IBM, Tibco etc).
>> Basically you can look at https://github.com/apache/nifi/pull/222 and see
>> what’s going on (in ControllerServices specifically ), but in the nutshell,
>> user points to the directory containing additional resources that needs to
>> be added to the class path (e.g., JARs etc.)
>>
>> Oleg
>>
>> On Feb 22, 2016, at 8:07 AM, Jeremy Dyer  jdy...@gmail.com>> wrote:
>>
>> What would be the recommended way to include 3rd party dependencies for
>> building a custom processor that are not present in the public maven
>> repository? Local lib directory or ???
>>
>>

Re: 3rd Party Dependencies

[Jeremy Dyer]

Joe and Oleg,

Thank you both for the information. Joe I agree with your point that maven
should be leveraged as much as possible. I will have to check with the
original author of the code to see if publishing to some maven repository
would be allowed. Fingers crossed.

Oleg that is very helpful information for sure and if the maven repository
publishing becomes a road block I will certainly fall back to this approach.

Thanks

On Mon, Feb 22, 2016 at 8:18 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:

> Jeremy
>
> Actually the new JMS support which is going in 0.6 answers your exact
> question since with this new support we are supporting non-OS JMS providers
> (e.g., IBM, Tibco etc).
> Basically you can look at https://github.com/apache/nifi/pull/222 and see
> what’s going on (in ControllerServices specifically ), but in the nutshell,
> user points to the directory containing additional resources that needs to
> be added to the class path (e.g., JARs etc.)
>
> Oleg
>
> On Feb 22, 2016, at 8:07 AM, Jeremy Dyer > wrote:
>
> What would be the recommended way to include 3rd party dependencies for
> building a custom processor that are not present in the public maven
> repository? Local lib directory or ???
>
>

[GitHub] nifi pull request: NIFI-1539 - Add normalization of content type f...

[soenkeliebau]

GitHub user soenkeliebau opened a pull request:

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

NIFI-1539 - Add normalization of content type for content viewing

Pull request for 
[NIFI-1539](https://issues.apache.org/jira/browse/NIFI-1539)

Add code to ContentViewerController to strip content type of any trailing 
parameters and lowercase the type and subtype.

Added function to ViewableContent to enable retrieving the original value 
of the content type if needed.

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

$ git pull https://github.com/soenkeliebau/nifi NIFI-1539

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

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


commit 10d8227f443a82bfd644936866c18297f0ffb9e4
Author: Sönke Liebau 
Date:   2016-02-22T07:25:42Z

NIFI-1539 - Add normalization of content type for content viewing

Add code to ContentViewerController to strip content type of any trailing 
parameters and lowercase the type and subtype.

Added function to ViewableContent to enable retrieving the original value 
of the content type if needed.




---
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: NIFI-614 Added initial support for new style JM...

[olegz]

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

https://github.com/apache/nifi/pull/222#discussion_r53622460
  
--- Diff: nifi-nar-bundles/nifi-jms-bundle/nifi-jms-cf-service/.gitignore 
---
@@ -0,0 +1 @@
+/lib/
--- End diff --

It isn't ;)


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

Re: 3rd Party Dependencies

[Joe Witt]

Jeremy

Would strongly recommend that Maven and its artifact construct be
leveraged to the greatest extent possible.  For an organization using
libraries not available publicly it is often a good idea to have those
artifacts in their own repository.  That repository can be added to
their pom.xml so that Maven can find the artifacts.  You can see an
example of this in the root nifi pom.xml where the JCenter artifact
repository is added.

Thanks
Joe

On Mon, Feb 22, 2016 at 8:07 AM, Jeremy Dyer  wrote:
> What would be the recommended way to include 3rd party dependencies for
> building a custom processor that are not present in the public maven
> repository? Local lib directory or ???

3rd Party Dependencies

[Jeremy Dyer]

What would be the recommended way to include 3rd party dependencies for
building a custom processor that are not present in the public maven
repository? Local lib directory or ???

Re: Issue in Custom Processor in 0.4.1 version

[Jeremy Dyer]

Venkat,

Are you seeing any sort of error or warning in your nifi-app.log file?
Could you pass along your nifi-app.log file?

On Mon, Feb 22, 2016 at 5:10 AM, Venkat Sgk  wrote:

> Hi Team,
>
> We are using apache Nifi 0.4.1 and trying to write custom processor to
> convert CSV to avro.
> when modifying existing code and generated .nar file. When .nar is placed
> in lib directory, and started nifi server we were not able to access nifi (
> http://localhost:8080/nifi/).
>
> We checked the nifi status with status-nifi.bat it is saying server is
> running..
>
> We have seen this feature convert CSV to avro is available in 0.5.0
> version. ( InferAvroSchema).
>
>
> Could you please suggest how to fix this issue..
>
>
> Thanks,
> Venkat
>

Re: Issue in Custom Processor in 0.4.1 version

[Pierre Villard]

Hi,
Could you attach the logs?

2016-02-22 11:10 GMT+01:00 Venkat Sgk :

> Hi Team,
>
> We are using apache Nifi 0.4.1 and trying to write custom processor to
> convert CSV to avro.
> when modifying existing code and generated .nar file. When .nar is placed
> in lib directory, and started nifi server we were not able to access nifi (
> http://localhost:8080/nifi/).
>
> We checked the nifi status with status-nifi.bat it is saying server is
> running..
>
> We have seen this feature convert CSV to avro is available in 0.5.0
> version. ( InferAvroSchema).
>
>
> Could you please suggest how to fix this issue..
>
>
> Thanks,
> Venkat
>

Re: Issue in Custom Processor in 0.4.1 version

[Oleg Zhurakousky]

Could you please look at the logs and post any exceptions you see there?

Sent from my iPhone

> On Feb 22, 2016, at 06:57, Venkat Sgk  wrote:
> 
> Hi Team,
> 
> We are using apache Nifi 0.4.1 and trying to write custom processor to
> convert CSV to avro.
> when modifying existing code and generated .nar file. When .nar is placed
> in lib directory, and started nifi server we were not able to access nifi (
> http://localhost:8080/nifi/).
> 
> We checked the nifi status with status-nifi.bat it is saying server is
> running..
> 
> We have seen this feature convert CSV to avro is available in 0.5.0
> version. ( InferAvroSchema).
> 
> 
> Could you please suggest how to fix this issue..
> 
> 
> Thanks,
> Venkat