Hi Vitali, so if the *commons-logging* is removed from the banned dependency, do we expect developers to use it or will we enforce through checkstyle to use the current logging library ? What are the pros/cons of using one vs the other ? Any idea why it was in the banned dependency earlier ?
Aman On Wed, Apr 3, 2019 at 1:03 AM Arina Yelchiyeva <[email protected]> wrote: > Looks like we don’t have much of a choice if we want to support Hadoop 3. > > Kind regards, > Arina > > > On Apr 2, 2019, at 7:40 PM, Vitalii Diravka <[email protected]> wrote: > > > > Hi devs! > > > > I am working on the update of Hadoop libs to the 3.2.0 version [1]. > > I found the issue in *hadoop-common* related to several loggers in the > > project [2], [3]. > > So to update the version of hadoop libs in Drill it is necessary to > remove > > *commons-logging* from banned dependencies [4]. > > After doing it I didn't find conflicts between two logger libs in Drill. > > > > Is this solution acceptable? > > It can be temporary until [3] is fixed. > > > > > > > > [1] https://issues.apache.org/jira/browse/DRILL-6540 > > [2] > > > https://issues.apache.org/jira/browse/DRILL-6540?focusedCommentId=16606306&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16606306 > > [3] https://issues.apache.org/jira/browse/HADOOP-15749 > > [4] https://github.com/apache/drill/blob/master/pom.xml#L522 > > > > > > Kind regards > > Vitalii >
