@Althotta  NiFi node disconnections are rarely the result of some underlying issue in NiFi code.  Node disconnection are more commonly the result of resource consumption or configurations not being optimal in a NiFi deployment.   This particular post if two years old.  You should create a new post and provide details around your node disconnection issue and the specific Apache NiFi version you are running to get better assistance.  The NiFi cluster UI is a good place to start.  The "view details" icon to the far left for each node will provide you with node events which will include disconnect events along with reason.  Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

Hi @Dan Burkert , i have tried exactly the same DDL and it give the error. I used hue/impala to create the table. Can you help? ParseException: Syntax error in line 4:undefined: RANGE(year, month) ( ^ Encountered: RANGE Expected: CACHED, COMMENT, LOCATION, PARTITION, PARTITIONED, PRODUCED, ROW, SORT, STORED, TBLPROPERTIES, UNCACHED, WITH CAUSED BY: Exception: Syntax error   ... View more

Hello @hebamahmoud  If the issue is has been from any of the above responses, Could you accept it as a solution? Regards, Chethan YM ... View more

if what you provided seems to be giving you the expected output then you are good to go :). ... View more

I have used the below spec for moving some of the resource characterstic to top level but iam getting null values.  [ { "operation": "shift", "spec": { "header": { "timeStamp": "records.inv_activity_ts", "activityId": "records.inv_activity_id", "action": "records.action" }, "resource": { "drniId": "records.inv_id", "subtype": "records.inv_subtype", "name": "records.inv_name", "resourceCharacteristic": { "*": { "name": { "matchingkey": "records.matchingkey-value", "status": "records.status-value" }, "value": { "matchingkey": "records.matchingkey-value", "status": "records.status-value" } } } } } } ]   Output iam getting { "records" : { "inv_activity_ts" : "1670484663189", "inv_activity_id" : "256388257993155783", "action" : "create", "inv_id" : "256383859946641699", "inv_subtype" : "Backplane Connection", "inv_name" : "Backplane Connection", "matchingkey-value" : null, "status-value" : null } }   What is mistake iam making?.  ... View more

I had a similar issue, it happens because of nifi not being able to resolve the schema. You need to first create a schema and set the type of billing address as string and add it to avroschemaregistry and lastly configure your jsontreereader to use that schema ... View more

@Althotta, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.  ... View more

I'm able to fix this .. In JSON Tree READER the configuration for `Schema Access Strategy` should be "Infer Schema" Input date format will be "yyyy-MM-dd HH:mm:ss.SSS'Z'" avro schema for the same will be { "name": "createdAt", "type": { "type": "long", "logicalType": "timestamp-millis" } }   ... View more

I have achieved this using Wait and Noitfy which is working as per my use case. ... View more

@Althotta, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.   ... View more