Hi Bob, You can actually build your storage plugin outside of drill, package it using maven, then copy the resultant JAR files into the <drill>/jars/3rdparty folder. Here are some examples…
https://github.com/bizreach/drill-ltsv-plugin <https://github.com/bizreach/drill-ltsv-plugin> https://github.com/cgivre/drill-logfile-plugin <https://github.com/cgivre/drill-logfile-plugin> IMHO this is much easier than trying to rebuild Drill every time you need to rebuild. Best, — C > On Aug 3, 2017, at 13:29, Bob Rudis <[email protected]> wrote: > > Hey folks, > > First: > > Inspired by the PCAP support in 1.11.0 I started down the path of > cloning drill and just doing a test build before I started looking at > 2 of the issues I posted for the PCAP storage format and also working > to incorporate a similar WARC plugin (via the jwat jars). > > `mvn package -DskipTests` works fine but `mvn install -DskipTests` generates: > > Found Banned Dependency: log4j:log4j:jar:1.2.17 > Found Banned Dependency: commons-logging:commons-logging:jar:1.1.1 > > warnings which causes: > > Apache Drill Root POM .............................. FAILURE > > and (hence) the overall build to fail. > > I'm hoping that I'm just missing something obvious after some failed googling. > > > Second: > > Is there a way to develop the WARC format plugin outside of > Drill-source-proper vs having to build into it. If so, is there a > small, example GH repo someone cld point me to (that also has the "how > to get it into Drill" part). From a scan of the source, it looks like > the formats are embedded into a few source files in the > Drill-source-proper. If there's no way to develop one outside of it, > that's not a problem, I just figured it'd be easier to do it outside > of modifying Drill source first. > > thx, > > -Bob
