The compile problem is a problem with the MapR repo (I think). I have reported it to the folks who can fix it.
Regarding the generic question, I think that Drill is very much a good choice for putting a SQL layer on a noSQL database. It is definitely the case that the community is much broader than it used to be. A number of companies now use Drill in their products which is one of the best ways to build long-term community. There are alternatives, of course. All have trade-offs (because we live in the world): - Calcite itself (what Drill uses as a SQL parser and optimizer) can be used, but you have to provide an execution framework and you wind up with something that only works for your engine and is unlikely to support parallel operations. Calcite is used by lots of projects, though, so it is has a very broad base of support. - Spark SQL is fairly easy to extend (from what I hear from friends) but the optimizer doesn't deal well with complicated tradeoffs (precisely because it is fairly simple). You also wind up with the baggage of spark which could be good or bad. You would get some parallelism, though. I don't think that Spark SQL handles complex objects, however. - Postgres has a long history of having odd things grafted onto it. I know little about this other than seeing the results. Extending Postgres would not likely give you any parallelism, but there might be a way to support complex objects through Postgres JSON object support. On Sun, May 3, 2020 at 11:09 AM Tugdual Grall <tugd...@gmail.com> wrote: > Hello > > It has been a long time since I used Drill! > > I wanted to build it to start to work on a new datasource,. > > But when run "mvn clean install", I hit the exception below. > > => Can somebody help? > > => This bring me to a generic question, if I want to expose a NoSQL > database using SQL/JDBC/ODBC for Analytics purposes, is Drill the best > option? or I should look at something else? > > > Thanks! > > ==== > [INFO] exec/Java Execution Engine ......................... FAILURE [ > 0.676 s] > > [ERROR] Failed to execute goal on project drill-java-exec: Could not > resolve dependencies > for project org.apache.drill.exec:drill-java-exec:jar:1.18.0-SNAPSHOT: > Failed to collect dependencies at org.kohsuke:libpam4j:jar:1.8-rev2: Failed > to read artifact descriptor for org.kohsuke:libpam4j:jar:1.8-rev2: Could > not transfer artifact org.kohsuke:libpam4j:pom:1.8-rev2 from/to > mapr-releases (http://repository.mapr.com/maven/): Transfer failed for > > http://repository.mapr.com/maven/org/kohsuke/libpam4j/1.8-rev2/libpam4j-1.8-rev2.pom > 500 Proxy Error -> [Help 1] > [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/DependencyResolutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <args> -rf :drill-java-exec >
