Re: NiFi 1.3 - PublishKafka_0_10 - A message in the stream exceeds the maximum allowed message size of 1048576 bytes

[mayank rathi]

Thanks Koji for replying. After your email I looked into Kafka logs again
and found out that message.max.bytes was setup to accept only 1 MB
messages. I increased this to 10 MB and after that messages are now being
pushed to Kafka.

Thanks for helping !!

On Sun, Nov 19, 2017 at 7:01 PM, Koji Kawamura <ijokaruma...@gmail.com>
wrote:

> Hi Mayank,
>
> I've tried to reproduce the issue, but to no avail so far.
> PublishKafka_0_10 uses the specified Max Request Size as expected and
> I got the exception if incoming message size exceeds the configured
> size.
> And I was able to publish messages whose size is 2.08MB with 10MB Max
> Request Size.
>
> The stacktrace you reported is created within NiFi AbstractDemarcator
> (StreamDemarcator), when it tried to read bytes from incoming FlowFile
> content and read size exceeds maxDataSize.
> StreamDemarcator.maxDataSize is set to the specified PublishKafka_0_10
> 'Max Request Size'.
>
> Does this issue still happen? If so, do you mind sharing your
> processor configuration by exporting as a template?
>
> Thanks,
> Koji
>
>
> On Sat, Nov 18, 2017 at 1:54 AM, mayank rathi <mayank.ra...@gmail.com>
> wrote:
> > Hello All,
> >
> > I am getting this error in PublishKafka_0_10 processor for a message of
> > size 2.08 MB. I have updated Max Request Size to 10 MB in processor
> > properties and max.request.size to 10 MB in Kafka's server.properties.
> > After reboot Kafka Broker I can see that max.request.size = 10 MB in
> Kafka
> > logs but I am still getting below error.
> >
> > What am I missing here?
> >
> > 2017-11-17 11:07:47,966 ERROR [Timer-Driven Process Thread-4]
> > o.a.n.p.kafka.pubsub.PublishKafka_0_10
> > PublishKafka_0_10[id=e6d932d9-97ae-1647-aa8f-86d07791ce25]
> > Failed to send all message for StandardFlowFileRecord[uuid=
> > fa2399e5-bea5-4113-b58b-6cdef228733c,claim=StandardContentClaim
> > [resourceClaim=StandardResourceClaim[id=1510934860019-132,
> > container=default, section=132], offset=0, length=2160613],offset=0,name=
> > 12337127439954063,size=2160613] to Kafka; routing to failure due to
> > org.apache.nifi.stream.io.exception.TokenTooLargeException: A message in
> > the stream exceeds the maximum allowed message size of 1048576 bytes.: {}
> > org.apache.nifi.stream.io.exception.TokenTooLargeException: A message in
> > the stream exceeds the maximum allowed message size of 1048576 bytes.
> > at org.apache.nifi.stream.io.util.AbstractDemarcator.
> extractDataToken(
> > AbstractDemarcator.java:157)
> > at org.apache.nifi.stream.io.util.StreamDemarcator.
> > nextToken(StreamDemarcator.java:129)
> > at org.apache.nifi.processors.kafka.pubsub.PublisherLease.
> > publish(PublisherLease.java:78)
> > at org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_
> > 10$1.process(PublishKafka_0_10.java:334)
> > at org.apache.nifi.controller.repository.
> StandardProcessSession.read(
> > StandardProcessSession.java:2136)
> > at org.apache.nifi.controller.repository.
> StandardProcessSession.read(
> > StandardProcessSession.java:2106)
> > at org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_
> > 10.onTrigger(PublishKafka_0_10.java:330)
> > at org.apache.nifi.processor.AbstractProcessor.onTrigger(
> > AbstractProcessor.java:27)
> > at org.apache.nifi.controller.StandardProcessorNode.onTrigger(
> > StandardProcessorNode.java:1120)
> > at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.
> call(
> > ContinuallyRunProcessorTask.java:147)
> > at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.
> call(
> > ContinuallyRunProcessorTask.java:47)
> > at org.apache.nifi.controller.scheduling.
> TimerDrivenSchedulingAgent$1.
> > run(TimerDrivenSchedulingAgent.java:132)
> > at java.util.concurrent.Executors$RunnableAdapter.
> > call(Executors.java:511)
> > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> > at java.util.concurrent.ScheduledThreadPoolExecutor$
> > ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> > at java.util.concurrent.ScheduledThreadPoolExecutor$
> > ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(
> > ThreadPoolExecutor.java:1142)
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> > ThreadPoolExecutor.java:617)
> > at java.lang.Thread.run(Thread.java:748)
> >
> > Thanks and Regards
> > Mayank
> >
> > --
> > NOTICE: This email message is fo

NiFi 1.3 - PublishKafka_0_10 - A message in the stream exceeds the maximum allowed message size of 1048576 bytes

[mayank rathi]

Hello All,

I am getting this error in PublishKafka_0_10 processor for a message of
size 2.08 MB. I have updated Max Request Size to 10 MB in processor
properties and max.request.size to 10 MB in Kafka's server.properties.
After reboot Kafka Broker I can see that max.request.size = 10 MB in Kafka
logs but I am still getting below error.

What am I missing here?

