Re: Access to Apache JIRA

[Joe Witt]

thanks Sarah!  You're added so you should be all set.

Joe

On Wed, Jul 20, 2016 at 11:14 PM, Sarah Olson
 wrote:
> Hi all,I am interested in creating some JIRAs and assigning them to myself so 
> that I can work on them. Can I get JIRA privileges to do this, please?My user 
> name is: solson75
> Thanks very much! Sarah Olson

Access to Apache JIRA

[Sarah Olson]

Hi all,I am interested in creating some JIRAs and assigning them to myself so 
that I can work on them. Can I get JIRA privileges to do this, please?My user 
name is: solson75
Thanks very much! Sarah Olson m: 415 298 5573

Re: Github write permission

[Koji Kawamura]

Bryan, I'll updated Github account to add apache.org address, thank you!

On Thu, Jul 21, 2016 at 12:59 AM, Bryan Bende  wrote:
> You should also be able to add your @apache.org email address as an
> additional email in your GitHub account.
>
> This way you can make commits with your apache.org if you want to.
>
> On Wed, Jul 20, 2016 at 11:20 AM, Koji Kawamura 
> wrote:
>
>> Hi Aldrin,
>>
>> Thank you for your prompt reply.
>> I understand that I need to commit to the ASF repo.
>>
>> The another thing I was wondering about was, how Github resolves a
>> relationship between Apache git user and Github user. I saw other
>> commits are properly related to Github user account, but mine was not.
>>
>> Talked with Joe Percivall, he advised me to use the same id and
>> email-address in ASF and Github. I was using @apache.org email when I
>> pushed the commit to ASF. After changing git config to use my private
>> email that I have been using on Github, commit to ASF is successfully
>> reflected in Github.
>>
>> Koji
>>
>> On Wed, Jul 20, 2016 at 11:56 PM, Aldrin Piri 
>> wrote:
>> > Hi Koji,
>> >
>> > GitHub is only a mirror of the ASF repos at this time. All commits must
>> be
>> > pushed to the ASF repositories and then are subsequently pushed to the
>> > GitHub repos.
>> > On Wed, Jul 20, 2016 at 10:39 Koji Kawamura 
>> wrote:
>> >
>> >> Hello team,
>> >>
>> >> I've just become a NiFi committer from today, got so excited.
>> >> Thank you for everyone who have been supporting me to made
>> contributions!
>> >>
>> >> I was able to setup my email, ssh, and made my first commit to
>> >> nifi-site project today.
>> >>
>> >> However, when I tried to push my commit to the nifi-site on Github, I
>> >> got a permission error, while doing so succeeded with Apache Git.
>> >> Do I need to ask infra for Github write permission?
>> >>
>> >> Thanks!
>> >> Koji
>> >>
>>

Re: PutS3Object error

[James Wing]

ListS3 processor is a great place to start.  I can think of a couple of
likely causes:

* Credentials - you might want to double-check how you specified the
credentials to make sure it is right.  If you specify access key and secret
key, and the secret key is not correct, I believe you will get this error.

* Region - you should make sure the region you specify in the processors
matches the S3 bucket's region.  S3 is a bit weird about the rules for
buckets and regions, but it might help to check.

Thanks,

James

On Wed, Jul 20, 2016 at 12:57 PM, Nabegh  wrote:

> Hi James,
>
> I'm using nifi-0.7.0-RC2. I tried ListS3 processor and I received the same
> error.
>
> Thanks
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/PutS3Object-error-tp12878p12880.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>

Re: PutS3Object error

[Nabegh]

Hi James,

I'm using nifi-0.7.0-RC2. I tried ListS3 processor and I received the same
error.

Thanks



--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/PutS3Object-error-tp12878p12880.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: PutS3Object error

[James Wing]

Nabegh,

Can you share which version of NiFi you are using?  Have you tried
GetS3Object?  I recommend also trying GetS3Object also to separate general
problems with authenticating and connecting to S3 from particular issues
putting objects, putting can be more complicated.

Thanks,

James


On Wed, Jul 20, 2016 at 12:09 PM, Nabegh  wrote:

