Re: JoltTransformJSON error

Glad it worked out! Let us know if you have any other questions. -yolanda > On Oct 6, 2016, at 3:49 PM, Karthik Ramakrishnan > wrote: > > Hi Yolanda, > > Thanks!! This is working. I guess I added too many specifications in the > spec. Unlike the

Re: SelectHiveQL Error

Andrew is correct. Although the HiveServer 1 driver is included with the NAR, the HiveConnectionPool is hardcoded to use the HiveServer 2 driver (since the former doesn't allow for simultaneous connections and we are using a connection pool :) the scheme should be jdbc:hive2:// not hive. If

Re: Routeonattribute

Hello, I'm not totally sure, but I think this creates two levels of expression language and won't work. Typically the flow file would have an attribute like db.table.name and then in RouteOnAttribute you would define a property like test = ${db.table.name: equals('test')}. -Bryan On Thu, Oct

RE: SelectHiveQL Error

Hi Matt, Here is the whole error trace, starting from when I turned on the SelectHiveQL processor: INFO [StandardProcessScheduler Thread-2] o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled SelectHiveQL[id=0157102a-94da-11ec-0f7e-17fd3119aa00] to run with 1 threads 2016-10-06 15:37:06,554 INFO

Routeonattribute

Hi, can we refer to an attribute from a previous processor for specifying a boolean clause in routeonattribute processor. For Eg. : A flowfile from a previous processor has a attribute called expression with value ${db.table.name:equals('test')} . Can we refer to this ${expression} attribute as

Re: Fetchs3Object

James you are right. we find the solution. thanks for the help. On Fri, Oct 7, 2016 at 12:02 AM, Tseytlin, Keren < keren.tseyt...@capitalone.com> wrote: > Selvam, > > > > For debugging purposes, I would highly recommend trying to use the AWS CLI > to get the file onto whatever machine you are

Re: SelectHiveQL Error

Dan, That is a catch-all error returned when (in case probably) something is misconfigured. Are there more error lines below that in the log? The driver class and all its dependencies are present in the Hive NAR, so there is likely an underlying error that, while being propagated up, returns the

SelectHiveQL Error

Hello, I am trying to use a SelectHiveQL processor using the following controller configuration: Database Connection URL - jdbc:hive://server:port/default Hive Configuration Resources - /path/to/hive/hive-site.xml When my processor goes to run the simple query, I get the following error

Re: JoltTransformJSON error

Matt / Yolanda, Thanks for taking the reply. I just found time to work on this. I removed the array brackets from the spec and changed it to 'shift', but this is the only output I am getting as of now. { "shift": "Update" } I am not getting the entire tree as in the app-demo. Is there

Re: Fetchs3Object

Selvam, Can you describe what is happening when you run FetchS3Object? Does the processor start? Are flowfiles routed to the failure relationship? Are there error messages? To test your configuration, I recommend using ListS3 to get flowfiles with attributes referencing the S3 objects, then