@ckumar yes I have - the username and passwords are correct. ... View more

Hi @DennisJaheruddi    I managed to speak to some devs on Slack and we found a related issue, posted below.   https://issues.apache.org/jira/projects/NIFI/issues/NIFI-8749   Hopefully it gets fixed soon so that we can upgrade to 1.14.0 +  ... View more

Hi @DennisJaheruddi    Unfortunately seems I cannot access the support ticket area - not enough privileges.   All I need to know if this is a bug (in which case I stay with 1.12.1) or if this is a new "feature" in which case I need to update all my flows when upgrading to 1.14.0.     ... View more

Is there any way to reach the Devs to know if this is intentional or not?   I need to upgrade a bunch of servers from 1.12.2 to 1.14.0, but I also need to know if we first have to add a bunch of processors to deal with this timezone change from PutDatabaseRecord. ... View more

My data source is not QueryDatabaseTable, it is json received from another source. Do I need to convert JSON to AVRO now before using PutDatabaseRecord?   Also, if I do add a new ConvertRecord processor for every PutDatabaseRecord I have, these do not have the "Use Avro Logical Types: TRUE" option either. ... View more

The only fix I've found so far is to update the Record Reader of this processor: * Make sure it is not inferred * Write the schema with the order of the record fields matching the order of the table fields.   I'm not sure if there was a reason this was changed or of this is a bug? ... View more

Did you find a fix? Just upgraded from 1.12.2 to 1.13.2 and got a lot of these errors.   PutDatabaseRecord[id=af45e8dc-985b-3f7a-5959-539aa4e7fe9d] Failed to put Records to database for StandardFlowFileRecord[uuid=a398eafb-1fba-441c-81bc-c50509b74ed4,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1626097496241-29, container=default, section=29], offset=171430, length=172],offset=0,name=a398eafb-1fba-441c-81bc-c50509b74ed4,size=172]. Routing to failure.: Operand type clash: int is incompatible with datetime2 PutDatabaseRecord[id=08642c9d-0ce6-3277-79ec-fd5dc8990ba9] Failed to put Records to database for StandardFlowFileRecord[uuid=47f06505-9a47-40c2-b708-21c76466a555,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1626097496241-29, container=default, section=29], offset=174092, length=433],offset=0,name=50e9f73b-c3ee-4d22-8bde-4c2ec306400a,size=433]. Routing to failure.: For input string: "nifi2" PutDatabaseRecord[id=3287e964-c2fb-3cff-345a-d0c11af60271] Failed to put Records to database for StandardFlowFileRecord[uuid=5d060b61-93ef-497b-983c-ef51596202cd,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1626097434922-28, container=default, section=28], offset=683211, length=377],offset=0,name=177de348-4f8c-4ce1-b450-c0eb45b51c9e,size=377]. Routing to failure.: The conversion from String to DECIMAL is unsupported. An exact copy of this flow on 1.12.2 works perfectly well.   ... View more

Just to add to the above, I am getting a lot of the below errors. All the devices sending data via http POSTS are on cellular networks with some having bad signal. Could this be causing the difference between posts the HandleHttpRequest processor receives vs the amount of flowfiles it creates?   ERROR POST from HandleHttpRequest[id=da9f6288-5359-38e9-cb70-1c832b186f63] Failed to receive content from HTTP Request from 10.0.2.2 due to java.util.concurrent.TimeoutException: Idle timeout expired: 60000/60000 ms: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 60000/60000 ms   Sorry about the bump but I'm really struggling to get to the bottom of this. ... View more