@Jaimin7 assuming "gt" is your parameter, that would be referenced as #{gt} and i think would be:   {"updatedAt" : {#{gt} : 2022-12-10}}   If "gt" is your variable, that would be represented as ${gt} and that would then be:   {"updatedAt" : {${gt} : 2022-12-10}}     Preference going forward is to use Paramaters as Variables will be going away soon. ... View more

@hegdemahendra Awesome to see you making custom processors.  A few things that might help:   Make sure this controller service exists in your nifi,  some nifi builds do not include all nars Make sure this controller service exists in your project dependencies That said, you may find more advanced nifi help engaging with the nifi developer community on slack or the mailing list. You can find the slack invite link at the bottom of that page. ... View more

@quangbilly79 The top screen shot is for CDP Public Cloud and the bottom screen shot is for CDP Private Cloud Base.  As such, the CDE (Cloudera Data Engineering) "Schedule Job" is not available in the Cloudera Manager UI.    You could use something like Oozie:   https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/configuring-oozie/topics/oozie-introduction.html     ... View more

@abdebja Have you completed HUE configuration for SSL of each services host(s)?   The docs are as follows:   https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/securing-hue/topics/hue-configuring-tls-ssl.html     ... View more

@Vickey   You will need to investigate the differences in execution from nifi vs hue.   You should be able to see some differences in tez between both queries.   The return code 1 is often due to tez resource availability.    Also, i would suggest that you NOT do anything with retry logic in nifi until you are sure the processor works as expected the first time.   Bringing in the retry logic only hides the issue if it is intermittent.  Sounds like it is consistently not working, so retry is not helpful.  Another suggestion is to turn the process logging level to DEBUG.   Last but not least, in future, try to screen shot your flow, and processor configs so all of us can see more details ... View more

@Griggsy  I would have to have working sample to test and provide better solution, that said i think you need to use function inside of the value, not the property.   There you could also use ifElse making the NiFi Expression language operate for both scenarios.   Chaining expressions together can be a challenge but should get you where you need to go. ... View more

Are you sure the code is the same?   Sounds like the clustered version is kicking off job and its never finishing (endless loop?) or the task is creating some performance or connectivity issue..   Depending on your processor,  it may need to be flagged as Primary Only. ... View more

I believe so.  Were you able to get a token using that user? ... View more