date:20180201

RE: Apache Phoenix integration

2018-02-01 Thread Kunal Khatua

The JDBC storage plugin allows Drill to leverage any SQL system that has JDBC 
drivers, so it should work.

That said, the JDBC storage plugin is a community developed storage plugin, so 
it might not be fully tested. 

If you are looking to simply have the Phoenix JDBC driver bundled into the 
Drill 3rd party directory, I (think) the reason it is not bundled is because 
we're not actively tracking compatibility of different JDBC drivers with Drill. 
There could also be license issues, which is why we can't bundle drivers for 
platforms like Oracle, etc. 

~ Kunal 

-Original Message-
From: Flavio Pompermaier [mailto:pomperma...@okkam.it] 
Sent: Thursday, February 01, 2018 9:39 AM
To: user@drill.apache.org
Subject: Apache Phoenix integration

Hi all,
looking at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__drill.apache.org_docs_apache-2Ddrill-2Dcontribution-2Dideas_=DwIBaQ=cskdkSMqhcnjZxdQVpwTXg=-cT6otg6lpT_XkmYy7yg3A=daBPP_PaenGs721v8erkPwwO543kYzW-gKUv-c1jVWM=KMq_T0hogIOIv_ttrCLCxBeEt-AUKKxpcQt3PpeNSbs=
it seems that Apache Phoenix is not integrated with Drill right now. In theory 
the integration should be quite straightforward using the JDBC Phoenix 
connector, isn't it?
Right now there are just a few problem of class loading when putting the 
phoenix jar into jars/3rdparty but it shouldn't be too hard to shade 
conflicting classes away.

Has anyone attempted to connect to to Apache before?

Best,
Flavio

Re: Fw: Re: drill in 10 minutes tutorial problem with osx

2018-02-01 Thread Sorabh Hamirwasia

Hi Paul,
The reason we are picking *org.apache* instead of *oadd.org.apache *is
because using Sqlline when we search for Drilver class, it finds it first
inside *jars/drill-jdbc-1.12.0.jar* instead of
*jars/jdbc-driver/drill-jdbc-all-1.12.0.jar* hence it loads all the classes
inside the org.apache namespace. I have already tried drill-embedded and
single node running in distributed mode on osx and it works fine for me in
both cases. It looks to be a setup specific issue on Teemu's environment.

Thanks,
Sorabh

On Wed, Jan 31, 2018 at 9:26 PM, Paul Rogers 
wrote:

