@Srinivas-M You may set these properties in a safety valve for core-site.xml. CM UI > HDFS > Configuration >  Cluster-wide Advanced Configuration Snippet (Safety Valve) for core-site.xml ... View more

we tried replicating the issue with the data shared by @Shivakuk . Left/Right Single/Double Quotation Mark(smart quotes) in the text did not show up correctly and got converted to ? . I was able to fix this issue by changing the  LC_CTYPE from "UTF-8" to "en_US.UTF-8". Check "locale" command output: # locale LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= See what your LC_CTYPE read. If it does not read "en_US.UTF-8", do the following: vi ~/.bash_profile Add the following two lines at the bottom: +++ LC_CTYPE=en_US.UTF-8 export LC_CTYPE +++ Save the file, and source it for it to take effect: #source ~/.bash_profile Now connect to beeline, and see if the data show up correctly.   ... View more

@itdm_bmi We are still seeing the error " java.lang.ClassNotFoundException: Class org.apache.hadoop.hive.contrib.serde2.MultiDelimitSerDe" This means, you have not uploaded the "hive-contrib" jar to Hive classpath as mentioned here. If you are on CDP(>7.1.5 onward) then, we will not have to upload hive-contrib jar to the class path. This serde class is already added to Hive native serde list. You just need to alter the original table, and change the serde(Note: only applies to CDP version > 7.1.5) ALTER TABLE <table name> SET SERDE 'org.apache.hadoop.hive.serde2.MultiDelimitSerDe' If you are on an older version, do consider uploading to hive-contrib jar to hive classpath by uploading this to aux jar path location. ... View more

@AndreaCavenago Does this error appear every time we run this spark-submit command? As this is a warning message, and it does not have any real impact, we can avoid it by changing the log level. In the script.py file, add the following two lines: from pyspark import SparkContext SparkContext.setLogLevel("ERROR") This will avoid the WARN message. But it will still be good to address the actual issue. ... View more

@novice_tester when you create a database, it takes the external warehouse directory path from hive.metastore.warehouse.external.dir, and sets that as the database LOCATION for external tables only(when created without setting location clause). Please note, there is another MANAGEDLOCATION field that is blank.   e.g. describe database extended question; +-----------+----------+----------------------------------------------------+------------------+-------------+-------------+-------------+ | db_name | comment | location | managedlocation | owner_name | owner_type | parameters | +-----------+----------+----------------------------------------------------+------------------+-------------+-------------+-------------+ | question | | hdfs://node2.cloudera.com:8020/warehouse/tablespace/external/hive/question.db | | hive | USER | | +-----------+----------+----------------------------------------------------+------------------+-------------+-------------+-------------+  A Managedlocation can be set on a database if you want to use a different location for managed tables other than hive.metastore.warehouse.dir. Otherwise it is kept blank. I hope this helps.   To summarize, you do not need to worry about the LOCATION of a database. It can host both managed and external tables. When you create a managed table under the same DB, it will pick the path set in hive.metastore.warehouse.dir, irrespective of the database Location, and when you create an external table without the location clause, it gets stored in the DB LOCATION path. ... View more