> Hi .. PutS3Object processor is throwing the follow error .. Any idea why?
>
>
> 2016-07-20 15:25:41,922 ERROR [Timer-Driven Process Thread-6]
> o.a.nifi.processors.aws.s3.PutS3Object
> com.amazonaws.services.s3.model.AmazonS3Exception: The request signature we
> calculated does not match the signature you provided. Check your key and
> signing method. (Service: Amazon S3; Status Code: 403; Error Code:
> SignatureDoesNotMatch; Request ID: D433C836E1584299)
> at
>
> com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1219)
> ~[aws-java-sdk-core-1.10.32.jar:na]
> at
>
> com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:803)
> ~[aws-java-sdk-core-1.10.32.jar:na]
> at
>
> com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:505)
> ~[aws-java-sdk-core-1.10.32.jar:na]
> at
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:317)
> ~[aws-java-sdk-core-1.10.32.jar:na]
> at
> com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595)
> ~[aws-java-sdk-s3-1.10.32.jar:na]
> at
>
> com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1382)
> ~[aws-java-sdk-s3-1.10.32.jar:na]
> at
>
> org.apache.nifi.processors.aws.s3.PutS3Object$1.process(PutS3Object.java:446)
> ~[nifi-aws-processors-0.7.0.jar:0.7.0]
> at
>
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1851)
> ~[na:na]
> at
>
> org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1822)
> ~[na:na]
> at
>
> org.apache.nifi.processors.aws.s3.PutS3Object.onTrigger(PutS3Object.java:400)
> ~[nifi-aws-processors-0.7.0.jar:0.7.0]
> at
>
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> [nifi-api-0.7.0.jar:0.7.0]
> at
>
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> at
>
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> at
>
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> at
>
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_91]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [na:1.8.0_91]
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_91]
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> [na:1.8.0_91]
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_91]
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_91]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/PutS3Object-error-tp12878.html
> Sent from the Apache NiFi Developer List mailing list archive at
> Nabble.com.
>

PutS3Object error

[Nabegh]

Hi .. PutS3Object processor is throwing the follow error .. Any idea why?


2016-07-20 15:25:41,922 ERROR [Timer-Driven Process Thread-6]
o.a.nifi.processors.aws.s3.PutS3Object 
com.amazonaws.services.s3.model.AmazonS3Exception: The request signature we
calculated does not match the signature you provided. Check your key and
signing method. (Service: Amazon S3; Status Code: 403; Error Code:
SignatureDoesNotMatch; Request ID: D433C836E1584299)
at
com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1219)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:803)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:505)
~[aws-java-sdk-core-1.10.32.jar:na]
at 
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:317)
~[aws-java-sdk-core-1.10.32.jar:na]
at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3595)
~[aws-java-sdk-s3-1.10.32.jar:na]
at
com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1382)
~[aws-java-sdk-s3-1.10.32.jar:na]
at
org.apache.nifi.processors.aws.s3.PutS3Object$1.process(PutS3Object.java:446)
~[nifi-aws-processors-0.7.0.jar:0.7.0]
at
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1851)
~[na:na]
at
org.apache.nifi.controller.repository.StandardProcessSession.read(StandardProcessSession.java:1822)
~[na:na]
at
org.apache.nifi.processors.aws.s3.PutS3Object.onTrigger(PutS3Object.java:400)
~[nifi-aws-processors-0.7.0.jar:0.7.0]
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
[nifi-api-0.7.0.jar:0.7.0]
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054)
[nifi-framework-core-0.7.0.jar:0.7.0]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
[nifi-framework-core-0.7.0.jar:0.7.0]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
[nifi-framework-core-0.7.0.jar:0.7.0]
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127)
[nifi-framework-core-0.7.0.jar:0.7.0]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_91]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
[na:1.8.0_91]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
[na:1.8.0_91]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
[na:1.8.0_91]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_91]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]



--
View this message in context: 
http://apache-nifi-developer-list.39713.n7.nabble.com/PutS3Object-error-tp12878.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Github write permission

[Bryan Bende]

You should also be able to add your @apache.org email address as an
additional email in your GitHub account.

This way you can make commits with your apache.org if you want to.

On Wed, Jul 20, 2016 at 11:20 AM, Koji Kawamura 
wrote:

> Hi Aldrin,
>
> Thank you for your prompt reply.
> I understand that I need to commit to the ASF repo.
>
> The another thing I was wondering about was, how Github resolves a
> relationship between Apache git user and Github user. I saw other
> commits are properly related to Github user account, but mine was not.
>
> Talked with Joe Percivall, he advised me to use the same id and
> email-address in ASF and Github. I was using @apache.org email when I
> pushed the commit to ASF. After changing git config to use my private
> email that I have been using on Github, commit to ASF is successfully
> reflected in Github.
>
> Koji
>
> On Wed, Jul 20, 2016 at 11:56 PM, Aldrin Piri 
> wrote:
> > Hi Koji,
> >
> > GitHub is only a mirror of the ASF repos at this time. All commits must
> be
> > pushed to the ASF repositories and then are subsequently pushed to the
> > GitHub repos.
> > On Wed, Jul 20, 2016 at 10:39 Koji Kawamura 
> wrote:
> >
> >> Hello team,
> >>
> >> I've just become a NiFi committer from today, got so excited.
> >> Thank you for everyone who have been supporting me to made
> contributions!
> >>
> >> I was able to setup my email, ssh, and made my first commit to
> >> nifi-site project today.
> >>
> >> However, when I tried to push my commit to the nifi-site on Github, I
> >> got a permission error, while doing so succeeded with Apache Git.
> >> Do I need to ask infra for Github write permission?
> >>
> >> Thanks!
> >> Koji
> >>
>