> Resending this since the original response went only to Teemu. Developers
> may want to look into the potential bug discussed below.
> - Paul
>  Hi Teemu,
> Thanks for posting the detailed information. Very helpful.
> You are running Sqlline with an embedded Drillbit (that's what
> drill-embedded) does. I suspect that you are hitting an issue due to the
> way that Drill builds the JDBC driver. I'll explain the issue (for the
> benefit of the Drill folks) then suggest a solution for you.
> Drill builds a JDBC driver that includes all of Drill. But, Drill is huge
> (200+ MB), we try to create a dependency-reduced jar. It seems that we are
> not removing so much from the jar that it can no longer run an embedded
> server. The problem in this case is that the jar relocates the package with
> DrillConfig, but it looks like some other part of the code is not adjusted.
> From the dependency-reduced-pom.xml file:
>
>   
>
> ...
>
> 
>
>   org.apache.drill.common.
>
>   oadd.org.apache.drill.common.
>
> 
>
> The stack trace you provided shows that the code tries to reference
> DrillConfig in its original location: 
> org.apache.drill.common.config.DrillConfig.
> But, because of the relocation, it should be referenced
> as add.org.apache.drill.common.config.DrillConfig.
> This is clearly a bug. Would be great if someone (Kunal?) could verify
> this and file a bug.
> In the mean time, I'd suggest you simply run an actual Drill server, then
> connect Sqlline to that server. You'll want to run as a server anyway to
> use the Web UI, to see query profiles, to change your storage profiles, and
> so on.
> A quick check of the documentation suggests we don't actually write up
> this use case. (Suggestion to Bridget: we should.) Here is what to do:
> 1. Ensure you have a Zookeeper running on your machine. See [1] for hints.
> You only need one ZK on your laptop.2. Start Drill with drillbit.sh start.
> (See the distributed mode docs for the other commands.)3. Start Sqlline as
> explained in [2]
> The "out of the box" Drill config uses the "out of the box" ZK config, so
> you should not have to do any setup. Seen the docs for how to use the web
> console and how to stop your Drill server.
> Another key advantage of this mode is that you can better control memory,
> which is important as you run larger or more complex queries.
> Thanks,
> - Paul
> [1] http://drill.apache.org/docs/distributed-mode-prerequisites/[2]
> http://drill.apache.org/docs/starting-drill-in-distributed-mode/
>
>
>
> On Friday, January 26, 2018, 12:32:13 AM PST, te...@pentinsaari.fi <
> te...@pentinsaari.fi> wrote:
>
>  Hi all,
>
> I'm trying to follow the 10 minutes tutorial and I get stuck right
> away...
>
> https://drill.apache.org/docs/drill-in-10-minutes/
>
> Everything works just fine with my ubuntu box, but with osx, this is all
> I get
>
> $ bin/drill-embedded
> Java HotSpot(TM) 64-Bit Server VM warning: Ignoring option MaxPermSize;
> support was removed in 8.0
> sun/misc/VM
> apache drill 1.12.0
> "just drill it"
> 0: jdbc:drill:zk=local> SELECT * FROM cp.`employee.json` LIMIT 3;
> No current connection
> 0: jdbc:drill:zk=local> !list
> 1 active connection:
>   #0  closed  jdbc:drill:zk=local
> 0: jdbc:drill:zk=local> !quit
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.drill.common.config.DrillConfig
> at
> org.apache.drill.jdbc.impl.DrillConnectionImpl.(
> DrillConnectionImpl.java:124)
> at
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(
> DrillJdbc41Factory.java:72)
> at
> org.apache.drill.jdbc.impl.DrillFactory.newConnection(
> DrillFactory.java:69)
> at
> org.apache.calcite.avatica.UnregisteredDriver.connect(
> UnregisteredDriver.java:144)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at sqlline.DatabaseConnection.connect(DatabaseConnection.java:167)
> at
> sqlline.DatabaseConnection.getConnection(DatabaseConnection.java:213)
> at sqlline.Commands.close(Commands.java:925)
> at sqlline.Commands.quit(Commands.java:889)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:62)
> at
>

Re: No FileSystem for scheme: maprfs

2018-02-01 Thread Abhishek Girish

Hey,

Images haven't come through (usually attachments aren't supported in
mailing lists). Can you please find another way of sharing them?

Also, can you share how you deployed Drill - did you build from source or
download packages from MapR? The message usually means your DFS storage
plugin is unable to talk to MapR-FS. Please share the DFS storage plugin
contents, the drill-env.sh [and distrib-env.sh] files. Also, a verbose
version of the error message you observe.

Regards,
Abhishek

On Thu, Feb 1, 2018 at 10:57 AM, Willian Ribeiro <
willian.ribe...@blueshift.com.br> wrote:

