The Drill project uses Apache maven as the build tool. The project has been split up into a number of separate maven modules to isolate the various components and plugins.
The artifactId is the name that is used as the name of the output of the build.
In general the new name of an artifact should follow the pattern of drill-<what>-<kind> So a format plugin for something should become drill-something-storage
If a module is really just a combination of other modules then let the name end with -parent and the module must be <packaging>pom</packaging>.
To ensure the build remains readable for the developers building the system we want to have the module show a name that is easy to read and easy to understand which part of the project is being built.
When creating a new module please make sure the new module has a name that follows the pattern shown in the other modules.
Some basic patterns of those names:
Drill : :pom module name ends with :jar module name ends with the name of that module.Please make sure the names are concise, unique and easy to read.
The file drill-jdbc-all-${project.version}.jar is outside the expected size range. This is likely due to you adding new dependencies to a java-exec and not updating the excludes in this module. This is important as it minimizes the size of the dependency of Drill application users.
The maxsize of the jar can be configured via jdbc-all-jar.maxsize property in drill-jdbc-all
To check the full list of Maven profiles:
mvn help:all-profiles
To check the list of active Maven profiles:
mvn help:active-profiles
To run Apache Drill on the Hadoop2 cluster r2.4.1-r2.9.2 need to prepare the Drill distribution by building the project with hadoop-2 profile:
mvn clean install -Phadoop-2
or
mvn clean install -P hadoop-2