You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/07/23 19:06:00 UTC

[jira] [Created] (FLINK-18697) Adding flink-table-api-java-bridge_2.11 to a Flink job kills the IDE logging

Robert Metzger created FLINK-18697:
--------------------------------------

             Summary: Adding flink-table-api-java-bridge_2.11 to a Flink job kills the IDE logging
                 Key: FLINK-18697
                 URL: https://issues.apache.org/jira/browse/FLINK-18697
             Project: Flink
          Issue Type: Bug
          Components: Table SQL / API
    Affects Versions: 1.11.0
            Reporter: Robert Metzger


Steps to reproduce:
- Set up a Flink project using a Maven archetype
- Add "flink-table-api-java-bridge_2.11" as a dependency
- Running Flink won't produce any log output

Probable cause:
"flink-table-api-java-bridge_2.11" has a dependency to "org.apache.flink:flink-streaming-java_2.11:test-jar:tests:1.11.0", which contains a "log4j2-test.properties" file.

When I disable Log4j2 debugging (with "-Dlog4j2.debug"), I see the following line:
{code}
DEBUG StatusLogger Reconfiguration complete for context[name=3d4eac69] at URI jar:file:/Users/robert/.m2/repository/org/apache/flink/flink-streaming-java_2.11/1.11.0/flink-streaming-java_2.11-1.11.0-tests.jar!/log4j2-test.properties (org.apache.logging.log4j.core.LoggerContext@568bf312) with optional ClassLoader: null
{code}





--
This message was sent by Atlassian Jira
(v8.3.4#803005)