@Cloudera learning   I don't think any formula aviable to estimate the durtaion ( at least to my knowledge)   But I tried the data node decommission few times for various reasons and this is my experience   for a 40 TB node, it took between 45 mins and 60 mins approx (i hope it should be less than 5 or 10 mins for you)   you can monitor this from CM -> HDFS -> WebUI -> Namenode Web UI -> a new window will open, 'Datanodes' menu -> scroll down to Decommissioning (keep refresh this page to get the progress) ... View more

@Venkatesh_Kumar   Pls try this options https://github.com/rcongiu/Hive-JSON-Serde#jsonserde---a-readwrite-serde-for-json-data   ... View more

@ludof   Please run the below command, it will show you which java version being used currently   echo $JAVA_HOME     ... View more

@ludof   If my understanding is correct, you want to add few new parameters which are not already present in configuration. If so, in general cloudera provides this option   Ex: Cloudera manager -> Hive -> Configuration -> search for 'Advanced Configuration' -> identify the correct file & click on + symbol and add the corresponding name and value    if you need specific to Oozie, search for 'Oozie Server Advanced Configuration Snippet (Safety Valve) for oozie-site.xml' under Oozie -> Configuration and add name values as needed   also pls make sure to restart the corresponding service, so that your changes will be activated ... View more

@ludof   If you have cloudera managed cluster then it is recomended to manage your configuration via cloudera manager.    please do not edit the configuration file manually unless you are very familiar as the same copy of configuration file will be maintained in different nodes and in different locations (in the same node) for various reasons  ... View more

@ludof   The table 'titles' will be in hdfs, so the user root cannot access it unless it has permission to read/write (root is not an admin for hdfs). Either you can set the permission to the root user in hdfs for the table or use the user who has already permission to read/write ... View more

  @cjervis  - This is the third time i'm posting the below message in the same thread as it get deleted automatically everytime when I edit the below message. In summary, I made few typos and tried to correct it by editing the message but found the entire post is missing after edit. Please take care!!   @ludof   You have mentioned that you are importing data from MySQL and you have already installed MySQL Connector. So sqoop suppose to use MySQL Connector but it is still using "Generic JDBC Connector". I believe the below three reasons will be the reason for your issue   1. You might have made some mistake in the MySQL Connector configuration/installation (or)   2. The MySQL Connector version that you are using is not Suitable for your MySQL Version. Ex: If you are using MySQL 5.6, it requires a driver version 5.1.26 or higher (or)   3. May be you would get the latest mysql connector version in /usr/share/java, still it may create trouble if you have old version and new version in the same folder and mysql-connector-java.jar is still pointing to the older version Ex: Consider you have below old & new version in /usr/share/java and mysql-connector-java.jar is pointing to older version mysql-connector-java-5.1.25-bin.jar -- old version mysql-connector-java-5.1.40-bin.jar -- new version then remove the link mysql-connector-java.jar and make it refer to the new version as follows rm mysql-connector-java.jar ln -s /usr/share/java/mysql-connector-java-5.1.40-bin.jar mysql-connector-java.jar mysql-connector-java.jar -> /usr/share/java/mysql-connector-java-5.1.40-bin.jar   ... View more