2017-11-17 11:07:47,966 ERROR [Timer-Driven Process Thread-4]
o.a.n.p.kafka.pubsub.PublishKafka_0_10
PublishKafka_0_10[id=e6d932d9-97ae-1647-aa8f-86d07791ce25]
Failed to send all message for StandardFlowFileRecord[uuid=
fa2399e5-bea5-4113-b58b-6cdef228733c,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1510934860019-132,
container=default, section=132], offset=0, length=2160613],offset=0,name=
12337127439954063,size=2160613] to Kafka; routing to failure due to
org.apache.nifi.stream.io.exception.TokenTooLargeException: A message in
the stream exceeds the maximum allowed message size of 1048576 bytes.: {}
org.apache.nifi.stream.io.exception.TokenTooLargeException: A message in
the stream exceeds the maximum allowed message size of 1048576 bytes.
at org.apache.nifi.stream.io.util.AbstractDemarcator.extractDataToken(
AbstractDemarcator.java:157)
at org.apache.nifi.stream.io.util.StreamDemarcator.
nextToken(StreamDemarcator.java:129)
at org.apache.nifi.processors.kafka.pubsub.PublisherLease.
publish(PublisherLease.java:78)
at org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_
10$1.process(PublishKafka_0_10.java:334)
at org.apache.nifi.controller.repository.StandardProcessSession.read(
StandardProcessSession.java:2136)
at org.apache.nifi.controller.repository.StandardProcessSession.read(
StandardProcessSession.java:2106)
at org.apache.nifi.processors.kafka.pubsub.PublishKafka_0_
10.onTrigger(PublishKafka_0_10.java:330)
at org.apache.nifi.processor.AbstractProcessor.onTrigger(
AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(
StandardProcessorNode.java:1120)
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
ContinuallyRunProcessorTask.java:147)
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
ContinuallyRunProcessorTask.java:47)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.
run(TimerDrivenSchedulingAgent.java:132)
at java.util.concurrent.Executors$RunnableAdapter.
call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$
ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$
ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Thanks and Regards
Mayank

-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

PutSQL: java.sql.BatchUpdateException: invalid batch command

[mayank rathi]

Hello All,

Can someone please help in understanding what I am doing wrong here?

I am passing following values to PutSQL processor

sql.args.1.type
2005

sql.args.1.value
V99|1.0| E99|BILLING|1234567|11049532|350|201706|201709|
R03|350|11049532|4| |KK|174|A|07/27/1948| |322| |0|F| |
|201712|201709|0|168900.56|0|0|0|0|40134|201712|0|0|316| |200402|0| | | | |
| | | | |POPR_CUPDT| | | | | | | | | | | |0|0|2|200402|0| | | |
P03|0|1|0|0|199404|317|201711|08/17/2017| |0|201712|08/22/2017|322|0|
K06|201706|111.53|111.53|14.8|96.73|111.53|15||0|0|
K06|201707|117.48|117.48|15.85|101.63|117.48|15||0|0|
K06|201708|227.98|227.98|44.34|183.64|227.98|30||0|0|

SQL query is:
select obds_loader.getmain(?) from dual

PutSQL processor is throwing below error.

2017-10-12 13:56:39,129 ERROR [Timer-Driven Process Thread-1]
o.apache.nifi.processors.standard.PutSQL
PutSQL[id=0beb1a31-980d-38f9-fc0e-6c0ac7a68984]
Failed to update database due to a failed batch update,
java.sql.BatchUpdateException: invalid batch command. There were a total of
1 FlowFiles that failed, 0 that succeeded, and 0 that were not execute and
will be routed to retry; : java.sql.BatchUpdateException: invalid batch
command
java.sql.BatchUpdateException: invalid batch command
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(
OraclePreparedStatement.java:10358)
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(
OracleStatementWrapper.java:230)
at org.apache.commons.dbcp.DelegatingStatement.executeBatch(
DelegatingStatement.java:297)
at org.apache.commons.dbcp.DelegatingStatement.executeBatch(
DelegatingStatement.java:297)
at org.apache.nifi.processors.standard.PutSQL.lambda$null$
10(PutSQL.java:348)
at org.apache.nifi.processor.util.pattern.ExceptionHandler.
execute(ExceptionHandler.java:127)
at org.apache.nifi.processors.standard.PutSQL.lambda$new$12(
PutSQL.java:346)
at org.apache.nifi.processor.util.pattern.PutGroup.
putFlowFiles(PutGroup.java:94)
at org.apache.nifi.processor.util.pattern.Put.onTrigger(Put.java:101)
at org.apache.nifi.processors.standard.PutSQL.lambda$
onTrigger$20(PutSQL.java:554)
at org.apache.nifi.processor.util.pattern.PartialFunctions.
onTrigger(PartialFunctions.java:114)
at org.apache.nifi.processor.util.pattern.RollbackOnFailure.onTrigger(
RollbackOnFailure.java:184)
at org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:554)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(
StandardProcessorNode.java:1119)
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
ContinuallyRunProcessorTask.java:147)
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
ContinuallyRunProcessorTask.java:47)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.
run(TimerDrivenSchedulingAgent.java:128)
at java.util.concurrent.Executors$RunnableAdapter.
call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$
ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$
ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

Thanks and Regards


-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

Re: [EXT] Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?

[mayank rathi]

Hello All,

How can we find out list of fixes that will go in 1.4.0 release?

Thanks!!

On Wed, Sep 20, 2017 at 9:53 AM, Brandon DeVries  wrote:

