I bet some throuough class cleansing can mean keeping this limit as opposed to increasing it.
I suggest the JIRA instead be someone reducing the current size by 2mb. In the past I've done this by expanding the archive and determining all the large chunks of classes that shouldn't be included. Note the current filter list at [1] and [2] needs to be continuously updated. It looks like neither have been updated since January. [1] https://github.com/apache/drill/blob/master/exec/jdbc-all/pom.xml#L280 [2] https://github.com/apache/drill/blob/master/exec/jdbc-all/pom.xml#L386 -- Jacques Nadeau CTO and Co-Founder, Dremio On Mon, Jun 6, 2016 at 6:52 AM, Arina Yelchiyeva <arina.yelchiy...@gmail.com > wrote: > Hi all! > > Drill has enforcer for drill-jdbc-all-1.7.0-SNAPSHOT.jar max size. Max size > is 20000000. > Currently on master jar size is 19956787. > 43213 bytes is left till the limit. I have exceeded this limit just with > adding a of couple of new classes. > > I am going to create Jira to update this limit. > Just wanted to know your opinion on new max size. 30000000 will be ok? > > > Kind regards > Arina >
