ASF GitHub Bot commented on DRILL-6311:

Github user ilooner commented on a diff in the pull request:

    --- Diff: exec/vector/pom.xml ---
    @@ -69,6 +69,7 @@
    +      <scope>test</scope>
    --- End diff --
    The `<classifier>tests</classifier>` tag includes the test classes in 
drill-common. The test category classes are included in 
common/src/test/java/org/apache/drill/categories. So test category classes will 
be accessible to maven. However, looks like I forgot the test scope so the test 
classes and resources from drill-common were being included in Drill's standard 
(non-test) classpath.

> No logging information in drillbit.log / drillbit.out
> -----------------------------------------------------
>                 Key: DRILL-6311
>                 URL: https://issues.apache.org/jira/browse/DRILL-6311
>             Project: Apache Drill
>          Issue Type: Bug
>          Components:  Server
>    Affects Versions: 1.14.0
>            Reporter: Sorabh Hamirwasia
>            Assignee: Sorabh Hamirwasia
>            Priority: Major
>             Fix For: 1.14.0
> On latest masterĀ 9a6cb59b9b7a5b127e5f60309ce2f506ede9652a, when running 
> Drillbit in cluster mode, there is no log prints in drillbit.log / .out file. 
> Due to the latest commit there is a change in vector/pom.xml which is adding 
> drill-common artifact and the scope is not there. Hence it'sĀ placed under 
> drillbit jar path which also contains another logback-test.xml which 
> overrides the default logback.xml inside conf directory.

This message was sent by Atlassian JIRA

Reply via email to