Apache Drill allows querying with sq. against a mess of data assets, consisting of JSON documents, Parquet and Avro, Hive tables, RDBMS, and more. MapR has launched an ODBC driving force for it, and that i idea it'd be neat to get it to paintings with OBIEE. It obviously does work for OBIEE walking on windows, however I desired for you to apply it to my trendy environment, Linux.
For greater data on Apache Drill, see my previous put up, creation to Apache Drill.
OBIEE 12c (and 11g and 10g earlier than it) helps three primary methods of connecting to facts assets:
Local Gateway, consisting of OCI for Oracle. this is constantly the preferred choice, as it offers the finest help and performance.
facts Direct ODBC Drivers, a fixed of that are bundled with OBIA for allowing connectivity to sources which includes sq. Server, MySQL, Hive, and Impala. The configuration of these is documented in the OBIEE manuals, and is generally a supported configuration.
local ODBC Drivers.
To get OBIEE to paintings with Apache Drill, we're going to use the third choice - native ODBC drivers. i'm doing this on SampleApp v511. For a geek-out on information of the technique I went through and diagnostics used to get this to work, see here.
_Update: Fiston has written up an incredible weblog submit displaying how JDBC can be used to connect OBIEE 12c to Apache Drill - very cool!_
First matters First - setting up Apache Drill
Drill can be deployed in allotted configuration (with all the parallel processing goodness which that brings), but also run as a unmarried example domestically. For the sake of simplicity, that's what i am going to do right here. it is rather easy to do:
# Download Apache Drill
wget http://www.apache.org/dyn/closer.cgi/drill/drill-1.7.0/apache-drill-1.7.0.tar.gz
# Unpack
tar -xvf apache-drill-1.7.0.tar.gz
# Run
cd /opt/apache-drill-1.7.0/ && bin/sqlline -u jdbc:drill:zk=local
You need to make sure you've got a recent JDK available, and if you're running it on BigDataLite VM, watch out for this odd problem that I had which was related to classpaths and maniested itself with the error java.lang.NoSuchMethodError:
com.fasterxml.jackson.databind.JavaType.isReferenceType()Z.
All being well, you'll now have a Drill prompt:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Aug 09, 2016 5:51:43 AM org.glassfish.jersey.server.ApplicationHandler initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26...
apache drill 1.7.0
"say hello to my little drill"
0: jdbc:drill:zk=local>
From here you can run a simple query to check the version:
0: jdbc:drill:zk=local> SELECT version FROM sys.version;
+----------+
| version |
+----------+
| 1.7.0 |
+----------+
1 row selected (0.392 seconds)
or query one of the built-in sample data sets:
0: jdbc:drill:zk=local> select count(*) from cp.`employee.json`;
+---------+
| EXPR$0 |
+---------+
| 1155 |
+---------+
1 row selected (0.977 seconds)
For greater data on Apache Drill, see my previous put up, creation to Apache Drill.
OBIEE 12c (and 11g and 10g earlier than it) helps three primary methods of connecting to facts assets:
Local Gateway, consisting of OCI for Oracle. this is constantly the preferred choice, as it offers the finest help and performance.
facts Direct ODBC Drivers, a fixed of that are bundled with OBIA for allowing connectivity to sources which includes sq. Server, MySQL, Hive, and Impala. The configuration of these is documented in the OBIEE manuals, and is generally a supported configuration.
local ODBC Drivers.
To get OBIEE to paintings with Apache Drill, we're going to use the third choice - native ODBC drivers. i'm doing this on SampleApp v511. For a geek-out on information of the technique I went through and diagnostics used to get this to work, see here.
_Update: Fiston has written up an incredible weblog submit displaying how JDBC can be used to connect OBIEE 12c to Apache Drill - very cool!_
First matters First - setting up Apache Drill
Drill can be deployed in allotted configuration (with all the parallel processing goodness which that brings), but also run as a unmarried example domestically. For the sake of simplicity, that's what i am going to do right here. it is rather easy to do:
# Download Apache Drill
wget http://www.apache.org/dyn/closer.cgi/drill/drill-1.7.0/apache-drill-1.7.0.tar.gz
# Unpack
tar -xvf apache-drill-1.7.0.tar.gz
# Run
cd /opt/apache-drill-1.7.0/ && bin/sqlline -u jdbc:drill:zk=local
You need to make sure you've got a recent JDK available, and if you're running it on BigDataLite VM, watch out for this odd problem that I had which was related to classpaths and maniested itself with the error java.lang.NoSuchMethodError:
com.fasterxml.jackson.databind.JavaType.isReferenceType()Z.
All being well, you'll now have a Drill prompt:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Aug 09, 2016 5:51:43 AM org.glassfish.jersey.server.ApplicationHandler initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29 01:25:26...
apache drill 1.7.0
"say hello to my little drill"
0: jdbc:drill:zk=local>
From here you can run a simple query to check the version:
0: jdbc:drill:zk=local> SELECT version FROM sys.version;
+----------+
| version |
+----------+
| 1.7.0 |
+----------+
1 row selected (0.392 seconds)
or query one of the built-in sample data sets:
0: jdbc:drill:zk=local> select count(*) from cp.`employee.json`;
+---------+
| EXPR$0 |
+---------+
| 1155 |
+---------+
1 row selected (0.977 seconds)
No comments:
Post a Comment