> All,
>
> I think we should plan on calling for a vote on Friday.  That gives two
> days to wrap up any outstanding tickets that anyone feels really belong in
> 1.4.  At that point the remaining tickets can be shifted to a future
> release.
>
> If there are tickets that are not getting the attention they need to make
> it into the release, let the list know.
>
> Any objections?
>
> Brandon
>
> On Wed, Sep 20, 2017 at 12:32 AM Koji Kawamura 
> wrote:
>
> > Hi Paul,
> >
> > I was able to reproduce the GenerateTableFetch processor issue
> > reported by NIFI-4395.
> > Please go ahead and provide a PR, I can review it.
> >
> > Thanks,
> > Koji
> >
> > On Wed, Sep 20, 2017 at 1:10 PM, Paul Gibeault (pagibeault)
> >  wrote:
> > > We have submitted this JIRA ticket:
> > > https://issues.apache.org/jira/browse/NIFI-4395
> > >
> > > This issue causes GenerateTableFetch processor to malfunction after a
> > server restart.
> > >
> > > We are very interested in getting this released in 1.4.0 and are
> willing
> > to provide the PR if there is still time.
> > >
> > > Thanks,
> > > Paul Gibeault
> > >
> > >
> > > -Original Message-
> > > From: Michael Hogue [mailto:michael.p.hogu...@gmail.com]
> > > Sent: Tuesday, September 19, 2017 9:36 AM
> > > To: dev@nifi.apache.org
> > > Subject: [EXT] Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?
> > >
> > > All,
> > >
> > >There are a couple of issues with open PRs that i think would be
> > desirable to get into 1.4.0:
> > >
> > >   - https://github.com/apache/nifi/pull/2163 - trivial one-liner in
> > ListenGRPC
> > >   - https://github.com/apache/nifi/pull/1985 - support TLS algorithm
> > selection via SSLContextService in HandleHTTPRequest
> > >
> > > Thanks,
> > > Mike
> > >
> > > On Tue, Sep 19, 2017 at 10:46 AM Mark Bean 
> > wrote:
> > >
> > >> I agree with including only those which can be completed quickly in
> > 1.4.0.
> > >> We are anxious for the next release to begin exercising some of the
> > >> new features. IMO it's time to get 1.4.0 out the door.
> > >>
> > >> Thanks,
> > >> Mark
> > >>
> > >> On Mon, Sep 18, 2017 at 6:59 PM, Jeff  wrote:
> > >>
> > >> > Still good.  Was looking through tickets yesterday and today and
> > >> > while review progress has been made on some PRs, it might be best to
> > >> > move JIRAs tagged for 1.4.0 that have PRs and aren't on the cusp of
> > >> > being committed
> > >> to
> > >> > post 1.4.0.  Thoughts?
> > >> >
> > >> > On Mon, Sep 18, 2017 at 2:50 PM Joe Witt 
> wrote:
> > >> >
> > >> > > Definitely agree with Brandon that due for a 1.4.0 and it has some
> > >> > > really nice things in it
> > >> > >
> > >> > > Jeff Storck volunteered to RM.  Jeff you still good?  Anything I
> > >> > > can
> > >> help
> > >> > > with?
> > >> > >
> > >> > >
> > >> > > Thanks
> > >> > > Joe
> > >> > >
> > >> > > On Mon, Sep 18, 2017 at 2:28 PM, Brandon DeVries 
> > wrote:
> > >> > > > There are significant changes in 1.4.0 that I am actively
> > >> > > > waiting
> > >> on...
> > >> > > >
> > >> > > > On Mon, Sep 18, 2017 at 2:25 PM Russell Bateman <
> > >> r...@windofkeltia.com
> > >> > >
> > >> > > > wrote:
> > >> > > >
> > >> > > >> I don't know. Are we due for a release? Is time-since the
> > >> significant
> > >> > > >> factor in a release cycle or is growing features part of it?
> > >> > > >>
> > >> > > >> 1.3.0 subsists with no bump of the third digit. This is an
> > >> > > >> oddly
> > >> > stable
> > >> > > >> .0 product (though the third digit had somewhat different
> > >> > > >> semantics
> > >> in
> > >> > > >> NiFi 0.x). No bug fixes to 1.3.0 in its roughly 6-month
> history?
> > >> > That's
> > >> > > >> an achievement.
> > >> > > >>
> > >> > > >> If there have been important features worked on and ready to
> > >> > > >> go, by
> > >> > all
> > >> > > >> means, let's have 1.4.0. But if 1.4.0 is little more than
> > >> > > >> 1.3.1,
> > >> let's
> > >> > > >> rethink why we'd do that.
> > >> > > >>
> > >> > > >> Russ
> > >> > > >>
> > >> > > >>
> > >> > > >> On 09/18/2017 12:08 PM, Brandon DeVries wrote:
> > >> > > >> > +1, it seems like we're do for a release.  It's been a week,
> > >> > > >> > +and a
> > >> > > couple
> > >> > > >> > of the mentioned tickets have shown progress... but a number
> > >> > > haven't.  If
> > >> > > >> > no one wants to get them wrapped up, can we put them off to
> > 1.5?
> > >> > > >> >
> > >> > > >> > On Mon, Sep 11, 2017 at 11:39 AM Wes Lawrence <
> > >> > wesleyll...@gmail.com>
> > >> > > >> wrote:
> > >> > > >> >
> > >> > > >> >> I'd also like NIFI-4242 and NIFI-4181 added (or if it's OK,
> > >> > > >> >> I can
> > >> > > label
> > >> > > >> >> their fix versions for 1.4.0. I wasn't sure sure I could do

