Hi Kunal, I am assisting Shai with the drill, I followed you instructions but once I am running maven with the profile of cloudera aka 'cdh' I am receiving this [dor@dor-fedora64 drill]$ mvn -U -DskipTests clean install -Pcdh [INFO] Scanning for projects... Downloading: https://repository.cloudera.com/artifactory/cloudera-repos/org/apache/apache/14/apache-14.pom Downloading: http://conjars.org/repo/org/apache/apache/14/apache-14.pom Downloading: http://repository.mapr.com/maven/org/apache/apache/14/apache-14.pom Downloading: http://repo.dremio.com/release/org/apache/apache/14/apache-14.pom Downloading: http://repository.mapr.com/nexus/content/repositories/drill/org/apache/apache/14/apache-14.pom Downloading: https://repo.maven.apache.org/maven2/org/apache/apache/14/apache-14.pom [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.apache.drill:drill-root:1.11.0: Could not transfer artifact org.apache:apache:pom:14 from/to cloudera (https://repository.cloudera.com/artifactory/cloudera-repos/): repository.cloudera.com: Name or service not known and 'parent.relativePath' points at wrong local POM @ line 15, column 11 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.apache.drill:drill-root:1.11.0 (/home/dor/Downloads/drill/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for org.apache.drill:drill-root:1.11.0: Could not transfer artifact org.apache:apache:pom:14 from/to cloudera (https://repository.cloudera.com/artifactory/cloudera-repos/): repository.cloudera.com: Name or service not known and 'parent.relativePath' points at wrong local POM @ line 15, column 11: Unknown host repository.cloudera.com: Name or service not known -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException [dor@dor-fedora64 drill]$
** I am using fedora 26 ** Regards, Dor -----Original Message----- From: Kunal Khatua [mailto:kkha...@mapr.com] Sent: יום ה 03 אוגוסט 2017 20:53 To: user@drill.apache.org Subject: RE: drill error connecting to Hbase The failure appears to be coming from this: Caused by: java.lang.IllegalAccessError: Class org/apache/hadoop/hbase/zookeeper/MetaTableLocator illegally accessing "package private" member of class com/google/common/base/Stopwatch Scrolling up a bit, I noticed that during the startup, there is an error here: 2017-08-03 11:04:58,957 [main] WARN o.a.drill.exec.util.GuavaPatcher - Unable to patch Guava classes. javassist.CannotCompileException: by java.lang.LinkageError: com.google.common.base.Stopwatch When you build your Drill package, you can specify a profile. https://github.com/apache/drill/blob/master/pom.xml#L953 You can choose the platform you need Drill for and build with that. This tells Maven to apply specific versions of some dependencies that will work. e.g. mvn -U -DskipTests clean install -P<profile Id> If there is an issue, let us know the specs of the platform you are building against. It is possible that there might have been upgrades to the dependencies within these platforms that are not being reflected in the pon.xml. -----Original Message----- From: Shai Shapira [mailto:shai.shap...@amdocs.com] Sent: Thursday, August 03, 2017 1:13 AM To: user@drill.apache.org; Kunal Khatua <kkha...@mapr.com> Subject: RE: drill error connecting to Hbase Attached the relevant part from the sqlline.log, Hope it helps Thanks, Shai -----Original Message----- From: Shai Shapira Sent: Thursday, August 03, 2017 11:04 AM To: kkha...@mapr.com Cc: user@drill.apache.org Subject: RE: drill error connecting to Hbase Hi, My versions are: Hbase - 1.2.0 Hive - 1.1.0 I'll send the complete stack trace. Is Drill is so version sensitive? Can I build a solution for production based on Drill? Or should I stick to what is coming with the Cloudera/Hortonworks distribution? Thanks, Shai hbase shell 17/08/03 10:54:05 INFO Configuration.deprecation: hadoop.native.lib is deprecated. Instead, use io.native.lib.available HBase Shell; enter 'help<RETURN>' for list of supported commands. Type "exit<RETURN>" to leave the HBase Shell Version 1.2.0-cdh5.8.2, rUnknown, Sun Sep 11 11:52:54 PDT 2016 hive shell Logging initialized using configuration in jar:file:/opt/cloudera/parcels/CDH-5.8.2-1.cdh5.8.2.p1980.2070/jars/hive-common-1.1.0-cdh5.8.2.jar!/hive-log4j.properties WARNING: Hive CLI is deprecated and migration to Beeline is recommended. Thanks, Shai -----Original Message----- From: Kunal Khatua [mailto:kkha...@mapr.com] Sent: Wednesday, July 26, 2017 8:58 PM To: user@drill.apache.org Subject: RE: drill error connecting to Hbase The bundled projects (HBase, Hive) in CDH have their own versions. I'm wondering if that is what is the difference. Drill has been tested with HBase 1.1.1 and Hive 1.2.1 . For higher versions, as long as APIs have not changed, things should be backward compatible. Also, the error message you see in the SQLLine session... there is a complete stack trace in the Drill logs. Can you share that stack trace as well? -----Original Message----- From: Shai Shapira [mailto:shai.shap...@amdocs.com] Sent: Wednesday, July 26, 2017 5:50 AM To: user@drill.apache.org Subject: RE: drill error connecting to Hbase It is CDH 5.8.2 I believe it is reliable versions, isn't it? Thanks, Shai -----Original Message----- From: Kunal Khatua [mailto:kkha...@mapr.com] Sent: Monday, July 24, 2017 8:50 AM To: user@drill.apache.org Subject: RE: drill error connecting to Hbase This means that the connectivity with ZK appears to be working. What are the HBase, ZK and Hadoop versions that you are working with? I presume that the student table is otherwise accessible. -----Original Message----- From: Shai Shapira [mailto:shai.shap...@amdocs.com] Sent: Sunday, July 23, 2017 2:58 AM To: user@drill.apache.org Cc: Shai Shapira <shai.shap...@amdocs.com> Subject: RE: drill error connecting to Hbase Hi, I installed Drill and started to work with it, my goal is to use it to connect to Hbase. I checked it a bit locally, csv files, Json files, works great. When I am trying to connect to Hbase, I am getting error. It seems that it is connecting to the Hbase/ZK, but fails somehow there. The errors when trying to select from non-exist table ( stud ) and when accessing an existing table ( students ) are different. For existing table, the error is in the zookeeper.MetaTableLocator. Any ideas? Thanks, Shai illin4620 STABDB05 54 > drill Jul 20, 2017 6:17:02 PM org.glassfish.jersey.server.ApplicationHandler initialize INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26... apache drill 1.10.0 "just drill it" 0: jdbc:drill:zk=local> use hbase; +-------+------------------------------------+ | ok | summary | +-------+------------------------------------+ | true | Default schema changed to [hbase] | +-------+------------------------------------+ 1 row selected (0.895 seconds) 0: jdbc:drill:zk=local> select * from students ; Error: SYSTEM ERROR: IllegalAccessError: tried to access method com.google.common.base.Stopwatch.<init>()V from class org.apache.hadoop.hbase.zookeeper.MetaTableLocator [Error Id: 71a4a041-4f5d-4e68-9400-78c2faeac6f9 on illin4620:31010] (state=,code=0) 0: jdbc:drill:zk=local> select * from stud ; Error: DATA_READ ERROR: Failure while loading table stud in database hbase. Message: stud SQL Query null [Error Id: f0a6591d-9068-4490-95c0-b0aea41365b4 on illin4620:31010] (state=,code=0) Thanks, Shai From: Shai Shapira Sent: Sunday, July 23, 2017 12:49 PM To: Shai Shapira <shai.shap...@amdocs.com> Subject: drill error connecting to Hbase Shai Shapira * shai.shap...@amdocs.com<mailto:shai.shap...@amdocs.com> * +972 9 776 4171 This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
