The timestamp column is not "suitable" for a partition (unless you want thousands and thousand of partitions).   What is suitable : - is to create an Hive table on top of the current not partitionned data, - create a second Hive table for hosting the partitionned data (the same columns + the partition column), - eventualy load the data from the first table to the second one using a query that will "parse" the timestamp column and extract what should be a suitable value for the partition column (for example the year or the year-and-the-month, ...).   Example :   INSERT INTO TABLE my_partitioned_table PARTITION (part_col_name) SELECT *, year(to_date(my_timestamp_column)) FROM my_not_partitioned_table;   You don't have to put the partition value in the insert statement if you enable dynamic partition in Hive. set hive.exec.dynamic.partition=true; set hive.exec.dynamic.partition.mode=nonstrict;   And on your sample it's not working properly because you didn't parse the timestamp column, you use it as is. Each unique value will create a partition. For a timestamps, it's almost each value that is unique.   ... View more

The solution was to put the python script in Hue->Query->Editor->Spark in the Libs field with the full path of the python script example: Libs:  /user/userxyz/myscript.py and run the query. Clicking the job_xxxxx link will show if the script ran successfully or not. ... View more

You might want to try map parquet tables by index, rather than column name: SET parquet.column.index.access=true; ... View more

ACID is still not considered as production ready at this stage from Cloudera, as they are still experimental, please see our doc below: https://www.cloudera.com/documentation/enterprise/latest/topics/hive_ingesting_and_querying_data.html ... View more