About AcharkiMed

AcharkiMed · ‎03-31-2018

Hi @CoryIsaacson, Cloudera Impala ODBC v2.5.5 is the old version, in fact, I think it's the first release. You are now using the last one 2.5.41 (october 2017). 41 > 5 😉 Good luck.

AcharkiMed · ‎03-31-2018

Hi @GopinathS, I think you must change this param in your odbc.ini file: StringColumnLength: The maximum number of characters that can be contained in STRING columns. (default value: 32767). source: https://www.cloudera.com/documentation/other/connectors/impala-odbc/latest/Cloudera-ODBC-Driver-for-Impala-Install-Guide.pdf Good luck.

AcharkiMed · ‎03-16-2018

Hi, The problem was that the class : org.apache.sentry.binding.metastore.SentrySyncHMSNotificationsPostEventListener don't exist in the jar file /opt/cloudera/parcels/CDH-5.12.2-1.cdh5.12.2.p0.4/jars/sentry-binding-hive-1.5.1-cdh5.12.2.jar within the CDH 5.12.2. In fact, there is two ways to solve it, either upgrade to CDH-5.14.0 (this is the easy way) or download the sentry tarball sentry-1.5.1-cdh5.14.0.tar.gz, extract it and try to replace the exist jar with sentry-1.5.1-cdh5.14.0/apache-sentry-1.5.1-cdh5.14.0-bin/lib/sentry-binding-hive-1.5.1-cdh5.14.0.jar that contain the concerned class org/apache/sentry/binding/metastore/SentrySyncHMSNotificationsPostEventListener.class.

AcharkiMed · ‎03-15-2018

Hi, After upgrading from CM 5.12.2 to CM 5.14.1 the Hive metastore service can't start and give the below error message: Command failed to run because this role has an invalid configuration. Review and correct its configuration. First error: Enable Stored Notifications in Database is required by Sentry and must be enabled. And when I enable the Enable Stored Notifications in Database, I have this error: 2018-03-14 19:24:27,154 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: Starting hive metastore on port 9083 2018-03-14 19:24:27,230 WARN org.apache.hadoop.hive.conf.HiveConf: [main]: HiveConf of name hive.sentry.conf.url does not exist 2018-03-14 19:24:27,468 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: 0: Opening raw store with implemenation class:org.apache.hadoop.hive.metastore.ObjectStore 2018-03-14 19:24:27,607 INFO org.apache.hadoop.hive.metastore.ObjectStore: [main]: ObjectStore, initialize called 2018-03-14 19:24:27,737 INFO DataNucleus.Persistence: [main]: Property hive.metastore.integral.jdo.pushdown unknown - will be ignored 2018-03-14 19:24:27,737 INFO DataNucleus.Persistence: [main]: Property datanucleus.cache.level2 unknown - will be ignored 2018-03-14 19:24:28,209 WARN org.apache.hadoop.hive.conf.HiveConf: [main]: HiveConf of name hive.sentry.conf.url does not exist 2018-03-14 19:24:28,211 INFO org.apache.hadoop.hive.metastore.ObjectStore: [main]: Setting MetaStore object pin classes with hive.metastore.cache.pinobjtypes="Table,StorageDescriptor,SerDeInfo,Partition,Database,Type,FieldSchema,Order" 2018-03-14 19:24:28,257 INFO org.apache.hadoop.hive.metastore.ObjectStore: [main]: Initialized ObjectStore 2018-03-14 19:24:29,217 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: Added admin role in metastore 2018-03-14 19:24:29,219 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: Added public role in metastore 2018-03-14 19:24:29,266 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: No user is added in admin role, since config is empty 2018-03-14 19:24:29,266 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: Begin calculating metadata count metrics. 2018-03-14 19:24:29,268 INFO DataNucleus.Datastore: [main]: The class "org.apache.hadoop.hive.metastore.model.MFieldSchema" is tagged as "embedded-only" so does not have its own datastore table. 2018-03-14 19:24:29,269 INFO DataNucleus.Datastore: [main]: The class "org.apache.hadoop.hive.metastore.model.MOrder" is tagged as "embedded-only" so does not have its own datastore table. 2018-03-14 19:24:29,332 INFO DataNucleus.Datastore: [main]: The class "org.apache.hadoop.hive.metastore.model.MFieldSchema" is tagged as "embedded-only" so does not have its own datastore table. 2018-03-14 19:24:29,332 INFO DataNucleus.Datastore: [main]: The class "org.apache.hadoop.hive.metastore.model.MOrder" is tagged as "embedded-only" so does not have its own datastore table. 2018-03-14 19:24:29,364 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: Finished metadata count metrics: 1 databases, 3 tables, 0 partitions. 2018-03-14 19:24:29,385 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [main]: DefaultFS: hdfs://node.master.dc8:8020 2018-03-14 19:24:29,400 INFO org.apache.sentry.binding.hive.conf.HiveAuthzConf: [main]: DefaultFS: hdfs://node.master.dc8:8020 2018-03-14 19:24:29,438 WARN org.apache.hadoop.hive.conf.HiveConf: [main]: HiveConf of name hive.sentry.conf.url does not exist 2018-03-14 19:24:29,439 WARN org.apache.sentry.binding.hive.conf.HiveAuthzConf: [main]: Using the deprecated config setting hive.sentry.server instead of sentry.hive.server 2018-03-14 19:24:29,442 ERROR org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: MetaException(message:Failed to instantiate listener named: org.apache.sentry.binding.metastore.SentrySyncHMSNotificationsPostEventListener, reason: java.lang.ClassNotFoundException: org.apache.sentry.binding.metastore.SentrySyncHMSNotificationsPostEventListener) at org.apache.hadoop.hive.metastore.MetaStoreUtils.getMetaStoreListeners(MetaStoreUtils.java:1517) at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:555) at org.apache.hadoop.hive.metastore.RetryingHMSHandler.<init>(RetryingHMSHandler.java:78) at org.apache.hadoop.hive.metastore.RetryingHMSHandler.getProxy(RetryingHMSHandler.java:84) at org.apache.hadoop.hive.metastore.HiveMetaStore.newRetryingHMSHandler(HiveMetaStore.java:6313) at org.apache.hadoop.hive.metastore.HiveMetaStore.newRetryingHMSHandler(HiveMetaStore.java:6308) at org.apache.hadoop.hive.metastore.HiveMetaStore.startMetaStore(HiveMetaStore.java:6558) at org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:6485) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.run(RunJar.java:221) at org.apache.hadoop.util.RunJar.main(RunJar.java:136) 2018-03-14 19:24:29,442 ERROR org.apache.hadoop.hive.metastore.HiveMetaStore: [main]: Metastore Thrift Server threw an exception... MetaException(message:Failed to instantiate listener named: org.apache.sentry.binding.metastore.SentrySyncHMSNotificationsPostEventListener, reason: java.lang.ClassNotFoundException: org.apache.sentry.binding.metastore.SentrySyncHMSNotificationsPostEventListener) at org.apache.hadoop.hive.metastore.MetaStoreUtils.getMetaStoreListeners(MetaStoreUtils.java:1517) at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:555) at org.apache.hadoop.hive.metastore.RetryingHMSHandler.<init>(RetryingHMSHandler.java:78) at org.apache.hadoop.hive.metastore.RetryingHMSHandler.getProxy(RetryingHMSHandler.java:84) at org.apache.hadoop.hive.metastore.HiveMetaStore.newRetryingHMSHandler(HiveMetaStore.java:6313) at org.apache.hadoop.hive.metastore.HiveMetaStore.newRetryingHMSHandler(HiveMetaStore.java:6308) at org.apache.hadoop.hive.metastore.HiveMetaStore.startMetaStore(HiveMetaStore.java:6558) at org.apache.hadoop.hive.metastore.HiveMetaStore.main(HiveMetaStore.java:6485) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.run(RunJar.java:221) at org.apache.hadoop.util.RunJar.main(RunJar.java:136) 2018-03-14 19:24:29,444 INFO org.apache.hadoop.hive.metastore.HiveMetaStore: [Thread-2]: Shutting down hive metastore. NB: Knowing that CDH is always 5.12.2 and JDK updated from 1.8_121 to 1.8_144. Is it just a temporary problem that need a CDH be upgraded to 5.14.0 ? or it's a bug!? Thanks in advance.