Re: Github write permission

[Koji Kawamura]

Hi Aldrin,

Thank you for your prompt reply.
I understand that I need to commit to the ASF repo.

The another thing I was wondering about was, how Github resolves a
relationship between Apache git user and Github user. I saw other
commits are properly related to Github user account, but mine was not.

Talked with Joe Percivall, he advised me to use the same id and
email-address in ASF and Github. I was using @apache.org email when I
pushed the commit to ASF. After changing git config to use my private
email that I have been using on Github, commit to ASF is successfully
reflected in Github.

Koji

On Wed, Jul 20, 2016 at 11:56 PM, Aldrin Piri  wrote:
> Hi Koji,
>
> GitHub is only a mirror of the ASF repos at this time. All commits must be
> pushed to the ASF repositories and then are subsequently pushed to the
> GitHub repos.
> On Wed, Jul 20, 2016 at 10:39 Koji Kawamura  wrote:
>
>> Hello team,
>>
>> I've just become a NiFi committer from today, got so excited.
>> Thank you for everyone who have been supporting me to made contributions!
>>
>> I was able to setup my email, ssh, and made my first commit to
>> nifi-site project today.
>>
>> However, when I tried to push my commit to the nifi-site on Github, I
>> got a permission error, while doing so succeeded with Apache Git.
>> Do I need to ask infra for Github write permission?
>>
>> Thanks!
>> Koji
>>

Re: [ANNOUNCE] New Apache NiFi Committer Koji Kawamura

[Joe Skora]

Congratulations Koji!

Welcome to the team.

On Wed, Jul 20, 2016 at 10:41 AM, Koji Kawamura 
wrote:

> Thanks everyone! I'll keep trying my best to develop the great tool
> with this great community!
>
> Koji
>
> On Wed, Jul 20, 2016 at 6:43 PM, Pierre Villard
>  wrote:
> > Congrats Koji!
> >
> > Pierre
> >
> > 2016-07-20 3:16 GMT+02:00 Joe Percivall  >:
> >
> >>  Congrats Koji! - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
> >> joeperciv...@yahoo.com
> >>
> >>
> >> On Tuesday, July 19, 2016 9:13 PM, Oleg Zhurakousky <
> >> ozhurakou...@hortonworks.com> wrote:
> >>
> >>
> >>  Congrats Koji!
> >> Glad to see you on board!
> >>
> >> Oleg
> >> On Jul 19, 2016, at 7:45 PM, Andy LoPresto   >> alopre...@apache.org>> wrote:
> >>
> >> Congratulations Koji. Excited for even more great contributions.
> >>
> >> Andy LoPresto
> >> alopre...@apache.org
> >> alopresto.apa...@gmail.com
> >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >>
> >> On Jul 19, 2016, at 3:58 PM, Matt Burgess > mattyb...@gmail.com>> wrote:
> >>
> >> Congratulations and welcome Koji! Your contributions are greatly
> >> appreciated and I'm looking forward to more in the future!
> >>
> >> Regards,
> >> Matt
> >>
> >> On Tue, Jul 19, 2016 at 6:55 PM, Tony Kurc > tk...@apache.org>> wrote:
> >> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Koji
> >> Kawamura has accepted the PMC's invitation to become a committer on the
> >> Apache NiFi project. We greatly appreciate all of Koji's hard work and
> >> generous contributions and look forward to continued involvement in the
> >> project.
> >>
> >> Koji has been instrumental in couchbase integration, as well improving
> >> site-to-site. Welcome and congratulations!
> >>
> >> Tony
> >>
> >>
> >>
> >>
> >>
>

Re: [ANNOUNCE] New Apache NiFi Committer Koji Kawamura

[Koji Kawamura]

Thanks everyone! I'll keep trying my best to develop the great tool
with this great community!

Koji

On Wed, Jul 20, 2016 at 6:43 PM, Pierre Villard
 wrote:
