@Vikas-Nifi  @ckumar is 100% correct.  Only fields explicitly marked as supporting NiFi Expression Language (NEL) can support a NEL expression "${schedule}". I am however curious about your use case as to why you would even being trying to do this.  From what you shared you are extracting a cron schedule from the json content of some FlowFiles traversing an EvaluateJsonPath processor.  That "schedule" is added on to the NiFi FlowFile as a FlowFile attribute (key=value pair).   This would not make that key=value pair accessible to any other NiFi component unless that FlowFile containing the FlowFile attribute was processed by that other component.   However, in your shared dataflow you do not mention that EvaluateJsonPath connects to your invokeHTTP processor via an inbound dataflow connection (Keep in mind that even if you did do this, it does not change the fact that the run schedule property does not support NEL).   I just wanted to clarify how FlowFile attributes are and can be used. Also keep in mind that the "run schedule" is a scheduler only.  The run schedule set on a processor controls when the NiFi controller will schedule the execution of the processors code.  It does not mean that they the processor will immediately execute at time of scheduling (It may be delayed on execution waiting for an available execution thread from the thread pool).  All scheduled components share a thread pool and NiFi framework will also handle assigning threads to next scheduled component as thread become available.  So the NiFi framework needs to know the scheduling for a component when it is started; otherwise, NiFi would never know when to schedule it to execute.   Unless a component property has an explicit tool tip that tells you it support NEL, then it does not.  For NiFi processor components, you will find that only some processor specific properties within the "PROPERTIES" tab support NEL.  This is not only available through property tooltips, but also in the processors documentation. Examples: Even when NEL is supported there is a scope.  It may support FlowFile attributes, Variable Registry (going away in NiFi 2.x releases), or both.  Thank you,  Matt ... View more

yes I think that was the issue. I am still new to Nifi and slowly learning to work with it. Thank you @ckumar  ... View more

Thank you @MattWho   Your recommendation worked for me. I have updated bootstrap.conf file in nifi.  Was able to successfully enable DB controller service and persist data into Ignite database from Nifi. Details: Copied jvm parameters available in the file \apache-ignite-2.16.0-bin\bin\include\jvmdefaults.sh to \nifi-2.0.0-M2\conf\bootstrap.conf file Here is the format and exact list of java arguments added in nifi bootstrap java.arg.21=--add-opens=java.base/jdk.internal.access=ALL-UNNAMED java.arg.22=--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED java.arg.23=--add-opens=java.base/sun.nio.ch=ALL-UNNAMED java.arg.24=--add-opens=java.base/sun.util.calendar=ALL-UNNAMED java.arg.25=--add-opens=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED java.arg.26=--add-opens=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED java.arg.27=--add-opens=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED java.arg.28=--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED java.arg.29=--add-opens=java.base/java.io=ALL-UNNAMED java.arg.30=--add-opens=java.base/java.nio=ALL-UNNAMED java.arg.31=--add-opens=java.base/java.net=ALL-UNNAMED java.arg.32=--add-opens=java.base/java.util=ALL-UNNAMED java.arg.33=--add-opens=java.base/java.util.concurrent=ALL-UNNAMED java.arg.34=--add-opens=java.base/java.util.concurrent.locks=ALL-UNNAMED java.arg.35=--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED java.arg.36=--add-opens=java.base/java.lang=ALL-UNNAMED java.arg.37=--add-opens=java.base/java.lang.invoke=ALL-UNNAMED java.arg.38=--add-opens=java.base/java.math=ALL-UNNAMED java.arg.39=--add-opens=java.sql/java.sql=ALL-UNNAMED java.arg.40=--add-opens=java.base/java.lang.reflect=ALL-UNNAMED java.arg.41=--add-opens=java.base/java.time=ALL-UNNAMED java.arg.42=--add-opens=java.base/java.text=ALL-UNNAMED java.arg.43=--add-opens=java.management/sun.management=ALL-UNNAMED java.arg.44=--add-opens=java.desktop/java.awt.font=ALL-UNNAMED We just need to make sure java.arg.<>  numbers are unused in the bootstrap file that we are working on. Thanks again! ... View more

I agree with ckumar's point and there is one more thing you could do if it makes you feel safer. You could put the HadoopConfigurationResources file path string into a sensitive parameter and refer to the that parameter (using #{paramname}) in the HiveCatalogService property. ... View more

Do you see any exceptions in the logs before you see the Initiating shutdown of Jetty web server?  ... View more

Load the data into NiFi in an iterative manner, for this you can evaluate GenerateTableFetch -->ExecuteSQL. Loading a large table in one go with ExecuteSQL could result in high heap usage. on the other side, CPU usage is high due to running too many parallelism by increasing the processor concurrent task from default 1 to 8 which is not required.  Thank you ... View more

Hi @Ytch , The way I was able to get to work is through the following instruction: 1- After you have download the jdbc drive from here: https://learn.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-ver15 you should be able to find the following dll "mssql-jdbc_auth-8.2.2.x64.dll" under the path: ..\sqljdbc_8.2\enu\auth\x64 2- Copy the dll and place under the JAVA Home path bin folder: .. \Java\jdk-21\bin 3- Adjust the DB Connection URL in the DBCPconnectionpool  controller service by adding and setting "integrated security"  flag to true: jdbc:sqlserver://{SQL SEVER NAME};databaseName={DB NAme};integratedSecurity=true; 4- Restart Nifi If that helps please accept solution. Thanks   ... View more

Can you please try these two  NIFI_JVM_HEAP_INIT NIFI_JVM_HEAP_MAX   Thank you  ... View more