@PJ You can increase or decrese the number of mappers used in sqoop command using -m option. This helps you determine the number of parallel connections to be made to netezza. Though, please note, this doe snot always works, sometime the number of mappers are still decided on the basis of splits. The impact of this would be on Yarn, the number of mappers would add load on Yarn as it will run as a Map-Reduce job. ... View more

@Anurag Mishra Can you try the connect command as below: !connect jdbc:hive2://<hiveserver2_host>:10000/default;principal=hive/_HOST@SOLON.PRD Please note that I have changed principal=hive/<host>@SOLON.PRD to principal=hive/_HOST@SOLON.PRD Do replace <hiveserver2_host> with hostname of your Hiveserver2. ... View more

@Tauseef Ahmad No, Hive Metastore and HiveServer2 are still on version 1.2.X.X in HDP-2.6.X. Though, having said that, there are may functionalities of Hive 2.1 which are backported to existing Hive 1.2 in HDP stack. ... View more

@Georg Heiler Please confirm if hive.server2.enable.doAs is set to false at your end, if not, can you please set it to false and then test(hive.server2.enable.doAs=true is not supported with LLAP) Also, confirm if "Maximum Total Concurrent Queries" is not configured 0 for your LLAP. ... View more

@kumar sonal - Please share the exact error you see while connecting to Hive via ODBC - Do confirm if you are using Hortonworks provided Simba ODBC driver. - Is your cluster kerberised? ... View more

@Ans Butt Try using Hortonworks provided Simba ODBC driver which can be dowloaded here. ... View more

@Sirine It could be related to the below issue: https://issues.apache.org/jira/browse/HIVE-16828 Though, I am not sure it is a view of table at your end. As a workaround, can you try recreating the table and then try the query again. ... View more

@Gaurang Shah Please check for the exact error in the Yarn application log corresponding to query run. The Yarn app logs should give us a better understanding of Vertex failure issue. Attache them here, if you can. ... View more

@Gerhard Neuhofer can you share the command used to import the data to Hive. Also, I do not understand "the log directo empty", does this mean no logs in Hive Metastore? Id yes, it seems like a process crash. Check your /var/log/messages for any errors at the time. Do confirm if core limit is set to unlimited in "ulimit -a" output, this shall generate a core file for analysis of the crash. ... View more

@Burhan ud Din Qazi There is no such functionality in Hive, though, I think you can achieve this by adding constraint on all the columns of the table. ... View more

@pk reddy - Can you try running the command via Hive user and not root user. - Check if you enough space under /tmp directory as hive login creates logs there. ... View more

Hi @regie canada, You can use ? to pass the parameters in place of the usual @. Using @ is specific to Transact-SQL. The driver supports SQL-92 syntax where parameter markers in the SQL statement are expected to be question marks. Thanks, Rohit Rai Malhotra ... View more

Hi @May Lei, The syntax you describe is specific to Transact-SQL. The driver supports SQL-92 syntax where parameter markers in the SQL statement are expected to be question marks '?'. Thus, could you please try replacing @ with ? and then test the query. ex) select * from table where col1 = ?param Thanks, Rohit Rai Malhotra ... View more

Hi @wlf211, Have you tried running the query when hive.execution.engine set to MR. This should resolve the problem. Though, if you want to continue using TEZ as your execution engine, try setting the below property and then test the query: hive.auto.convert.sortmerge.join=false Thanks, Rohit Rai Malhotra ... View more

Hi @sandrine G, The issue you are facing is due to some dependency version mismatch. Are in the middle of an upgrade? If yes, please make sure your cluster is upgraded successfully and then try enabling the service. Thanks, Rohit Rai Malhotra ... View more