Cloudera Community
brianwhu
user rank
Explorer
My Accepted Solutions
Show All

Connection via com.cloudera.impala.jdbc.DataSource...

by Explorer in Support Questions
‎09-20-2019 07:50 AM
1 Kudo
‎09-20-2019 07:50 AM
1 Kudo
The latest Impala JDBC driver (2.6.15) seems to have an issue with its DataSource implementation. When trying to use com.cloudera.impala.jdbc.DataSource directly without any reference to the driver name, we get the following exception. Could anyone shed some light?   Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) Caused by: java.sql.SQLException: Error creating Driver, Driver class name incorrect. at com.cloudera.impala.jdbc.common.AbstractDataSource.doInitialize(Unknown Source) at com.cloudera.impala.jdbc.common.AbstractDataSource.getSimbaConnection(Unknown Source) at com.cloudera.impala.jdbc.common.AbstractDataSource.getConnection(Unknown Source) ... 5 more Caused by: com.cloudera.impala.support.exceptions.GeneralException: Error creating Driver, Driver class name incorrect. at com.cloudera.impala.dsi.core.impl.DSIDriverFactory.createDriver(Unknown Source) ... 9 more Caused by: java.lang.ClassCastException: com.cloudera.impala.jdbc.Driver cannot be cast to com.cloudera.impala.dsi.core.interfaces.IDriver ... 10 more     ... View more
Labels:

Re: You can't drop a kudu partition?!

by Explorer in Support Questions
‎05-24-2017 10:59 AM
‎05-24-2017 10:59 AM
I see my mistake. The statement is supposed to say DROP RANGE PARTITION... ... View more

You can't drop a kudu partition?!

by Explorer in Support Questions
‎05-24-2017 10:03 AM
‎05-24-2017 10:03 AM
When trying to drop a range partition of a Kudu table via Impala's ALTER TABLE, we got   Server version: impalad version 2.8.0-cdh5.11.0 RELEASE (build e09660de6b503a15f07e84b99b63e8e745854c34) Query: alter TABLE vis.ss7gsm_fact_kudu DROP PARTITION (unix_timestamp('2017-03-21 00:00:00') <= sql_interval < unix_timestamp('2017-03-21 02:00:00')) ERROR: AnalysisException: ALTER TABLE DROP PARTITION is not supported for Kudu tables: PARTITION (unix_timestamp('2017-03-21 00:00:00') <= sql_interval < unix_timestamp('2017-03-21 02:00:00'))   Is this an Impala/Kudu integration issue or the way it is with Kudu?   Thanks, Brian ... View more
Labels:

Re: Impala/Kudu non-covering range partition to su...

by Explorer in Support Questions
‎04-13-2017 06:36 AM
‎04-13-2017 06:36 AM
Hi Matt,   It seems we are going down this path for now. It is close enough to what we have in Vertica, which does grow new partitions automatically though.   Thanks, Brian ... View more

Is there an Impala UDF C++ dev package for Red Hat...

by Explorer in Support Questions
‎03-17-2017 08:21 AM
‎03-17-2017 08:21 AM
Hi,   On Red Hat 6.8 the highest version of g++ supported is 4.4.7 (see this Red Hat document). This compiler can't handle some of the later C++ language features used by the Impala UDF development package. The following has to be done to get the sample codes in "impala-udf-samples-master" to compile:   #define keyword "noexcept" as "throw()" #include <memory> to access std::shared_ptr Add compiler flag "-std=c++0x" so std::shared_ptr is recognized Even so, the generated binaries "uda-sample-test" and "udf-sample-test" when run from the command line crash right away with segmentation faults.   Is there a package that would support this old version of g++?   Thanks, Brian Hu ... View more
Labels:

Impala/Kudu non-covering range partition to suppor...

by Explorer in Support Questions
‎02-13-2017 09:17 AM
‎02-13-2017 09:17 AM
Hi Impala/Kudu gurus,   I'm extremely excited by the new Impala/Kudu release that supports non-covering range partition, as described here: https://github.com/cloudera/kudu/blob/master/docs/design-docs/non-covering-range-partitions.md and here: https://gerrit.cloudera.org/#/c/4856/   Yet I haven't figured out how exactly to use it to support rolling window data retention that our business needs. The syntax descibed in the 2nd document above still seems to require static partition specification.   What we need is the ability to auto-create new partitions based on a timestamp expression so that each partition contains x days of data only. We then can drop the old partitions based on our data retention policy on a per table basis.   As a comparison, the similar function is provided by Oracle's range interval partition:     PARTITION BY RANGE (CREATION_DATE) INTERVAL (NUMTODSINTERVAL(7, 'DAY')) and Vertica's partition key expression:   PARTITION BY (floor((((tbl.creation_ts)::date - '0001-12-31 BC'::date) / 3)))   Thanks, Brian ... View more
Labels:
Contact Me
Online
Offline
Last Visited
‎02-04-2020 04:26 PM
Community Statistics
Member Since ‎02-09-2017 08:14 AM
Last Visited ‎02-04-2020 04:26 PM
Posts 8
Kudos received 1