> Good morning,
>
> I've tried a lot of suggestions for this error, but i couldn't find any
> solution for my problem.
>
>  - I  have a mapr cluster with hive tables in it.
>
>  - I need to use the Drill to query those tables outside the cluster.
>
>  - I have a CentOS VM configured with distributed Drill but as a single
> node (just for now).
>
>  - I can see the tables and query them when they are empty like this one:
>
> [image: Inline image 1]
>
>
> but when i try to query a table that isn't empty, i get this error:
>
> [image: Inline image 4]
>
>
> My question is: I can query hive tables (located in a mapr cluster) from
> Drill that is installed in a VM (CentOS) outside this cluster?
>
>
> This is how i setup Drill:
>
> STORAGE PLUGIN:
>
> [image: Inline image 5]
>
> drill-override.conf (Configured as a cluster single node)
>
> [image: Inline image 7]
>
> DRILL JARS:
>
> [image: Inline image 8]
>
>
> 3rparty JARS:
>
> 3rdparty/antlr-2.7.7.jar
>
> 3rdparty/antlr-runtime-3.4.jar
>
> 3rdparty/apacheds-i18n-2.0.0-M15.jar
>
> 3rdparty/apacheds-kerberos-codec-2.0.0-M15.jar
>
> 3rdparty/api-asn1-api-1.0.0-M20.jar
>
> 3rdparty/api-util-1.0.0-M20.jar
>
> 3rdparty/asm-debug-all-5.0.3.jar
>
> 3rdparty/async-1.4.1.jar
>
> 3rdparty/avro-1.7.7.jar
>
> 3rdparty/avro-ipc-1.7.7.jar
>
> 3rdparty/avro-ipc-1.7.7-tests.jar
>
> 3rdparty/avro-mapred-1.7.7.jar
>
> 3rdparty/aws-java-sdk-1.7.4.jar
>
> 3rdparty/bcpkix-jdk15on-1.52.jar
>
> 3rdparty/bcprov-jdk15on-1.52.jar
>
> 3rdparty/bonecp-0.8.0.RELEASE.jar
>
> 3rdparty/calcite-avatica-1.4.0-drill-r23.jar
>
> 3rdparty/calcite-core-1.4.0-drill-r23.jar
>
> 3rdparty/calcite-linq4j-1.4.0-drill-r23.jar
>
> 3rdparty/commons-beanutils-1.8.3.jar
>
> 3rdparty/commons-beanutils-core-1.8.0.jar
>
> 3rdparty/commons-cli-1.2.jar
>
> 3rdparty/commons-codec-1.10.jar
>
> 3rdparty/commons-collections-3.2.1.jar
>
> 3rdparty/commons-compiler-2.7.6.jar
>
> 3rdparty/commons-compress-1.4.1.jar
>
> 3rdparty/commons-configuration-1.6.jar
>
> 3rdparty/commons-dbcp-1.4.jar
>
> 3rdparty/commons-digester-1.8.1.jar
>
> 3rdparty/commons-httpclient-3.1.jar
>
> 3rdparty/commons-io-2.4.jar
>
> 3rdparty/commons-lang-2.6.jar
>
> 3rdparty/commons-lang3-3.1.jar
>
> 3rdparty/commons-math-2.2.jar
>
> 3rdparty/commons-math3-3.1.1.jar
>
> 3rdparty/commons-net-3.6.jar
>
> 3rdparty/commons-pool-1.5.4.jar
>
> 3rdparty/commons-pool2-2.1.jar
>
> 3rdparty/commons-validator-1.4.1.jar
>
> 3rdparty/config-1.0.0.jar
>
> 3rdparty/converter-jackson-2.1.0.jar
>
> 3rdparty/curator-client-2.7.1.jar
>
> 3rdparty/curator-framework-2.7.1.jar
>
> 3rdparty/curator-recipes-2.7.1.jar
>
> 3rdparty/curator-x-discovery-2.7.1.jar
>
> 3rdparty/datanucleus-api-jdo-3.2.6.jar
>
> 3rdparty/datanucleus-core-3.2.10.jar
>
> 3rdparty/datanucleus-rdbms-3.2.9.jar
>
> 3rdparty/de.huxhorn.lilith.data.converter-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.data.eventsource-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.data.logging-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.data.logging.protobuf-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.logback.appender.multiplex-classic-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.logback.appender.multiplex-core-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.logback.classic-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.logback.converter-classic-0.9.44.jar
>
> 3rdparty/de.huxhorn.lilith.sender-0.9.44.jar
>
> 3rdparty/de.huxhorn.sulky.codec-0.9.17.jar
>
> 3rdparty/de.huxhorn.sulky.formatting-0.9.17.jar
>
> 3rdparty/de.huxhorn.sulky.io-0.9.17.jar
>
> 3rdparty/derby-driver.jar
>
> 3rdparty/disruptor-3.3.0.jar
>
> 3rdparty/dom4j-1.6.1.jar
>
> 3rdparty/eigenbase-properties-1.1.5.jar
>
> 3rdparty/esri-geometry-api-2.0.0.jar
>
> 3rdparty/findbugs-annotations-1.3.9-1.jar
>
> 3rdparty/foodmart-data-json-0.4.jar
>
> 3rdparty/freemarker-2.3.26-incubating.jar
>
> 3rdparty/gson-2.2.4.jar
>
> 3rdparty/guava-18.0.jar
>
> 3rdparty/hadoop-annotations-2.7.1.jar
>
> 3rdparty/hadoop-auth-2.7.1.jar
>
> 3rdparty/hadoop-aws-2.7.1.jar
>
> 3rdparty/hadoop-client-2.7.1.jar
>
> 3rdparty/hadoop-common-2.7.1.jar
>
> 3rdparty/hadoop-hdfs-2.7.1.jar
>
> 3rdparty/hadoop-mapreduce-client-app-2.7.1.jar
>
> 3rdparty/hadoop-mapreduce-client-common-2.7.1.jar
>
> 3rdparty/hadoop-mapreduce-client-core-2.7.1.jar
>
> 3rdparty/hadoop-mapreduce-client-jobclient-2.7.1.jar
>
> 3rdparty/hadoop-mapreduce-client-shuffle-2.7.1.jar
>
> 3rdparty/hadoop-yarn-client-2.7.1.jar
>
> 3rdparty/hadoop-yarn-common-2.7.1.jar
>
>

