Hi @drgenious  First, please test your script outside of Oozie. If it is working outside of Oozie, then it should work from Oozie as well. As for  error "No module named impala.dbapi" it could be that there is some version dependency issue with impyla and its related libraries refer ---> https://github.com/cloudera/impyla/issues/227   ... View more

Hi @MrBeasr  Please check the status of job via Oozie Database: # select count(*) from WF_JOBS where id like '%0043858-220322202819429-oozie-oozi-W%';   If require you may set the status of the job in Database itself: # update wf_jobs set status='FAILED' where id like '%0043858-220322202819429-oozie-oozi-W%';  ... View more

Hi @mohammad_shamim  You need to check DB logs and see if you are able to find any error. Else reach-out to your DB team, they should be best point of contact to help you with DB related problem  ... View more

Hi @JoshiRamesh  In your query the Question Mark (?) symbol is this a value for deliveryconstructuid. Can you put it in double quotes and check if it works for you Example SELECT * FROM my_table WHERE array_contains(my_array_col, "value1")  This query will return all rows from “my_table” where “my_array_col” contains “value1” ... View more

  Hi @dave22    The table data is stored in a HDFS location, so you may consume information out of it # hdfs dfs -du -s -h /path/to/database/ --> From here you can pick the owner of the path, which should be the username --> sub folders/files are the tables within the database --> The modification date can be used as the last updated date  --> size of the table can be picked using below command # hdfs dfs -du -s -h/path/to/database/ Let us know if this helps ... View more

Hi @Iga21207  Please find below the definition of parameters you have mentioned. We don't think that tweaking these parameters will cause much impact on the loading of metadata to impala daemon from catalog.  ================================================================== catalog_max_lock_skipped_topic_updates,   default value is 3:   Maximum number of topic updates skipped for a table due to lock contention in catalogd after which it must be added to the topic the update log. This limit only applies to distinct lock operations which block the topic update thread. topic_update_tbl_max_wait_time_ms,   default value is 120000:   Maximum time (in milliseconds) catalog's topic update thread will wait to acquire lock on table. If the topic update thread cannot acquire a table lock it skips the table from that topic update and processes the table in the next update. However to prevent starvation it only skips the table catalog_max_lock_skipped_topic_updates many times. After that limit is hit, topic thread block until it acquires the table lock. A value of 0 disables the timeout based locking which means topic update thread will always block until table lock is acquired. max_wait_time_for_sync_ddl_s,   default value is 0,   Maximum time (in seconds) until which a sync ddl operation will wait for the updated tables to be the added to the catalog topic. A value of 0 means sync ddl operation will wait as long as necessary until the update is propogated to all the coordinators. This flag only takes effect when topic_update_tbl_max_wait_time_ms is enabled. A value greater than 0 means catalogd will wait until that number of seconds before throwing an error indicating that not all the coordinators might have applied the changes caused due to the ddl. ================================================================== However, you may increase the num_metadata_loading_threads this determines how much parallelism Impala devotes to loading metadata in the background. The default is 64. You might increase this value for systems with huge numbers of databases, tables, or partitions. NOTE: Increasing this value will cause more CPU utilization.  ... View more

@skasireddy 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

@echodot 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

Hi @Kropiciel  To connect ODBC driver with multiple HiveServers, you can configure High Availability for Hive using LB, refer below doc for same. The use the LB hostname and port in the connection string https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/configuring-apache-hive/topics/hive-ha-loadbalancer.html Let us know if this helps.   As for the python connection use below code and check how it goes.   CODE: --------- from sqlalchemy import create_engine #Input Information host = hive_hostname port = 10000 schema = schema_name table = table_name   #Execution engine = create_engine(f'hive://{host}:{port}/{schema}') engine.execute(QUERY) ... View more