Re: PutSQL error: java.lang.String cannot be cast to oracle.sql.CLOB

[mayank rathi]

Hello All,

Logged https://issues.apache.org/jira/browse/NIFI-4352 for this issue.

Thanks!!

On Mon, Sep 4, 2017 at 10:23 AM, mayank rathi <mayank.ra...@gmail.com>
wrote:

>
> Hello All,
>
> I am passing sql.args.1.type = 2005 and sql.args.1.value as a CLOB value
> to PutSQL and it is throwing below error. How do I resolve this error?
>
> 2017-09-04 10:17:24,924 INFO [StandardProcessScheduler Thread-5] 
> o.a.n.c.s.TimerDrivenSchedulingAgent
> Scheduled PutSQL[id=69534f73-821e-1782--fabb94fb] to run with 1
> threads
> 2017-09-04 10:17:25,009 ERROR [Timer-Driven Process Thread-4]
> o.apache.nifi.processors.standard.PutSQL 
> PutSQL[id=69534f73-821e-1782--fabb94fb]
> org.apache.nifi.processors.standard.PutSQL$$Lambda$653/696434096@771333e
> failed to process due to org.apache.nifi.processor.exception.ProcessException:
> Failed to process StandardFlowFileRecord[uuid=14895cdd-3eac-4f2a-adae-
> f014526e24b1,claim=StandardContentClaim [resourceClaim=
> StandardResourceClaim[id=1502123289026-125, container=default,
> section=125], offset=71441, length=39],offset=0,name=5936554321553480,size=39]
> due to java.lang.ClassCastException: java.lang.String cannot be cast to
> oracle.sql.CLOB; rolling back session: {}
> org.apache.nifi.processor.exception.ProcessException: Failed to process
> StandardFlowFileRecord[uuid=14895cdd-3eac-4f2a-adae-f014526e24b1,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1502123289026-125,
> container=default, section=125], offset=71441, 
> length=39],offset=0,name=5936554321553480,size=39]
> due to java.lang.ClassCastException: java.lang.String cannot be cast to
> oracle.sql.CLOB
> at org.apache.nifi.processor.util.pattern.ExceptionHandler.
> lambda$createOnGroupError$14(ExceptionHandler.java:226)
> at org.apache.nifi.processor.util.pattern.ExceptionHandler.
> lambda$createOnError$13(ExceptionHandler.java:179)
> at org.apache.nifi.processor.util.pattern.ExceptionHandler$
> OnError.lambda$andThen$11(ExceptionHandler.java:54)
> at org.apache.nifi.processor.util.pattern.ExceptionHandler$
> OnError.lambda$andThen$11(ExceptionHandler.java:54)
> at org.apache.nifi.processor.util.pattern.ExceptionHandler.
> execute(ExceptionHandler.java:148)
> at org.apache.nifi.processors.standard.PutSQL.lambda$new$72(
> PutSQL.java:283)
> at org.apache.nifi.processors.standard.PutSQL.lambda$new$75(
> PutSQL.java:324)
> at org.apache.nifi.processor.util.pattern.PutGroup.
> putFlowFiles(PutGroup.java:91)
> at org.apache.nifi.processor.util.pattern.Put.onTrigger(Put.java:101)
> at org.apache.nifi.processors.standard.PutSQL.lambda$
> onTrigger$86(PutSQL.java:544)
> at org.apache.nifi.processor.util.pattern.PartialFunctions.
> onTrigger(PartialFunctions.java:114)
> at org.apache.nifi.processor.util.pattern.RollbackOnFailure.onTrigger(
> RollbackOnFailure.java:184)
> at org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:544)
> at org.apache.nifi.controller.StandardProcessorNode.onTrigger(
> StandardProcessorNode.java:1120)
> at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> ContinuallyRunProcessorTask.java:147)
> at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> ContinuallyRunProcessorTask.java:47)
> at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(
> TimerDrivenSchedulingAgent.java:132)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast
> to oracle.sql.CLOB
> at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(
> OraclePreparedStatement.java:8874)
> at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(
> OraclePreparedStatement.java:8396)
> at oracle.jdbc.driver.OraclePreparedStatement.setObject(
> OraclePreparedStatement.java:8980)
> at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(
> OraclePreparedStatementWrapper.java:242)
> at org.apache.commons.dbcp.DelegatingPreparedStatement.setObject(
> DelegatingPreparedStatement.java:166)
> at org.apache.commons.dbcp.DelegatingPreparedStatement.setObject(
> DelegatingPreparedSta

Output Port: Port X is invalid because Output Connection for port X is not defined

[mayank rathi]

Hello All,

I dragged an Output Port in canvas inside a Process Group and I am getting
error that - Port X is invalid because Output Connection for port X is not
defined.

What configuration am I missing?
Thanks!!

PutSQL error: java.lang.String cannot be cast to oracle.sql.CLOB

[mayank rathi]

Hello All,

I am passing sql.args.1.type = 2005 and sql.args.1.value as a CLOB value to
PutSQL and it is throwing below error. How do I resolve this error?

2017-09-04 10:17:24,924 INFO [StandardProcessScheduler Thread-5]
o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled
PutSQL[id=69534f73-821e-1782--fabb94fb] to run with 1 threads
2017-09-04 10:17:25,009 ERROR [Timer-Driven Process Thread-4]
o.apache.nifi.processors.standard.PutSQL
PutSQL[id=69534f73-821e-1782--fabb94fb]
org.apache.nifi.processors.standard.PutSQL$$Lambda$653/696434096@771333e
failed to process due to
org.apache.nifi.processor.exception.ProcessException: Failed to process
StandardFlowFileRecord[uuid=14895cdd-3eac-4f2a-adae-f014526e24b1,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1502123289026-125,
container=default, section=125], offset=71441,
length=39],offset=0,name=5936554321553480,size=39] due to
java.lang.ClassCastException: java.lang.String cannot be cast to
oracle.sql.CLOB; rolling back session: {}
org.apache.nifi.processor.exception.ProcessException: Failed to process
StandardFlowFileRecord[uuid=14895cdd-3eac-4f2a-adae-f014526e24b1,claim=StandardContentClaim
[resourceClaim=StandardResourceClaim[id=1502123289026-125,
container=default, section=125], offset=71441,
length=39],offset=0,name=5936554321553480,size=39] due to
java.lang.ClassCastException: java.lang.String cannot be cast to
oracle.sql.CLOB
at
org.apache.nifi.processor.util.pattern.ExceptionHandler.lambda$createOnGroupError$14(ExceptionHandler.java:226)
at
org.apache.nifi.processor.util.pattern.ExceptionHandler.lambda$createOnError$13(ExceptionHandler.java:179)
at
org.apache.nifi.processor.util.pattern.ExceptionHandler$OnError.lambda$andThen$11(ExceptionHandler.java:54)
at
org.apache.nifi.processor.util.pattern.ExceptionHandler$OnError.lambda$andThen$11(ExceptionHandler.java:54)
at
org.apache.nifi.processor.util.pattern.ExceptionHandler.execute(ExceptionHandler.java:148)
at org.apache.nifi.processors.standard.PutSQL.lambda$new$72(PutSQL.java:283)
at org.apache.nifi.processors.standard.PutSQL.lambda$new$75(PutSQL.java:324)
at
org.apache.nifi.processor.util.pattern.PutGroup.putFlowFiles(PutGroup.java:91)
at org.apache.nifi.processor.util.pattern.Put.onTrigger(Put.java:101)
at
org.apache.nifi.processors.standard.PutSQL.lambda$onTrigger$86(PutSQL.java:544)
at
org.apache.nifi.processor.util.pattern.PartialFunctions.onTrigger(PartialFunctions.java:114)
at
org.apache.nifi.processor.util.pattern.RollbackOnFailure.onTrigger(RollbackOnFailure.java:184)
at org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:544)
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1120)
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:147)
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to
oracle.sql.CLOB
at
oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:8874)
at
oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:8396)
at
oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8980)
at
oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:242)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.setObject(DelegatingPreparedStatement.java:166)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.setObject(DelegatingPreparedStatement.java:166)
at org.apache.nifi.processors.standard.PutSQL.setParameter(PutSQL.java:888)
at org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:677)
at
org.apache.nifi.processors.standard.PutSQL.lambda$null$71(PutSQL.java:285)
at
org.apache.nifi.processor.util.pattern.ExceptionHandler.execute(ExceptionHandler.java:127)
... 19 common frames omitted

