@Rak ,   I'm suspecting you are using Impala, because of the statement of the values returning null, but please confirm so I can properly label this question so others can see it.   Please see the following in the Impala documentation regarding the proper format for casting a string into a timestamp datatype:   https://docs.cloudera.com/documentation/enterprise/latest/topics/impala_timestamp.html   Restrictions: If you cast a  STRING  with an unrecognized format to a  TIMESTAMP , the result is  NULL  rather than an error. Make sure to test your data pipeline to be sure any textual date and time values are in a format that Impala  TIMESTAMP  can recognize. Currently, Avro tables cannot contain  TIMESTAMP  columns. If you need to store date and time values in Avro tables, as a workaround you can use a  STRING  representation of the values, convert the values to  BIGINT  with the  UNIX_TIMESTAMP()  function, or create separate numeric columns for individual date and time fields using the  EXTRACT()  function. Examples: The following examples demonstrate using  TIMESTAMP  values with built-in functions: select cast('1966-07-30' as timestamp); select cast('1985-09-25 17:45:30.005' as timestamp); select cast('08:30:00' as timestamp); select hour('1970-01-01 15:30:00'); -- Succeeds, returns 15. select hour('1970-01-01 15:30'); -- Returns NULL because seconds field required. select hour('1970-01-01 27:30:00'); -- Returns NULL because hour value out of range. select dayofweek('2004-06-13'); -- Returns 1, representing Sunday. select dayname('2004-06-13'); -- Returns 'Sunday'. select date_add('2004-06-13', 365); -- Returns 2005-06-13 with zeros for hh:mm:ss fields. select day('2004-06-13'); -- Returns 13. select datediff('1989-12-31','1984-09-01'); -- How many days between these 2 dates? select now(); -- Returns current date and time in local timezone.   ... View more

Hi @Rak ,   Could you please elaborate on what component you are specifically doing this (Hive, Impala, etc..) so we can properly label this question and answer accordingly? ... View more

I wanted to interject that while both the above are definite valid possible causes of Oozie jobs stuck in PREP state, there may be several other possible causes which may need to be resolved such as:   1.  Issues with the Yarn Resource Manager / MR Job Tracker, lack of resources either for the RM or queues for the user running the job. 2.  Problems with the Oozie server getting to the oozie database server, the database server itself, or locks on tables. 3.  Lack of resources to Oozie such as callable queues, java heap, GC thrashing, etc.   The above is a brief shortlist from review of support cases relating to Oozie jobs stuck in PREP.   I want to emphasize that deleting records from the Oozie database should be ONLY done the last resort to solving this problem, and only needed if you have a very large mass of oozie workflows that cannot be killed in a timely fashion by an oozie CLI script.   This should be only done at the direction of support, people knowledgeable with SQL, and the relationship between tables, columns, and rows in the oozie database as referential integrity and constraints are lacking in the schema design.  The above post from 2017 also missed one key table COORD_ACTIONS, where if this data was not properly cleaned up, would break your Oozie purge and possibly cause other serious problems. ... View more

I would say this depends on if your hostname is set FQDN at time of CM/cluster install, if your hostname is set as fully qualified in the OS by the hostname command, or if you are still using TLS/SSL your certificates have the FQDN hostname.   Kerberos and several other things are very sensitive to DNS.   Run the hosts inspector under CM to check for DNS / host resolution problems.   Since you state you are not using DNS, what I would suggest is making sure your /etc/hosts file on all hosts contains all hosts of the cluster and CM, and are set as fully qualified hostname first, then aliased to the short hostname.  You can use rsync to keep this file accurate across the cluster.   Also make sure /etc/nsswitch.conf has files first for the hosts: line, and /etc/hosts will get used first.   Finally, if you supect the internal hostname was changed away from FQDN to short, either change it back or follow the following article to get CM configuration back in sync with what it was at time of install (Check the Name column beneath CM hosts tab to see what CM has in it's database):   https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_change_hostnames.html   [root@cm1 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.2.3 cm1.rgjustice.com cm1 192.168.2.4 node1.rgjustice.com node1 192.168.2.5 node2.rgjustice.com node2   [root@cm1 ~]# cat /etc/nsswitch.conf |grep hosts #hosts: db files nisplus nis dns hosts: files dns myhostname ... View more

Hi @bridgor , if we were just to take the N6apache6thrift9transport13TSSLException originally posted, this typically ends in a hostname mistmatch in the .pem files used / DNS problems.   Check statestore logs / web UI for issues as well.   I agree with @AcharkiMed that this seems to be network / SSL related. ... View more

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