@pk97 Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution to help others find the answer more easily in the future.  ... View more

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

@zzzz77  When you executed your curl commands, did you check both the nifi-app.log and nifi-user.log for any ERROR or WARN log output that would provide more detail on the exception. The Apache NIFi 2.x Provenance rest-api endpoint request should look more like this: curl 'https://<HOSTNAME>:<PORT>/nifi-api/provenance' \ -H 'accept: application/json, text/plain, */*' \ -H 'content-type: application/json' \ -H 'Authorization:Bearer <TOKEN>' \ --data-raw '{"provenance":{"request":{"incrementalResults":false,"maxResults":1000,"summarize":true}}}' \ --insecure 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

@hckorkmaz01  While you are currently still using Apache NiFi 1.x major release version, it has reached end of life and is no longer receiving contributions.  As such components will not get library updates or security fixes going forward.   Apache NiFi 2.x is currently active major release being contributed to in the community.  The PrometheusReportingTask was deprecated in Apache NiFi 1.x and officially removed in Apache NiFi 2.x major release.   So I would avoid using it as you will eventually need to move to Apache NiFi 2.x to maintain a secure supported product release.  But technically, this reporting task, while not well maintained in the community, is capable of creating a prometheus endpoint which exposes metrics for all components (includes connections) for consumption. That being said, Cloudera has taken steps to create Cloudera versions of many of the deprecated and removed components in Apache NiFi 2.x; as well as, introduced many components not available at all in any Apache release version (PrometheusReportingTask is not one of them that was retained). https://docs.cloudera.com/cfm/4.11.0/nifi-components-cfm/components/ NOTE:  You are already using a considerably older Apache NiFI 1.18 release.  Many bug fixes and CVEs security issues have been addressed since that release.  If you cannot yet move to Apache NiFi 2.x, you should at least be on the most recent release of Apache NIFi 1.28. 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

@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

Thank you very much for trying to help. I’ve been stuck on this subject for the past two weeks, trying to improve queries on Impala. I’m currently on RHEL 9 and have unixODBC installed. I’ve configured my environment via /etc/profile.d/oracle.sh as follows: # Oracle Instant Client configuration export TNS_ADMIN=/opt/oracle/instantclient_12_2/network/admin export PATH=/opt/oracle/instantclient_12_2:$PATH export LD_LIBRARY_PATH=/opt/oracle/instantclient_12_2:/usr/lib64:$LD_LIBRARY_PATH # ODBC configuration export ODBCINI=/etc/odbc.ini export ODBCSYSINI=/etc # Cloudera Impala ODBC configuration export CLOUDERAIMPALAINI=/opt/cloudera/impalaodbc/lib/64/cloudera.impalaodbc.ini I’ve tested with: `isql Impala_KRB14 user password` and it connects successfully, but queries are taking too long. I’m looking for guidance on how to optimize these queries effectively. Here are the version of installed packages: unixODBC 2.3.9 DRIVERS............: /etc/odbcinst.ini SYSTEM DATA SOURCES: /etc/odbc.ini FILE DATA SOURCES..: /etc/ODBCDataSources USER DATA SOURCES..: /etc/odbc.ini SQLULEN Size.......: 8 SQLLEN Size........: 8 SQLSETPOSIROW Size.: 8   rpm -qa | grep cyrus-sasl cyrus-sasl-lib-2.1.27-21.el9.x86_64 cyrus-sasl-gssapi-2.1.27-21.el9.x86_64 cyrus-sasl-plain-2.1.27-21.el9.x86_64 cyrus-sasl-2.1.27-21.el9.x86_64 ... View more

We tried above suggested solution. ie setting "export NLS_LANG="AMERICAN_AMERICA.AL32UTF8" But still we are facing the same issue. ... View more

[test comment, edit] ... View more

@menuka, Welcome to our community! To help you get the best possible answer, I have tagged in our CDP experts @abdulpasithali and @zzeng, who may be able to assist you further. Please feel free to provide any additional information or details about your query, and we hope that you will find a satisfactory solution to your question. ... View more

@Taisia00, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution to aid others in finding the answer more easily in the future.  ... View more