AcharkiMed · ‎03-06-2018

@Tim Armstrong But with this solution we will lose the parallelism, no ? and it may be cause a slow insert queries..

AcharkiMed · ‎03-05-2018

Hi @hores 1- You are welcome. 2- Unfortunaly, I do a lot of searchs and it seems like there is no more depth explications about the queries profile metrics. What I advice you is when do you have a problem to understand one of it, try to communicate it with the community to get more explanations. Good luck.

AcharkiMed · ‎03-02-2018

Hi @kfc You can go to Configuration in CM Impala service and change the Impala Daemon Logging Threshold ERROR instead of INFO, so just the errors will be logged.

AcharkiMed · ‎03-01-2018

In fact, the answer is yes, I found that Spark has the MLlib Library for Machine Learning algorithms, and it seems great.

AcharkiMed · ‎02-28-2018

Hi @hores 1- I thing "Rows available" time, is the time that impala taked to execute the query and prepare the results to be fetched, it's just before "First row fetched". 2- May be this link about Monitoring Impala Queries can help you.

AcharkiMed · ‎02-28-2018

Thanks @Matt Brandwein. From a computational force point of view, yes (knowing that Mahout also uses Spark),but what about the Mahout algorithms library? is Spark has some libriries too?

Online	Offline
Last Visited	‎05-25-2022 11:41 AM

Member Since	‎07-17-2017 07:15 AM
Last Visited	‎05-25-2022 11:41 AM
Posts	143
Kudos received	16

Cloudera Community

Re: What performance to expect from Cloudera VM ?

Re: Impala date

Re: Error 1107

Re: Cannot connect to Impala via ODBC

Re: Getting improper "Unexpected character" using ...

Re: Impala ODBC Driver 2.5.5 old version?

Re: Impala ODBC driver settings for linux

Re: Hive Metastore fails to start after upgrading ...

Hive Metastore fails to start after upgrading to C...

Re: combine small parquet files

Re: Impala "Rows available" in Query Timeline

Re: Impalad logs diskspace full

Re: Why the Apache Mahout is deprecated and what's...

Re: Impala "Rows available" in Query Timeline

Re: Why the Apache Mahout is deprecated and what's...