Member since
07-07-2020
97
Posts
5
Kudos Received
5
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
315 | 05-31-2024 10:34 AM | |
1161 | 06-13-2022 10:24 PM | |
5041 | 06-09-2022 09:56 PM | |
1651 | 10-12-2021 07:13 AM | |
2727 | 09-22-2021 10:54 PM |
06-05-2024
12:03 PM
Hello, You can use chrony. If using chronyd for time synchronization at Kudu nodes, the rtcsync option must be enabled in chrony.conf. Without rtcsync, the local machine's clock will always be reported as unsynchronized and Kudu masters and tablet servers will not be able to start. Hope this helps.
... View more
05-31-2024
10:34 AM
1 Kudo
Hello, The Oozie workflows are available in HDFS within CDH and HDP clusters. To migrate the Oozie workflows from these clusters to CDP SaaS involves a separate workflow process. While using the HDP clusters, you can use the DistCp tool to migrate the Oozie workflows present in HDFS. While using the CDH clusters, you can employ the Replication Manager App to migrate the Oozie workflows present in HDFS Specifically, some manual updates are required to process the Oozie migration created outside of the Hue Workflow. Before you proceed further, you must understand: During the migration process you must copy across all Oozie job files (workflow.xml, job.properties, and any supporting JARs). Which Oozie workflow files must be copied or migrated to CDP One. Identify the workflow.xml file and job.properties file for each Oozie workload that must be migrated. These files are stored in HDFS and must be copied to the CDP One endpoint. The job.properties file must be updated with the appropriate CDP One endpoints. Optionally, the workflow.xml file needs to be updated. For example, while currently using the legacy “hive action” requires an update to the newer “hive2 action”. Depending on where (the location) you have stored your Oozie workflow data in HDFS, note the following information: The workflow.xml and any job JAR files reside within HDFS in the source cluster. These will have to be copied across into a CDP One endpoint. The job.properties file for a job contains a reference to the location of where the workflow files are stored. The job.properties file will need to be updated during a migration with the new target environment settings / locations.
... View more
03-21-2023
12:01 AM
Hello , - Please share the complete impala-shell command that you are using? - Is there any load balancer configured for impala? Thanks
... View more
07-19-2022
09:31 PM
For the workflows that were created on Hue, you can follow the next steps to export/import the workflows:
>To export:
Go to Documents> Select the workflow(s)> Select the button with three dots and select the Export option
>To import:
Go to Documents> Select the button with three dots and select the Import option.
... View more
06-26-2022
06:16 PM
As upsert is not SQL-92 syntax, the Impala JDBC driver does not currently support it. However, we are currently testing a newer version of the JDBC driver and hope to support upsert in the near future. For the time being, please break these statements into a combination of insert and update statements.
... View more
06-23-2022
03:56 AM
For a permanent fix, you need to install the python version 2.7.5.
... View more
06-22-2022
07:51 AM
Yes, you need to switch to venv everytime or you need to reinstall python with the 2.7.5 version.
... View more
06-22-2022
07:34 AM
You can try the below steps in edge node B virtualenv venv -p python2 cd venv source bin/activate (venv) impala-shell
... View more
06-22-2022
07:31 AM
Hello Syed, Yes, the impala is compatible with Python version 2.7.5.
... View more
06-13-2022
10:24 PM
Oozie Email Action supports attachments of HDFS files. Because standard output files are written as local files, you need to copy them to HDFS first, then specify the path in the <attachment> tag of the email action. <workflow-app name="[WF-DEF-NAME]" xmlns="uri:oozie:workflow:0.1"> ... <action name="[NODE-NAME]"> <email xmlns="uri:oozie:email-action:0.2"> <to>[COMMA-SEPARATED-TO-ADDRESSES]</to> <cc>[COMMA-SEPARATED-CC-ADDRESSES]</cc> <!-- cc is optional --> <subject>[SUBJECT]</subject> <body>[BODY]</body> <content_type>[CONTENT-TYPE]</content_type> <!-- content_type is optional --> <attachment>[COMMA-SEPARATED-HDFS-FILE-PATHS]</attachment> <!-- attachment is optional --> </email> <ok to="[NODE-NAME]"/> <error to="[NODE-NAME]"/> </action> ... </workflow-app>
... View more