Re: FetchParquet Type Conversion Error

will do, thx On Thu, Jun 28, 2018 at 8:25 PM, Bryan Bende wrote: > Joe, > > There was a similar issue I worked on recently that had to do with array > handling: > https://issues.apache.org/jira/browse/NIFI-5316 > > From a quick glance this may be a different variation of a similar issue. > > We

Re: FetchParquet Type Conversion Error

Joe, There was a similar issue I worked on recently that had to do with array handling: https://issues.apache.org/jira/browse/NIFI-5316 From a quick glance this may be a different variation of a similar issue. We are using Parquet’s Java API

Re: FetchParquet Type Conversion Error

*list*-*un*subscr...@apache.org On Thu, Jun 28, 2018 at 7:49 PM Joe Trite wrote: > Greetings, I'm using NiFi 1.6 trying to ListHDFS -> FetchParquet. I'm > seeing the below error on the fetch side. Are there any limitations with > FetchParquet data type conversions? I am able to cat/dump the

FetchParquet Type Conversion Error

Greetings, I'm using NiFi 1.6 trying to ListHDFS -> FetchParquet. I'm seeing the below error on the fetch side. Are there any limitations with FetchParquet data type conversions? I am able to cat/dump the file with parquet-tools and load/query the data in Spark so believe the files are

RE: Checking out specific branch of nifi

That was fast! Thank you Kevin. From: Kevin Doran [mailto:kdo...@apache.org] Sent: Thursday, June 28, 2018 12:00 PM To: users@nifi.apache.org Subject: Re: Checking out specific branch of nifi Hi Vitaly, All releases are tagged as “rel/”, so you can see all tags by running “git tag” and then use

Re: Checking out specific branch of nifi

Hi Vitaly, All releases are tagged as “rel/”, so you can see all tags by running “git tag” and then use “git checkout ” to checkout the version you want. Cheers, Kevin From: Vitaly Krivoy Reply-To: Date: Thursday, June 28, 2018 at 11:54 To: "users@nifi.apache.org" Subject: Checking out

Checking out specific branch of nifi

If I do "git checkout master", that would check out the next version of nifi which is 1.7 How do I check out current version 1.6? I don't see it when I list all branches. Thanks. Vitaly Krivoy STATEMENT OF CONFIDENTIALITY The information contained in this email message and any attachments

Re: simple JMS pub-sub not working

Thanks Kelsey. So it appears that when using RabbitMQ, it's attempting to access the RabbitMQ classes in a call from the ConsumeJMS processor, not from within the ConnectionFactory. I think we may end up needing to include a new property in ConsumeJMS / PublishJMS that optionally allow you to

Re: NiFi 1.6.0 - PutMongo Updates with $set

There's also a (can't remember the name) processor or two that generates SQL operations. Something like that for Mongo would be appropriate. The question is how to approach that because you might want to do multiple operations in the same query. Expressing that in the processor UI could

RE: simple JMS pub-sub not working

Hello Mark, Here you go: 2018-06-28 15:47:27,161 ERROR [Timer-Driven Process Thread-9] o.apache.nifi.jms.processors.ConsumeJMS ConsumeJMS[id=01641047-1441-10a4-ce22-23d392689dd9] ConsumeJMS[id=01641047-1441-10a4-ce22-23d392689dd9] failed to process session due to

Re: NiFi 1.6.0 - PutMongo Updates with $set

So you want to set state not data. On June 27, 2018 at 23:32:48, Ryan Hendrickson ( ryan.andrew.hendrick...@gmail.com) wrote: What we've got is a bunch of custom NiFi processors that are processing data. As the data is processed, we currently use Spring to load up a DAO to access Mongo and

simple JMS pub-sub not working

Hello again, I'm trying to set up a very simple round-trip JMS test. I have a RabbitMQ server set up and installed locally. I set up a simple NiFi flow that generates a FlowFile and uses PublishJMS to send it to the queue. I then have a ConsumeJMS processor that tries to consume what I just

Re: Issues with ExecuteSQL and DBCPConnectionPool service in NiFi

Paul, We use Apache DBCP to pool the connections, and one of its major features is to keep connections open for reuse, to avoid the overhead of establishing new connections (and shutting them down) quickly. In your case you are not creating/closing them quickly but rather every 5 mins. If they

Re: Issues with ExecuteSQL and DBCPConnectionPool service in NiFi

Hello NiFi Team, Can you provide any guidance on ExecuteSQL in combination with DBCPConnectionPool controller service not releasing connections to a remote database after a successful query? Is this intended behavior, a mis-configuration on our end, or a bug? We have a workaround as mentioned