Member since
03-23-2015
1288
Posts
114
Kudos Received
98
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3350 | 06-11-2020 02:45 PM | |
5067 | 05-01-2020 12:23 AM | |
2862 | 04-21-2020 03:38 PM | |
3564 | 04-14-2020 12:26 AM | |
2360 | 02-27-2020 05:51 PM |
05-23-2018
12:59 AM
Please run : sudo -u yarn yarn logs -applicationId application_1526609705906_0246 -appOwner {username} Capture the output and examine what the log says.
... View more
05-21-2018
06:10 PM
You will need to migrate the backend database to the new host. How to do it will be subject to which DB you are using. Please refer to the DB vendor for details. Once that DB migrate is done, then you can remove sentry and add sentry again to the new host as normal.
... View more
05-12-2018
03:43 PM
1 Kudo
The easy way to see if UseNativeQuery is in play here is to look at either JDBC driver log or Impala daemon log to see the query submitted is different from the query you actually ran. When UseNativeQuery=0, JDBC driver will transform query and the format submitted will be very different from your original query. I suggest you have a look to confirm. If you can share the exact error, that can help me to see what else it might be happening if UseNativeQuery is not in play.
... View more
05-12-2018
12:01 AM
1 Kudo
What exactly the error is?
... View more
05-11-2018
04:50 AM
1 Kudo
Hi, You just need to add UseNativeQuery into the connection string, so yours will look like below: jdbc:hive2://<cloudera serverserver>/<database>;AuthMech=1;principal=<>;KrbRealm=<>;KrbHostFQDN=<>;KrbServiceName=hive;KrbAuthType=2;UseNativeQuery=1 Manual can be found here: http://www.cloudera.com/documentation/other/connectors/hive-jdbc/latest/Cloudera-JDBC-Driver-for-Apache-Hive-Install-Guide.pdf Cheers
... View more
05-03-2018
09:54 PM
Hi Vitalii, I think you are correct, based on below: https://github.com/cloudera/sqoop/blob/cdh5-1.4.6_5.14.0/src/java/org/apache/sqoop/SqoopOptions.java#L1719-L1721 public void setInputFieldsTerminatedBy(char c) {
this.inputDelimiters.setFieldsTerminatedBy(c);
} https://github.com/cloudera/sqoop/blob/cdh5-1.4.6_5.14.0/src/java/org/apache/sqoop/SqoopOptions.java#L1816-L1818 public void setFieldsTerminatedBy(char c) {
this.outputDelimiters.setFieldsTerminatedBy(c);
} However, I can see that when --direct is used, 1. it calls class DirectMySQLManager: https://github.com/cloudera/sqoop/blob/cdh5-1.4.6_5.14.0/src/java/org/apache/sqoop/manager/DirectMySQLManager.java#L103 public void exportTable(com.cloudera.sqoop.manager.ExportJobContext context)
throws IOException, ExportException {
context.setConnManager(this);
MySQLExportJob exportJob = new MySQLExportJob(context);
exportJob.runExport();
} 2. in MySQLExportJob class, it actually uses getOutputFieldDelim() function https://github.com/cloudera/sqoop/blob/cdh5-1.4.6_5.14.0/src/java/org/apache/sqoop/mapreduce/MySQLExportJob.java#L57-L58 conf.setInt(MySQLUtils.OUTPUT_FIELD_DELIM_KEY,
options.getOutputFieldDelim()); This explains that we need to use --fields-terminated-by rather than --input-fields-terminated-by. It looks like that it is considered as output for MySQL, as code uses MySQLUtils.OUTPUT_FIELD_DELIM_KEY. I am not sure if it is expected or a bug. I will follow up with our engineering team. Look out for another update sometime next week.
... View more
05-02-2018
11:53 PM
Hi Vitalii, I tested further, you need to use --fields-terminated-by, not --input-fields-terminated-by for the export. As using --fields-terminated-by fixed the issue for me. I am not exactly sure the differences, but I am trying to figure it out.
... View more
05-02-2018
10:40 PM
Hi, Sorry about the delay. I am able to re-produce the issue, and currently investigating, will update you again when I have findings.
... View more
04-10-2018
03:30 PM
Good finding, looks like the keytab file for Oozie was outdated.
... View more
04-10-2018
04:21 AM
Hi, Thanks for reporting the issue, I will try to re-produce this in my lab and will let you know my findings. Cheers
... View more