Re: Source code for Version 0.3.0

[Adam Taft]

Just bumping this conversation.  Did we end up addressing this?  Are we
going for a signed release tag?  If so, does it make sense for the 0.3.0
tag to be signed by the releasor (I believe Matt Gilman)?  Or maybe just an
unsigned tag?

Thanks,

Adam


On Mon, Sep 21, 2015 at 2:28 PM, Joe Witt  wrote:

> Looks fairly straightforward to sign a release [1].
>
> What is the workflow you'd suggest?  Can we keep our current process
> and once the vote is done just add a step to make a new identical (but
> signed) tag with a name that doesn't include '-RC#'?
>
> I'm good with that.  I understand why the RC# throws folks off so
> happy to sort this out.
>
> [1] http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html
>
> On Mon, Sep 21, 2015 at 12:42 PM, Ryan Blue  wrote:
> > +1 for a nifi-0.3.0 release tag. Signed is even better, but I don't think
> > I'd mind if it weren't signed.
> >
> > rb
> >
> >
> > On 09/21/2015 06:35 AM, Sean Busbey wrote:
> >>
> >> The pattern I've liked the most on other projects is to create a
> >> proper release tag, signed by the RM on passage of the release vote. I
> >> don't recall off-hand what the phrasing was in the VOTE thread (if
> >> any).
> >>
> >> On Mon, Sep 21, 2015 at 8:13 AM, Adam Taft  wrote:
> >>>
> >>> What's the thoughts on creating a proper 0.3.0 tag, as would be
> >>> traditional
> >>> for a final release?  It is arguably a little confusing to only have
> the
> >>> RC
> >>> tags, when looking for the final release.  I found this head scratching
> >>> for
> >>> 0.2.0 as well.
> >>>
> >>> Adam
> >
> >
> >
> >
> > --
> > Ryan Blue
> > Software Engineer
> > Cloudera, Inc.
>

Re: NIFI RabbitMQ Processor

[Mark Payne]

Dave,

Absolutely.

The PutKafka processor (and associated TestPutKafka unit test class) which are 
found in the nar-bundles/nifi-kafka-bundle/nifi-kafka-processors module follow 
this pattern. 

The YandexTranslate (in the nifi-language-translation-bundle) also follows this 
pattern.

Thanks
-Mark


> On Oct 2, 2015, at 3:41 PM, DAVID SMITH  wrote:
> 
> Mark
> Thanks very much for the advice, that sounds a bit easier do you have an 
> example where you have done this sort of thing that I could have a look at?
> Many thanksDave 
> 
> 
> On Friday, 2 October 2015, 6:39, DAVID SMITH  
> wrote:
> 
> 
> Hi Chris
> 
> I have produced a set of processors which work with Java and C++ brokers (but 
> not RabbitMQ), but like you I haven't raised a ticket yet because
> I am unsure how to mock an AMQP broker.
> I would certainly be interested in seeing how you would do this.
> 
> Many thanks
> Dave
> 
> Sent from Yahoo! Mail on Android
> 
> 
> 

[GitHub] nifi pull request: NIFI-1020

[randerzander]

GitHub user randerzander opened a pull request:

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

NIFI-1020

Bumping Kafka API version to prevent PutKafka from writing to only one 
partition.

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

$ git pull https://github.com/randerzander/nifi master

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

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


commit da907d3d94b594e59859f1906a967fac5b0eba0c
Author: Randy Gelhausen 
Date:   2015-10-02T22:09:02Z

Bumped nifi-kafka-processors Kafka version




---
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-991: Add "upsert" verb support for Convert...

[randerzander]

Github user randerzander closed the pull request at:

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


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