Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Semantic exception on executing - show partitions `database_name.tablename`; in hive cli

avatar
Frequent Visitor

We recently upgraded from hdp 2.6.4 to 2.6.5. After the upgrade i am not able to execute this command - 

show partitions `<database_name>.<table_name>`

 

The command works fine with 2.6.4 version.

Any help would be appreciated. Thanks!

1 ACCEPTED SOLUTION

avatar
Frequent Visitor

Just an update from my side so that someone else would benefit, if they came across this issue.

Here is the resolution we received from the Cloudera/Hortonworks support team.

Resolution:

 

We have created followup jira's to support tablenames with (.)dot in HIVE-21198 & HIVE-21151. This 2 jira's are still in progress, but still consider that even if jiras are fixed, `db.table` will be considered as tablename with special characters.

 

Workaround:

 

Please consider to update the scripts to split & quote dbname & tablename like `dbname`.`tablename'

View solution in original post

1 REPLY 1

avatar
Frequent Visitor

Just an update from my side so that someone else would benefit, if they came across this issue.

Here is the resolution we received from the Cloudera/Hortonworks support team.

Resolution:

 

We have created followup jira's to support tablenames with (.)dot in HIVE-21198 & HIVE-21151. This 2 jira's are still in progress, but still consider that even if jiras are fixed, `db.table` will be considered as tablename with special characters.

 

Workaround:

 

Please consider to update the scripts to split & quote dbname & tablename like `dbname`.`tablename'