CLOB in sql.args.N.value

[mayank rathi]

Hello All,

Can I pass a CLOB as sql.args.N.value? Are their any size limitations for
attributes?

Thanks!!

Re: Reg. Nifi Clustering Load Balancing

[mayank rathi]

Does this help?

[image: Inline image 1]

On Tue, Aug 29, 2017 at 11:07 AM, Nishant Gupta 
wrote:

> Hello Sir/Madam,
>
> I need to know how we can implement load balancing and single point access
> to all data producer
>
> I have suppose 100 machines that produce data.(flowfiles)
> That data is sent over HTTP from 100 machines to nifi and that we can
> access using listenHTTP processor in Nifi.(Currently I am able to do that
> for single node Nifi)
> Is there any way to provide 100 machines with a single URL (for all 4-5
> nodes in Nifi Cluster)
>
> Can you please let me know how to achieve it.??
>
> Thanks and Regards,
> Nishant Gupta
>



-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

[NiFi-4290] Re: NiFi 1.4: PublishKafkaRecord_0_10: failed to process due to java.lang.NullPointerException

[mayank rathi]

Hello Joe,

I have added all the details to NiFi-4290. Please let me know if you need
any other information from my side.

Thanks
Mayank

On Sat, Aug 12, 2017 at 12:00 AM, Joe Witt <joe.w...@gmail.com> wrote:

> Thanks for reporting the issue.  It appears the NPE can occur if zero
> records end up getting published and it fails to lookup the schema
> because the message tracker is not yet initialized.
>
> So a couple things:
> 1) Verify the settings being used to lookup the schema.  You can show
> the record reader, writer, and schema registry settings being used for
> that publisher.
> 2) You do not need to SplitAvro before sending it via publish kafka
> record.  Avoiding doing the split beforehand can result in vastly
> superior performance.
>
> Thanks
> Joe
>
> On Fri, Aug 11, 2017 at 8:03 PM, mayank rathi <mayank.ra...@gmail.com>
> wrote:
> > Hello Joe,
> >
> > JIRA logged.
> >
> > https://issues.apache.org/jira/browse/NIFI-4290
> >
> > Thanks!!
> >
> > On Fri, Aug 11, 2017 at 9:48 PM, Joe Witt <joe.w...@gmail.com> wrote:
> >
> >> Hello
> >>
> >> Can you please file a jira and attach the logs to the jira.
> >>
> >> Thanks
> >> Joe
> >>
> >> On Aug 11, 2017 6:23 PM, "mayank rathi" <mayank.ra...@gmail.com> wrote:
> >>
> >> > Attached are the logs after setting processors in Debug mode. Here is
> the
> >> > flow:
> >> >
> >> > ExecuteSQL --> SplitAvro --> PublishKafkaRecord_0_10
> >> >
> >> > Thanks!!
> >> >
> >> > On Fri, Aug 11, 2017 at 9:01 PM, mayank rathi <mayank.ra...@gmail.com
> >
> >> > wrote:
> >> >
> >> >> Hello All,
> >> >>
> >> >> I am moving data to Kafka using NiFi's PublishKafkaRecord processor.
> I
> >> am
> >> >> using ConfluentSchemaRegistry Controller service and getting below
> >> error:
> >> >>
> >> >> 2017-08-11 20:54:25,937 ERROR [Timer-Driven Process Thread-4]
> >> >> o.a.n.p.k.pubsub.PublishKafkaRecord_0_10
> PublishKafkaRecord_0_10[id=b3c
> >> >> 03961-015d-1000-0946-79ccbe2ffbbd] PublishKafkaRecord_0_10[id=b3c
> >> >> 03961-015d-1000-0946-79ccbe2ffbbd] failed to process due to
> >> >> java.lang.NullPointerException; rolling back session: {}
> >> >> java.lang.NullPointerException: null
> >> >>
> >> >> I do not see any error on Kafka side.
> >> >>
> >> >> How can I debug and resolve this issue?
> >> >>
> >> >> Thanks!!
> >> >>
> >> >> --
> >> >> NOTICE: This email message is for the sole use of the intended
> >> >> recipient(s) and may contain confidential and privileged information.
> >> Any
> >> >> unauthorized review, use, disclosure or distribution is prohibited.
> If
> >> you
> >> >> are not the intended recipient, please contact the sender by reply
> email
> >> >> and destroy all copies of the original message.
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > NOTICE: This email message is for the sole use of the intended
> >> > recipient(s) and may contain confidential and privileged information.
> Any
> >> > unauthorized review, use, disclosure or distribution is prohibited. If
> >> you
> >> > are not the intended recipient, please contact the sender by reply
> email
> >> > and destroy all copies of the original message.
> >> >
> >>
> >
> >
> >
> > --
> > NOTICE: This email message is for the sole use of the intended
> recipient(s)
> > and may contain confidential and privileged information. Any unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not the
> > intended recipient, please contact the sender by reply email and destroy
> > all copies of the original message.
>



-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

Re: NiFi 1.4: PublishKafkaRecord_0_10: failed to process due to java.lang.NullPointerException

[mayank rathi]

Hello Joe,

JIRA logged.

https://issues.apache.org/jira/browse/NIFI-4290

Thanks!!

On Fri, Aug 11, 2017 at 9:48 PM, Joe Witt <joe.w...@gmail.com> wrote:

> Hello
>
> Can you please file a jira and attach the logs to the jira.
>
> Thanks
> Joe
>
> On Aug 11, 2017 6:23 PM, "mayank rathi" <mayank.ra...@gmail.com> wrote:
>
> > Attached are the logs after setting processors in Debug mode. Here is the
> > flow:
> >
> > ExecuteSQL --> SplitAvro --> PublishKafkaRecord_0_10
> >
> > Thanks!!
> >
> > On Fri, Aug 11, 2017 at 9:01 PM, mayank rathi <mayank.ra...@gmail.com>
> > wrote:
> >
> >> Hello All,
> >>
> >> I am moving data to Kafka using NiFi's PublishKafkaRecord processor. I
> am
> >> using ConfluentSchemaRegistry Controller service and getting below
> error:
> >>
> >> 2017-08-11 20:54:25,937 ERROR [Timer-Driven Process Thread-4]
> >> o.a.n.p.k.pubsub.PublishKafkaRecord_0_10 PublishKafkaRecord_0_10[id=b3c
> >> 03961-015d-1000-0946-79ccbe2ffbbd] PublishKafkaRecord_0_10[id=b3c
> >> 03961-015d-1000-0946-79ccbe2ffbbd] failed to process due to
> >> java.lang.NullPointerException; rolling back session: {}
> >> java.lang.NullPointerException: null
> >>
> >> I do not see any error on Kafka side.
> >>
> >> How can I debug and resolve this issue?
> >>
> >> Thanks!!
> >>
> >> --
> >> NOTICE: This email message is for the sole use of the intended
> >> recipient(s) and may contain confidential and privileged information.
> Any
> >> unauthorized review, use, disclosure or distribution is prohibited. If
> you
> >> are not the intended recipient, please contact the sender by reply email
> >> and destroy all copies of the original message.
> >>
> >
> >
> >
> > --
> > NOTICE: This email message is for the sole use of the intended
> > recipient(s) and may contain confidential and privileged information. Any
> > unauthorized review, use, disclosure or distribution is prohibited. If
> you
> > are not the intended recipient, please contact the sender by reply email
> > and destroy all copies of the original message.
> >
>