No FileSystem for scheme: maprfs

2018-02-01 Thread Willian Ribeiro

Good morning,

I've tried a lot of suggestions for this error, but i couldn't find any
solution for my problem.

 - I  have a mapr cluster with hive tables in it.

 - I need to use the Drill to query those tables outside the cluster.

 - I have a CentOS VM configured with distributed Drill but as a single
node (just for now).

 - I can see the tables and query them when they are empty like this one:

[image: Inline image 1]


but when i try to query a table that isn't empty, i get this error:

[image: Inline image 4]


My question is: I can query hive tables (located in a mapr cluster) from
Drill that is installed in a VM (CentOS) outside this cluster?


This is how i setup Drill:

STORAGE PLUGIN:

[image: Inline image 5]

drill-override.conf (Configured as a cluster single node)

[image: Inline image 7]

DRILL JARS:

[image: Inline image 8]


3rparty JARS:

3rdparty/antlr-2.7.7.jar

3rdparty/antlr-runtime-3.4.jar

3rdparty/apacheds-i18n-2.0.0-M15.jar

3rdparty/apacheds-kerberos-codec-2.0.0-M15.jar

3rdparty/api-asn1-api-1.0.0-M20.jar

3rdparty/api-util-1.0.0-M20.jar

3rdparty/asm-debug-all-5.0.3.jar

3rdparty/async-1.4.1.jar

3rdparty/avro-1.7.7.jar

3rdparty/avro-ipc-1.7.7.jar

3rdparty/avro-ipc-1.7.7-tests.jar

3rdparty/avro-mapred-1.7.7.jar

3rdparty/aws-java-sdk-1.7.4.jar

3rdparty/bcpkix-jdk15on-1.52.jar

3rdparty/bcprov-jdk15on-1.52.jar

3rdparty/bonecp-0.8.0.RELEASE.jar

3rdparty/calcite-avatica-1.4.0-drill-r23.jar

3rdparty/calcite-core-1.4.0-drill-r23.jar

3rdparty/calcite-linq4j-1.4.0-drill-r23.jar

3rdparty/commons-beanutils-1.8.3.jar

3rdparty/commons-beanutils-core-1.8.0.jar

3rdparty/commons-cli-1.2.jar

