Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.0-alpha
    • Fix Version/s: None
    • Component/s: conf
    • Labels:
      None

      Description

      Per HADOOP-8086 hadoop-auth uses slf4j, don't see why it shouldn't use log4j to be consistent with the rest of Hadoop.

        Issue Links

          Activity

          Eli Collins created issue -
          Eli Collins made changes -
          Field Original Value New Value
          Link This issue relates to HADOOP-8086 [ HADOOP-8086 ]
          Steve Loughran made changes -
          Link This issue relates to HADOOP-9864 [ HADOOP-9864 ]
          Hide
          Steve Loughran added a comment -
          1. hadoop-auth uses the SLF4J APIs, but the back end will be whichever SJF4J back end is chosen -which on Hadoop is Log4J.
          2. As jetty depends on SLF4J the same way, and apparently avro, hadoop-auth isn't the reason that this JAR is on the classpath
          3. if we moved to SLF4J everywhere, as HADOOP-9864 proposes, we would have consistency between hadoop-auth and everything else
          Show
          Steve Loughran added a comment - hadoop-auth uses the SLF4J APIs, but the back end will be whichever SJF4J back end is chosen -which on Hadoop is Log4J. As jetty depends on SLF4J the same way, and apparently avro, hadoop-auth isn't the reason that this JAR is on the classpath if we moved to SLF4J everywhere, as HADOOP-9864 proposes, we would have consistency between hadoop-auth and everything else

            People

            • Assignee:
              Unassigned
              Reporter:
              Eli Collins
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Development