Uh oh!
There was an error while loading. Please reload this page.
MapR 4 Profile corrected, Added Apache Drill Interpreter - #110
Conversation
pfcurtis
commented
Jun 19, 2015
- Corrected the "mapr4" profile to correctly pull the Maven artifacts from the MapR Maven repository. Added the MapR Maven repo to the POM.
- Added an Apache Drill interpreter. This interpreter requires the builder to obtain the Apache Drill JDBC and add it to their local Maven repository prior to building. This will incorporate the Drill JDBC driver into the build-dist profile
Conflicts: pom.xml
…aven repo, so it must be add to the local repo before building like so: mvn install:install-file -Dfile=<absolute_path_to_jdbc_jar>/drill-jdbc-all-1.0.0-mapr-r1.jar -DgroupId=org.apache.drill -DartifactId=drill-jdbc-all -Dversion=1.0.0-mapr-r1 -Dpackaging=jar
Leemoonsoo
commented
Jun 20, 2015
Thanks for making pullrequest! It looks like org.apache.drill:drill-jdbc-all:jar:1.0.0-mapr-r1 is not published in any maven repository that's why build is failing. How do you usually use drill-jdbc driver? download from some package? Another one is, could you explain little bit about |
pfcurtis
commented
Jun 20, 2015
On 6/20/15 6:44 PM, Lee moon soo wrote:
Regards, |
pfcurtis
commented
Jul 2, 2015
I've removed the incorrect POM file that was created during packaging. |
Leemoonsoo
commented
Jul 3, 2015
@pfcurtis |
pfcurtis
commented
Jul 3, 2015
pfcurtis
commented
Jul 9, 2015
Fetched the upstream master and checked that everything still compiles and executes properly. I think this (and the Drill interpreter) are ready to merge. The Drill JDBC will be in the Apache public repo with this newly released Drill version 1.1. |
Leemoonsoo
commented
Jul 9, 2015
Thanks. if adding a basic unittest is not too difficult, can we have one? If the test facilities can be run without any external dependency, can we have one basic unittest? So later, anyone can simply add more test to this interpreter module when there're some problem. |
JohnOmernik
commented
Sep 21, 2015
I would be interested in seeing this merged! |
jongyoul
commented
Sep 22, 2015
It would be better to split this PR to two separate issues of drill interpreter and MapR profile. |
bzz
commented
Sep 23, 2015
+1 for splitting. @walterdalton which part are you interested in particular? |
pfcurtis
commented
Sep 23, 2015
@walterdalton: I agree. Let me split this into two pull requests. The reason the Apache Drill PR hasn't been merged is I haven't had the time to build out unit tests. |
JohnOmernik
commented
Oct 15, 2015
I'd love to see both parts merged actually, I'd love to start hitting drill with Zeppelin AND I am running MapR :) |
pfcurtis
commented
Oct 15, 2015
I think it is a good idea to split the profiles from the Drill interpreter. As the Drill interpreter is simply a JDBC connection, that should be almost no effort to maintain. The MapR profiles just need to be kept up-to-date. Regards. ----- Original Message ----- I'd love to see both parts merged actually, I'd love to start hitting drill with Zeppelin AND I am running MapR :) Reply to this email directly or view it on GitHub: |
JohnOmernik
commented
Oct 24, 2015
Any further update or beer I could buy someone to get this merged in? :) |
jongyoul
commented
Oct 25, 2015
pfcurtis
commented
Oct 25, 2015
I will rework the pull request for the MapR profiles, and drop the code paul On 10/25/15 8:57 AM, Jongyoul Lee wrote:
|
jongyoul
commented
Oct 25, 2015
@pfcurtis Sounds great!! Thanks!! |
Leemoonsoo
commented
Oct 26, 2015
pfcurtis
commented
Oct 30, 2015
I'm closing this pull request, and re-opening a new one with only the MapR profile updates. |