Member since
06-26-2015
515
Posts
140
Kudos Received
114
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2586 | 09-20-2022 03:33 PM | |
| 6988 | 09-19-2022 04:47 PM | |
| 3691 | 09-11-2022 05:01 PM | |
| 4304 | 09-06-2022 02:23 PM | |
| 6817 | 09-06-2022 04:30 AM |
03-21-2022
11:22 PM
1 Kudo
@pandu2022 , Understood. Just keep in mind that not knowing any details makes it more difficult to help. What's your Kerberos KDC? (AD, MIT, FreeIPA, or other) When you changed the Impala principal name, did you create the new principal in Kerberos? You need to make sure that all the principals "impala_test/<host>" exist in the KDC for all the hosts. Did you regenerate the keytabs for all the Impala Daemons, Catalog and State Store with the new principal name? Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
03-21-2022
11:16 PM
Hi @dmorvant , The QueryDatabaseTableRecord processor is probably not the processor that you need. The main objective of this processor it to periodically query the same table looking for recent records added to the table that need to be ingested. Rather than triggered by an incoming flowfile, this processor is typically scheduled to run at regular intervals. It's also a stateful processor, which records the last record seen in the configured table. If you were able to change the configured database where it was looking for the table, it could confuse the processor and generate unexpected results. I believe that the processor that you're looking for is the ExecuteSQLRecord. This processor receives a flowfile with a SQL query and executes the query against the configured DBCP. If using DBCPConnectionPoolLookup, you can add a "database.name" attribute to the incoming flowfile to do what you want. If this is not what you need, it would help to understand what's your end goal so that we can thing of other ways to do what you need. Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
03-21-2022
08:52 PM
Did you change this configuration in Cloudera Manager? Can you share screenshots of your configuration? André
... View more
03-21-2022
03:23 PM
@Katja , I'm not totally sure but it may be possible that bind variables are accepted inside WITH clauses. Would you be able to try the alternative below? With variable1 as
(
SELECT orders.order_id, orders.order_date
FROM quest_stage.orders orders
)
Select *
from variable1
WHERE order_date = (CAST(? AS TIMESTAMP)) Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
03-21-2022
03:19 PM
@asomrak , Please have a look at the individual nodes and look for a directory called /tmp/scm_prepare_node.* Inside that directory there should be a log file called scm_prepare_node.log, which could tell you more about the error. If you can't figure out the root cause from that log's content, please share the file here so that we can take a look. Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
03-21-2022
03:12 PM
1 Kudo
@RobinRo , Yes, it does support other names. "cdsw" is just an example, but you can replace it with your preferred string. Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
03-21-2022
03:07 PM
@Tra , Could you please explains what your configuration is and which steps you executed to get to this point? Cheers, André
... View more
03-21-2022
03:05 PM
1 Kudo
@BerniHacker , I noticed that your JDBC URL starts with "jdbc:postgres:". The correct is "jdbc:postgresql:". Could you please make this change and try again? Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
03-21-2022
02:54 PM
1 Kudo
@pandu2022 , Where did you configure the customized service name for Impala? Did you configure this since Impala was installed or was it initially using the default name and you later changed it? Cheers, André
... View more
03-17-2022
02:33 PM
1 Kudo
Hi @Tra , When you start NiFi in cluster mode (no-standalone), besides configuring ZooKeeper properties in nifi.properties you also need to configure it for State Management in the conf/state-management.xml file. Make sure your zk-provider in that file looks like the example below: <cluster-provider>
<id>zk-provider</id>
<class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
<property name="Connect String">nifi-inf-02:2181,nifi-inf-03:2181</property>
<property name="Root Node">/nifi</property>
<property name="Session Timeout">10 seconds</property>
<property name="Access Control">Open</property>
</cluster-provider> Cheers, André -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more