> Congrats Koji!
>
> Pierre
>
> 2016-07-20 3:16 GMT+02:00 Joe Percivall :
>
>>  Congrats Koji! - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
>> joeperciv...@yahoo.com
>>
>>
>> On Tuesday, July 19, 2016 9:13 PM, Oleg Zhurakousky <
>> ozhurakou...@hortonworks.com> wrote:
>>
>>
>>  Congrats Koji!
>> Glad to see you on board!
>>
>> Oleg
>> On Jul 19, 2016, at 7:45 PM, Andy LoPresto  alopre...@apache.org>> wrote:
>>
>> Congratulations Koji. Excited for even more great contributions.
>>
>> Andy LoPresto
>> alopre...@apache.org
>> alopresto.apa...@gmail.com
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>>
>> On Jul 19, 2016, at 3:58 PM, Matt Burgess  mattyb...@gmail.com>> wrote:
>>
>> Congratulations and welcome Koji! Your contributions are greatly
>> appreciated and I'm looking forward to more in the future!
>>
>> Regards,
>> Matt
>>
>> On Tue, Jul 19, 2016 at 6:55 PM, Tony Kurc  tk...@apache.org>> wrote:
>> On behalf of the Apache NiFI PMC, I am very pleased to announce that Koji
>> Kawamura has accepted the PMC's invitation to become a committer on the
>> Apache NiFi project. We greatly appreciate all of Koji's hard work and
>> generous contributions and look forward to continued involvement in the
>> project.
>>
>> Koji has been instrumental in couchbase integration, as well improving
>> site-to-site. Welcome and congratulations!
>>
>> Tony
>>
>>
>>
>>
>>

Github write permission

[Koji Kawamura]

Hello team,

I've just become a NiFi committer from today, got so excited.
Thank you for everyone who have been supporting me to made contributions!

I was able to setup my email, ssh, and made my first commit to
nifi-site project today.

However, when I tried to push my commit to the nifi-site on Github, I
got a permission error, while doing so succeeded with Apache Git.
Do I need to ask infra for Github write permission?

Thanks!
Koji

Re: Manage datatypes in nifi

[Bryan Bende]

Hello,

This is more about Solr than NiFi...

The example is using Solr's dynamic field feature where a field name with
"_s" at the end means it is a string. For a date it is "_dt" at the end.

You can see the dynamic field types typically available here:
https://github.com/apache/lucene-solr/blob/67b638880d81fbb11abfbfc1ec93a5f3d86c3d3b/solr/server/solr/configsets/basic_configs/conf/managed-schema#L153

Keep in mind that when using a date type rather than a string, the value of
"created_at" will have to be in a date format that Solr accepts.

-Bryan


On Wed, Jul 20, 2016 at 8:11 AM, Shivadeep Gundoju <
shivadeep.gund...@techwave.net> wrote:

> Hello Team,
>
>  I am new to Nifi  . I have used above link to put twitter tweets to
> solr documents(
> https://blogs.apache.org/nifi/entry/indexing_tweets_with_nifi_and)
>
>  I am stuck with one problem
> I want  twitter_created_at_s:/created_at to be stored as Date
> datatype but this is by default saving it as string in solr document.
> Please help me . how to convert this particular field from string to
> Date ?
>
>
> Thanks in advance
> Shivadeep.G
>
>
>

Manage datatypes in nifi

[Shivadeep Gundoju]

Hello Team,

 I am new to Nifi  . I have used above link to put twitter tweets to solr 
documents(https://blogs.apache.org/nifi/entry/indexing_tweets_with_nifi_and)

 I am stuck with one problem
I want  twitter_created_at_s:/created_at to be stored as Date datatype 
but this is by default saving it as string in solr document.
Please help me . how to convert this particular field from string to Date ?


Thanks in advance
Shivadeep.G

Re: [ANNOUNCE] New Apache NiFi Committer Koji Kawamura

[Pierre Villard]

Congrats Koji!

Pierre

2016-07-20 3:16 GMT+02:00 Joe Percivall :

>  Congrats Koji! - - - - - - Joseph Percivalllinkedin.com/in/Percivalle:
> joeperciv...@yahoo.com
>
>
> On Tuesday, July 19, 2016 9:13 PM, Oleg Zhurakousky <
> ozhurakou...@hortonworks.com> wrote:
>
>
>  Congrats Koji!
> Glad to see you on board!
>
> Oleg
> On Jul 19, 2016, at 7:45 PM, Andy LoPresto > wrote:
>
> Congratulations Koji. Excited for even more great contributions.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jul 19, 2016, at 3:58 PM, Matt Burgess > wrote:
>
> Congratulations and welcome Koji! Your contributions are greatly
> appreciated and I'm looking forward to more in the future!
>
> Regards,
> Matt
>
> On Tue, Jul 19, 2016 at 6:55 PM, Tony Kurc > wrote:
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Koji
> Kawamura has accepted the PMC's invitation to become a committer on the
> Apache NiFi project. We greatly appreciate all of Koji's hard work and
> generous contributions and look forward to continued involvement in the
> project.
>
> Koji has been instrumental in couchbase integration, as well improving
> site-to-site. Welcome and congratulations!
>
> Tony
>
>
>
>
>