3rdparty/commons-codec-1.10.jar

3rdparty/commons-collections-3.2.1.jar

3rdparty/commons-compiler-2.7.6.jar

3rdparty/commons-compress-1.4.1.jar

3rdparty/commons-configuration-1.6.jar

3rdparty/commons-dbcp-1.4.jar

3rdparty/commons-digester-1.8.1.jar

3rdparty/commons-httpclient-3.1.jar

3rdparty/commons-io-2.4.jar

3rdparty/commons-lang-2.6.jar

3rdparty/commons-lang3-3.1.jar

3rdparty/commons-math-2.2.jar

3rdparty/commons-math3-3.1.1.jar

3rdparty/commons-net-3.6.jar

3rdparty/commons-pool-1.5.4.jar

3rdparty/commons-pool2-2.1.jar

3rdparty/commons-validator-1.4.1.jar

3rdparty/config-1.0.0.jar

3rdparty/converter-jackson-2.1.0.jar

3rdparty/curator-client-2.7.1.jar

3rdparty/curator-framework-2.7.1.jar

3rdparty/curator-recipes-2.7.1.jar

3rdparty/curator-x-discovery-2.7.1.jar

3rdparty/datanucleus-api-jdo-3.2.6.jar

3rdparty/datanucleus-core-3.2.10.jar

3rdparty/datanucleus-rdbms-3.2.9.jar

3rdparty/de.huxhorn.lilith.data.converter-0.9.44.jar

3rdparty/de.huxhorn.lilith.data.eventsource-0.9.44.jar

3rdparty/de.huxhorn.lilith.data.logging-0.9.44.jar

3rdparty/de.huxhorn.lilith.data.logging.protobuf-0.9.44.jar

3rdparty/de.huxhorn.lilith.logback.appender.multiplex-classic-0.9.44.jar

3rdparty/de.huxhorn.lilith.logback.appender.multiplex-core-0.9.44.jar

3rdparty/de.huxhorn.lilith.logback.classic-0.9.44.jar

3rdparty/de.huxhorn.lilith.logback.converter-classic-0.9.44.jar

3rdparty/de.huxhorn.lilith.sender-0.9.44.jar

3rdparty/de.huxhorn.sulky.codec-0.9.17.jar

3rdparty/de.huxhorn.sulky.formatting-0.9.17.jar

3rdparty/de.huxhorn.sulky.io-0.9.17.jar

3rdparty/derby-driver.jar

3rdparty/disruptor-3.3.0.jar

3rdparty/dom4j-1.6.1.jar

3rdparty/eigenbase-properties-1.1.5.jar

3rdparty/esri-geometry-api-2.0.0.jar

3rdparty/findbugs-annotations-1.3.9-1.jar

3rdparty/foodmart-data-json-0.4.jar

3rdparty/freemarker-2.3.26-incubating.jar

3rdparty/gson-2.2.4.jar

3rdparty/guava-18.0.jar

3rdparty/hadoop-annotations-2.7.1.jar

3rdparty/hadoop-auth-2.7.1.jar

3rdparty/hadoop-aws-2.7.1.jar

3rdparty/hadoop-client-2.7.1.jar

3rdparty/hadoop-common-2.7.1.jar

3rdparty/hadoop-hdfs-2.7.1.jar

3rdparty/hadoop-mapreduce-client-app-2.7.1.jar

3rdparty/hadoop-mapreduce-client-common-2.7.1.jar

3rdparty/hadoop-mapreduce-client-core-2.7.1.jar

3rdparty/hadoop-mapreduce-client-jobclient-2.7.1.jar

3rdparty/hadoop-mapreduce-client-shuffle-2.7.1.jar

3rdparty/hadoop-yarn-client-2.7.1.jar

3rdparty/hadoop-yarn-common-2.7.1.jar

3rdparty/hadoop-yarn-server-common-2.7.1.jar

3rdparty/hamcrest-core-1.3.jar

3rdparty/hbase-annotations-1.1.3.jar

