Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-3428

Fix log4j configuration errors when running hive on hadoop23

Log workAgile BoardRank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.10.0
    • 0.11.0
    • None
    • None

    Description

      There are log4j configuration errors when running hive on hadoop23, some of them may fail testcases, since the following log4j error message could printed to console, or to output file, which diffs from the expected output:

      [junit] < log4j:ERROR Could not find value for key log4j.appender.NullAppender
      [junit] < log4j:ERROR Could not instantiate appender named "NullAppender".
      [junit] < 12/09/04 11:34:42 WARN conf.HiveConf: hive-site.xml not found on CLASSPATH

      Attachments

        1. HIVE-3428.1.D8805.patch
          7 kB
          Gunther Hagleitner
        2. HIVE-3428_SHIM_EVENT_COUNTER.patch
          7 kB
          Gunther Hagleitner
        3. HIVE-3428.6.patch.txt
          36 kB
          Zhenxiao Luo
        4. HIVE-3428.5.patch.txt
          36 kB
          Zhenxiao Luo
        5. HIVE-3428.4.patch.txt
          35 kB
          Zhenxiao Luo
        6. HIVE-3428.3.patch.txt
          35 kB
          Zhenxiao Luo
        7. HIVE-3428.2.patch.txt
          9 kB
          Zhenxiao Luo
        8. HIVE-3428.1.patch.txt
          5 kB
          Zhenxiao Luo

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            hagleitn Gunther Hagleitner Assign to me
            zhenxiao Zhenxiao Luo
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment