Hi again @spartakus,  Adding more information, as mentioned, natively, it looks like it's not supported.  But here there is a Jira that explains the behavior and some steps they made:  https://issues.apache.org/jira/browse/NIFI-6152  ... View more

Hello @Isuri, Glad to have you on the community and to hear you're pursuing those certifications.  Congrats on CAISP completion.  That looks like an issue with the platform itself. What I would recommend you is to reach our Certification team via email: certification@cloudera.com They should be able to help you more on that question.  ... View more

Thank you @vafs ! Yes, that made the trick. Thanks; -karsten ... View more

Hello @zzzz77, Did the answers help you here?  If so, please consider marking the comment that help you as the solution.  ... View more

Hi @yoonli As per my knowledge Cloudera will not support Standalone setup and supported types are YARN and Kubernetes.  For your error, you need to check kerberos setup for standalone cluster and try to run simple examples like SparkPi and see whether it is working or not. ... View more

@vafsThank you for the detailed information, this fully clarifies the deprecation rationale, possible workarounds, and alternative approaches for gRPC integration in NiFi 2.x! ... View more

@Navaneeth 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.  Thanks. ... View more

Hello @Samya,  Thanks for joining our community.  That issue is happening because JSON_STORE format is VARCHAR(2), not VARIANT as required.  Something you can try is to add a ConvertRecord processor before the PutDatabaseRecord.  There, you can use a JsonTreeReader → JsonRecordSetWriter to reformat the content. In that way, the JSON_STORE field becomes a proper JSON object. Something like this👆 ... View more

Hello @enguias,  Sometimes this error could be for an old algorithm such as SHA-1. And most possible if using Java 11 that is more strict with the policies.  One option is to use connection without TLS, if possible and acceptable in your environment:  jdbc:sqlserver://<host>:<port>;databaseName=<DB>;encrypt=disable Or, update the certificate to SHA-256 with TLS 1.2.  This is the best option if you prefer to maintain the encryption.  Maybe this documentation from SQL can help too:  https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/configure-sql-server-encryption?view=sql-server-ver17  ... View more