3rdparty/hbase-client-1.1.3.jar

3rdparty/hbase-common-1.1.3.jar

3rdparty/hbase-common-1.1.3-tests.jar

3rdparty/hbase-hadoop2-compat-1.1.3.jar

3rdparty/hbase-hadoop-compat-1.1.3.jar

3rdparty/hbase-prefix-tree-1.1.3.jar

3rdparty/hbase-procedure-1.1.3.jar

3rdparty/hbase-protocol-1.1.3.jar

3rdparty/hbase-server-1.1.3.jar

3rdparty/hive-contrib-1.2.1.jar

3rdparty/hive-exec-2.1.1-mapr-1707-c25ea1308fbe694dcd8067f0b439c08d8a46eff2e3b59d46d5de5d15d39a37ba.jar

3rdparty/hive-hbase-handler-1.2.1.jar

3rdparty/hive-metastore-1.2.1.jar

3rdparty/hppc-0.7.1.jar

3rdparty/htrace-core-3.1.0-incubating.jar

3rdparty/httpclient-4.2.5.jar

3rdparty/httpcore-4.2.4.jar

3rdparty/httpdlog-parser-2.4.jar

3rdparty/interface-annotations-1.3.0.jar

3rdparty/jackson-annotations-2.7.9.jar

Apache Phoenix integration

2018-02-01 Thread Flavio Pompermaier

Hi all,
looking at https://drill.apache.org/docs/apache-drill-contribution-ideas/
it seems that Apache Phoenix is not integrated with Drill right now. In
theory the integration should be quite straightforward using the JDBC
Phoenix connector, isn't it?
Right now there are just a few problem of class loading when putting the
phoenix jar into jars/3rdparty but it shouldn't be too hard to shade
conflicting classes away.

Has anyone attempted to connect to to Apache before?

Best,
Flavio

Re: Drill 1.12 and OpenTSDB

2018-02-01 Thread Sanel Zukan

Thanks!

Best,
Sanel

Arina Yelchiyeva  writes:
> Hi Sanel,
>
> this is a bug. Fix was prepared and will be merged soon into the master.
>
> [1] https://issues.apache.org/jira/browse/DRILL-6119
> [2] https://github.com/apache/drill/pull/1102
>
> Kind regards
> Arina
>
> On Thu, Feb 1, 2018 at 3:56 PM, Sanel Zukan  wrote:
>
>> Hi,
>>
>> I've noticed that 1.12 version got support for OpenTSDB storage plugin,
>> but I'm still failing to register it.
>>
>> Here are the steps I've tried:
>>
>> 1. Run it with local zookeeper: bin/sqlline -u jdbc:drill:zk=local
>> 2. From http://drill.apache.org/blog/2017/12/15/drill-1.12-released/ I
>> tried to register plugin in Storage tab with this code:
>>
>>   {
>>"storage": {
>>  openTSDB: {
>>type: "openTSDB",
>>connection: "http://localhost:1;,
>>enabled: false
>> }
>>  }
>>}
>>
>> It failed with: "Please retry: error (invalid JSON mapping)". I also
>> looked in existing plugins configuration, and tried with this:
>>
>>   {
>> "type": "openTSDB",
>> "connection": "http://localhost:1;,
>> "enabled": false
>>   }
>>
>> which also failed with "Please retry: error (invalid JSON mapping)".
>>
>> In apache-drill-1.12.0/jars folder, I see these storage plugins:
>>
>>   drill-storage-kafka-1.12.0.jar
>>   drill-storage-hbase-1.12.0.jar
>>   drill-jdbc-storage-1.12.0.jar
>>   drill-storage-hive-core-1.12.0.jar
>>   drill-kudu-storage-1.12.0.jar
>>   drill-mongo-storage-1.12.0.jar
>>
>> Also, grepping through jars I can't find any of classes from
>> org.apache.drill.exec.store.openTSDB package. Is OpenTSDB plugin
>> (un)intentionally left from release tarball or the cause could be
>> something else?
>>
>> Thanks,
>> Sanel
>>