-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

Re: NiFi 1.4: PublishKafkaRecord_0_10: failed to process due to java.lang.NullPointerException

[mayank rathi]

Attached are the logs after setting processors in Debug mode. Here is the
flow:

ExecuteSQL --> SplitAvro --> PublishKafkaRecord_0_10

Thanks!!

On Fri, Aug 11, 2017 at 9:01 PM, mayank rathi <mayank.ra...@gmail.com>
wrote:

> Hello All,
>
> I am moving data to Kafka using NiFi's PublishKafkaRecord processor. I am
> using ConfluentSchemaRegistry Controller service and getting below error:
>
> 2017-08-11 20:54:25,937 ERROR [Timer-Driven Process Thread-4]
> o.a.n.p.k.pubsub.PublishKafkaRecord_0_10 PublishKafkaRecord_0_10[id=
> b3c03961-015d-1000-0946-79ccbe2ffbbd] PublishKafkaRecord_0_10[id=
> b3c03961-015d-1000-0946-79ccbe2ffbbd] failed to process due to 
> java.lang.NullPointerException;
> rolling back session: {}
> java.lang.NullPointerException: null
>
> I do not see any error on Kafka side.
>
> How can I debug and resolve this issue?
>
> Thanks!!
>
> --
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited. If you
> are not the intended recipient, please contact the sender by reply email
> and destroy all copies of the original message.
>



-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

NiFi 1.4: PublishKafkaRecord_0_10: failed to process due to java.lang.NullPointerException

[mayank rathi]

Hello All,

I am moving data to Kafka using NiFi's PublishKafkaRecord processor. I am
using ConfluentSchemaRegistry Controller service and getting below error:

2017-08-11 20:54:25,937 ERROR [Timer-Driven Process Thread-4]
o.a.n.p.k.pubsub.PublishKafkaRecord_0_10
PublishKafkaRecord_0_10[id=b3c03961-015d-1000-0946-79ccbe2ffbbd]
PublishKafkaRecord_0_10[id=b3c03961-015d-1000-0946-79ccbe2ffbbd] failed to
process due to java.lang.NullPointerException; rolling back session: {}
java.lang.NullPointerException: null

I do not see any error on Kafka side.

How can I debug and resolve this issue?

Thanks!!

-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

Re: NiFi 1.4 release date?

[mayank rathi]

Hello Joe,

I am interested in using ConfluentSchemaRegistry in NiFi-Kafka integration.

https://issues.apache.org/jira/browse/NIFI-1763

Do you have any timeframe in mind for 1.4 release?  2,4, 6 months etc.?
Is their any way to integrate ConfluentSchemaRegistry with 1.3 version?
Perhaps by copying ConfluentSchemaRegistry NAR files to 1.3 directories and
updating pom.xml.


Thanks!!

On Sat, Aug 5, 2017 at 10:11 PM, Joe Witt <joe.w...@gmail.com> wrote:

> Hello
>
> No specific date set but it is probably a good time to start pulling it
> together.  What is in there you are looking for?
>
> Thanks
>
> On Sat, Aug 5, 2017 at 6:52 PM mayank rathi <mayank.ra...@gmail.com>
> wrote:
>
> > Hello All,
> >
> > What's the tentative release date for NiFi 1.4?
> >
> > Thanks!!
> >
> > --
> > NOTICE: This email message is for the sole use of the intended
> recipient(s)
> > and may contain confidential and privileged information. Any unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not the
> > intended recipient, please contact the sender by reply email and destroy
> > all copies of the original message.
> >
>



-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

NiFi 1.4 release date?

[mayank rathi]

Hello All,

What's the tentative release date for NiFi 1.4?

Thanks!!

-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

Re: NiFi 1.4.0-SNAPSHOT build failing

[mayank rathi]

Thanks Andy for helping. I ran maven with `-DskipTests`and install went
fine.

On Fri, Aug 4, 2017 at 6:56 PM, Andy LoPresto <alopre...@apache.org> wrote:

> Hi,
>
> Sorry you are encountering this issue. I am unable to reproduce this issue
> locally. Do you have a Tomcat/Catalina instance running at the same time on
> your machine? A brief search of the internet for this issue reveals that it
> seems to be caused by container settings (I haven’t found any references to
> this occurring in unit tests, only in deployed applications).
>
> I would also recommend running `mvn clean` to ensure that everything is
> getting built with the proper dependencies, and potentially even cleaning
> out your `~/.m2/` repository (start with just the grpc dependencies) if
> that doesn’t work.
>
> We can continue trying to debug, but if you just want NiFi up and running
> immediately, you can also run maven with `-DskipTests` to avoid this right
> now.
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Aug 4, 2017, at 1:38 PM, mayank rathi <mayank.ra...@gmail.com> wrote:
>
> Hello All,
>
> I am trying to build NiFi 1.4.0-SNAPSHOT from Git and I am getting below
> error. Does anyone know how to resolve this error?
>
> Thanks in advance !!
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
> project nifi-grpc-processors: There are test failures.
> [ERROR]
> [ERROR] Please refer to
> /opt/nifi-master/nifi-nar-bundles/nifi-grpc-bundle/nifi-
> grpc-processors/target/surefire-reports
> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
>
>
> Running org.apache.nifi.processors.grpc.TestInvokeGRPC
> Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.726 sec
> <<< FAILURE! - in org.apache.nifi.processors.grpc.TestInvokeGRPC
> testSecureOneWaySsl(org.apache.nifi.processors.grpc.TestInvokeGRPC)  Time
> elapsed: 0.747 sec  <<< ERROR!
> java.lang.IllegalArgumentException: Jetty ALPN/NPN has not been properly
> configured.
>at
> io.grpc.netty.GrpcSslContexts.selectApplicationProtocolConfi
> g(GrpcSslContexts.java:174)
>at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.
> java:151)
>at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.
> java:139)
>at
> org.apache.nifi.processors.grpc.TestGRPCServer.start(
> TestGRPCServer.java:130)
>at
> org.apache.nifi.processors.grpc.TestInvokeGRPC.testSecureOneWaySsl(
> TestInvokeGRPC.java:464)
>
> testSecureTwoWaySsl(org.apache.nifi.processors.grpc.TestInvokeGRPC)  Time
> elapsed: 0.018 sec  <<< ERROR!
> java.lang.IllegalArgumentException: Jetty ALPN/NPN has not been properly
> configured.
>at
> io.grpc.netty.GrpcSslContexts.selectApplicationProtocolConfi
> g(GrpcSslContexts.java:174)
>at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.
> java:151)
>at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.
> java:139)
>at
> org.apache.nifi.processors.grpc.TestGRPCServer.start(
> TestGRPCServer.java:130)
>at
> org.apache.nifi.processors.grpc.TestInvokeGRPC.testSecureTwoWaySsl(
> TestInvokeGRPC.java:420)
>
>
> --
> NOTICE: This email message is for the sole use of the intended recipient(s)
> and may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply email and destroy
> all copies of the original message.
>
>
>


-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

NiFi 1.4.0-SNAPSHOT build failing

[mayank rathi]

Hello All,

I am trying to build NiFi 1.4.0-SNAPSHOT from Git and I am getting below
error. Does anyone know how to resolve this error?

Thanks in advance !!

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.18:test (default-test) on
project nifi-grpc-processors: There are test failures.
[ERROR]
[ERROR] Please refer to
/opt/nifi-master/nifi-nar-bundles/nifi-grpc-bundle/nifi-grpc-processors/target/surefire-reports
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]


Running org.apache.nifi.processors.grpc.TestInvokeGRPC
Tests run: 12, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.726 sec
<<< FAILURE! - in org.apache.nifi.processors.grpc.TestInvokeGRPC
testSecureOneWaySsl(org.apache.nifi.processors.grpc.TestInvokeGRPC)  Time
elapsed: 0.747 sec  <<< ERROR!
java.lang.IllegalArgumentException: Jetty ALPN/NPN has not been properly
configured.
at
io.grpc.netty.GrpcSslContexts.selectApplicationProtocolConfig(GrpcSslContexts.java:174)
at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.java:151)
at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.java:139)
at
org.apache.nifi.processors.grpc.TestGRPCServer.start(TestGRPCServer.java:130)
at
org.apache.nifi.processors.grpc.TestInvokeGRPC.testSecureOneWaySsl(TestInvokeGRPC.java:464)

testSecureTwoWaySsl(org.apache.nifi.processors.grpc.TestInvokeGRPC)  Time
elapsed: 0.018 sec  <<< ERROR!
java.lang.IllegalArgumentException: Jetty ALPN/NPN has not been properly
configured.
at
io.grpc.netty.GrpcSslContexts.selectApplicationProtocolConfig(GrpcSslContexts.java:174)
at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.java:151)
at io.grpc.netty.GrpcSslContexts.configure(GrpcSslContexts.java:139)
at
org.apache.nifi.processors.grpc.TestGRPCServer.start(TestGRPCServer.java:130)
at
org.apache.nifi.processors.grpc.TestInvokeGRPC.testSecureTwoWaySsl(TestInvokeGRPC.java:420)


-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.

Re: How to add headers to CSV file

[mayank rathi]

Thanks Mark. I am almost there.

Text in Flow file: ZYZTF9y wrote:

> Hello,
>
> You should be able to do this with ReplaceText, using a Replacement
> Strategy
> of Prepend. The Replacement Value would then be the header that you want
> to add to the
> beginning of the file.
>
> Thanks
> -Mark
>
>
> > On Aug 2, 2017, at 3:36 AM, mayank rathi <mayank.ra...@gmail.com> wrote:
> >
> > Hello All,
> >
> > I am working on a NiFi flow to read data from a database and dump it
> into a
> > CSV file.
> >
> > I will use ExecuteSQL to read data and PutFile to generate CSV file.
> >
> > Which processor can I use to add header to this CSV file?
> >
> > Thanks in advance
> > MR
> >
> > --
> > NOTICE: This email message is for the sole use of the intended
> recipient(s)
> > and may contain confidential and privileged information. Any unauthorized
> > review, use, disclosure or distribution is prohibited. If you are not the
> > intended recipient, please contact the sender by reply email and destroy
> > all copies of the original message.
>
>


-- 
NOTICE: This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply email and destroy
all copies of the original message.