[jira] [Updated] (DRILL-6800) Simplify packaging of Jdbc-all jar
[ https://issues.apache.org/jira/browse/DRILL-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Turton updated DRILL-6800: Fix Version/s: (was: 1.21.0) > Simplify packaging of Jdbc-all jar > -- > > Key: DRILL-6800 > URL: https://issues.apache.org/jira/browse/DRILL-6800 > Project: Apache Drill > Issue Type: Improvement > Components: Client - JDBC >Reporter: Sorabh Hamirwasia >Priority: Major > Fix For: Future > > > Today Jdbc-all package is created using drill-java-exec as dependency and > then excluding unnecessary dependency. Also there is size check for jdbc-all > jar to avoid including any unwanted dependency. But configured size has > increased over time and doesn't really provide a good mechanism to enforce > small footprint of jdbc-all jar. Following are some recommendation to improve > it: > 1) Divide java-exec module into separate client/server and common module > 2) Have size check for client artifact only. > 3) Update jdbc-all pom to include newly created client artifact and jdbc > driver artifact. > * Have multiple profiles to include and exclude any profile specific > dependency. For > example MapR profile will exclude hadoop dependency whereas apache profile > will > include it. > * We can create 2 artifacts for jdbc-all: one with and other without (for > smaller jar size) Hadoop dependencies. > 4) Update client side protobuf to not have server side definitions like > QueryProfile / CoreOperatorType etc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (DRILL-6800) Simplify packaging of Jdbc-all jar
[ https://issues.apache.org/jira/browse/DRILL-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua updated DRILL-6800: Fix Version/s: 2.0.0 Future > Simplify packaging of Jdbc-all jar > -- > > Key: DRILL-6800 > URL: https://issues.apache.org/jira/browse/DRILL-6800 > Project: Apache Drill > Issue Type: Improvement > Components: Client - JDBC >Reporter: Sorabh Hamirwasia >Priority: Major > Fix For: Future, 2.0.0 > > > Today Jdbc-all package is created using drill-java-exec as dependency and > then excluding unnecessary dependency. Also there is size check for jdbc-all > jar to avoid including any unwanted dependency. But configured size has > increased over time and doesn't really provide a good mechanism to enforce > small footprint of jdbc-all jar. Following are some recommendation to improve > it: > 1) Divide java-exec module into separate client/server and common module > 2) Have size check for client artifact only. > 3) Update jdbc-all pom to include newly created client artifact and jdbc > driver artifact. > * Have multiple profiles to include and exclude any profile specific > dependency. For > example MapR profile will exclude hadoop dependency whereas apache profile > will > include it. > * We can create 2 artifacts for jdbc-all: one with and other without (for > smaller jar size) Hadoop dependencies. > 4) Update client side protobuf to not have server side definitions like > QueryProfile / CoreOperatorType etc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6800) Simplify packaging of Jdbc-all jar
[ https://issues.apache.org/jira/browse/DRILL-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-6800: - Description: Today Jdbc-all package is created using drill-java-exec as dependency and then excluding unnecessary dependency. Also there is size check for jdbc-all jar to avoid including any unwanted dependency. But configured size has increased over time and doesn't really provide a good mechanism to enforce small footprint of jdbc-all jar. Following are some recommendation to improve it: 1) Divide java-exec module into separate client/server and common module 2) Have size check for client artifact only. 3) Update jdbc-all pom to include newly created client artifact and jdbc driver artifact. * Have multiple profiles to include and exclude any profile specific dependency. For example MapR profile will exclude hadoop dependency whereas apache profile will include it. * We can create 2 artifacts for jdbc-all: one with and other without (for smaller jar size) Hadoop dependencies. 4) Update client side protobuf to not have server side definitions like QueryProfile / CoreOperatorType etc was: Today Jdbc-all package is created using drill-java-exec as dependency and then excluding unnecessary dependency. Also there is size check for jdbc-all jar to avoid including any unwanted dependency. But configured size has increased over time and doesn't really provide a good mechanism to enforce small footprint of jdbc-all jar. Following are some recommendation to improve it: 1) Divide java-exec module into separate client/server and common module 2) Have size check for client artifact only. 3) Update jdbc-all pom to include newly created client artifact and jdbc driver artifact. * Have multiple profiles to include and exclude any profile specific dependency. For example MapR profile will exclude hadoop dependency whereas apache profile will include it. * We can create 2 artifacts for jdbc-all: one with and other without (for smaller jar size) Hadoop dependencies. 4) Update client side protobuf to not have server side definitions. > Simplify packaging of Jdbc-all jar > -- > > Key: DRILL-6800 > URL: https://issues.apache.org/jira/browse/DRILL-6800 > Project: Apache Drill > Issue Type: Improvement > Components: Client - JDBC >Reporter: Sorabh Hamirwasia >Priority: Major > > Today Jdbc-all package is created using drill-java-exec as dependency and > then excluding unnecessary dependency. Also there is size check for jdbc-all > jar to avoid including any unwanted dependency. But configured size has > increased over time and doesn't really provide a good mechanism to enforce > small footprint of jdbc-all jar. Following are some recommendation to improve > it: > 1) Divide java-exec module into separate client/server and common module > 2) Have size check for client artifact only. > 3) Update jdbc-all pom to include newly created client artifact and jdbc > driver artifact. > * Have multiple profiles to include and exclude any profile specific > dependency. For > example MapR profile will exclude hadoop dependency whereas apache profile > will > include it. > * We can create 2 artifacts for jdbc-all: one with and other without (for > smaller jar size) Hadoop dependencies. > 4) Update client side protobuf to not have server side definitions like > QueryProfile / CoreOperatorType etc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6800) Simplify packaging of Jdbc-all jar
[ https://issues.apache.org/jira/browse/DRILL-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sorabh Hamirwasia updated DRILL-6800: - Description: Today Jdbc-all package is created using drill-java-exec as dependency and then excluding unnecessary dependency. Also there is size check for jdbc-all jar to avoid including any unwanted dependency. But configured size has increased over time and doesn't really provide a good mechanism to enforce small footprint of jdbc-all jar. Following are some recommendation to improve it: 1) Divide java-exec module into separate client/server and common module 2) Have size check for client artifact only. 3) Update jdbc-all pom to include newly created client artifact and jdbc driver artifact. * Have multiple profiles to include and exclude any profile specific dependency. For example MapR profile will exclude hadoop dependency whereas apache profile will include it. * We can create 2 artifacts for jdbc-all: one with and other without (for smaller jar size) Hadoop dependencies. 4) Update client side protobuf to not have server side definitions. was: Today Jdbc-all package is created using drill-java-exec as dependency and then excluding unnecessary dependency. Also there is size check for jdbc-all jar to avoid including any unwanted dependency. But configured size has increased over time and doesn't really provide a good mechanism to enforce small footprint of jdbc-all jar. Following are some recommendation to improve it: 1) Divide java-exec module into separate client/server and common module 2) Have size check for client artifact only. 3) Update jdbc-all pom to include newly created client artifact and jdbc driver artifact. * Have multiple profiles to include and exclude any profile specific dependency. For example MapR profile will exclude hadoop dependency whereas apache profile will include it. * We can create 2 artifacts for jdbc-all: one with and other without (for smaller jar size) Hadoop dependencies. 4) Update client side protobuf to not have server side definitions. > Simplify packaging of Jdbc-all jar > -- > > Key: DRILL-6800 > URL: https://issues.apache.org/jira/browse/DRILL-6800 > Project: Apache Drill > Issue Type: Improvement > Components: Client - JDBC >Reporter: Sorabh Hamirwasia >Priority: Major > > Today Jdbc-all package is created using drill-java-exec as dependency and > then excluding unnecessary dependency. Also there is size check for jdbc-all > jar to avoid including any unwanted dependency. But configured size has > increased over time and doesn't really provide a good mechanism to enforce > small footprint of jdbc-all jar. Following are some recommendation to improve > it: > 1) Divide java-exec module into separate client/server and common module > 2) Have size check for client artifact only. > 3) Update jdbc-all pom to include newly created client artifact and jdbc > driver artifact. > * Have multiple profiles to include and exclude any profile specific > dependency. For > example MapR profile will exclude hadoop dependency whereas apache profile > will > include it. > * We can create 2 artifacts for jdbc-all: one with and other without (for > smaller jar size) Hadoop dependencies. > 4) Update client side protobuf to not have server side definitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