Re: Drill 1.12 and OpenTSDB

2018-02-01 Thread Arina Yelchiyeva

Hi Sanel,

this is a bug. Fix was prepared and will be merged soon into the master.

[1] https://issues.apache.org/jira/browse/DRILL-6119
[2] https://github.com/apache/drill/pull/1102

Kind regards
Arina

On Thu, Feb 1, 2018 at 3:56 PM, Sanel Zukan  wrote:

> Hi,
>
> I've noticed that 1.12 version got support for OpenTSDB storage plugin,
> but I'm still failing to register it.
>
> Here are the steps I've tried:
>
> 1. Run it with local zookeeper: bin/sqlline -u jdbc:drill:zk=local
> 2. From http://drill.apache.org/blog/2017/12/15/drill-1.12-released/ I
> tried to register plugin in Storage tab with this code:
>
>   {
>"storage": {
>  openTSDB: {
>type: "openTSDB",
>connection: "http://localhost:1;,
>enabled: false
> }
>  }
>}
>
> It failed with: "Please retry: error (invalid JSON mapping)". I also
> looked in existing plugins configuration, and tried with this:
>
>   {
> "type": "openTSDB",
> "connection": "http://localhost:1;,
> "enabled": false
>   }
>
> which also failed with "Please retry: error (invalid JSON mapping)".
>
> In apache-drill-1.12.0/jars folder, I see these storage plugins:
>
>   drill-storage-kafka-1.12.0.jar
>   drill-storage-hbase-1.12.0.jar
>   drill-jdbc-storage-1.12.0.jar
>   drill-storage-hive-core-1.12.0.jar
>   drill-kudu-storage-1.12.0.jar
>   drill-mongo-storage-1.12.0.jar
>
> Also, grepping through jars I can't find any of classes from
> org.apache.drill.exec.store.openTSDB package. Is OpenTSDB plugin
> (un)intentionally left from release tarball or the cause could be
> something else?
>
> Thanks,
> Sanel
>

Drill 1.12 and OpenTSDB

2018-02-01 Thread Sanel Zukan

Hi,

I've noticed that 1.12 version got support for OpenTSDB storage plugin,
but I'm still failing to register it.

Here are the steps I've tried:

1. Run it with local zookeeper: bin/sqlline -u jdbc:drill:zk=local
2. From http://drill.apache.org/blog/2017/12/15/drill-1.12-released/ I
tried to register plugin in Storage tab with this code:

  {
   "storage": {
 openTSDB: {
   type: "openTSDB",
   connection: "http://localhost:1;,
   enabled: false
}
 }
   }

It failed with: "Please retry: error (invalid JSON mapping)". I also
looked in existing plugins configuration, and tried with this:

  {
"type": "openTSDB",
"connection": "http://localhost:1;,
"enabled": false
  }

which also failed with "Please retry: error (invalid JSON mapping)".

In apache-drill-1.12.0/jars folder, I see these storage plugins:

  drill-storage-kafka-1.12.0.jar
  drill-storage-hbase-1.12.0.jar
  drill-jdbc-storage-1.12.0.jar
  drill-storage-hive-core-1.12.0.jar
  drill-kudu-storage-1.12.0.jar
  drill-mongo-storage-1.12.0.jar

Also, grepping through jars I can't find any of classes from
org.apache.drill.exec.store.openTSDB package. Is OpenTSDB plugin
(un)intentionally left from release tarball or the cause could be
something else?

Thanks,
Sanel

RE: Apache Phoenix integration

Re: Fw: Re: drill in 10 minutes tutorial problem with osx

Re: No FileSystem for scheme: maprfs

No FileSystem for scheme: maprfs

Apache Phoenix integration

Re: Drill 1.12 and OpenTSDB

Re: Drill 1.12 and OpenTSDB

Drill 1.12 and OpenTSDB

8 matches

Site Navigation

Mail list logo

Footer information