Uploaded image for project: 'Livy'
  1. Livy
  2. LIVY-901 Livy 0.8.0 Dependency Upgrades
  3. LIVY-878

Log4j upgrade for Livy 0.8.0 version

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.8.0
    • None
    • None

    Description

      We are looking for an advise from you in context of the below mentioned issue:

       

      A high severity vulnerability (CVE-2021-44228) impacting multiple versions of the Apache Log4j 2 utility was disclosed publicly via the project’s GitHub on December 9, 2021.

      The vulnerability impacts Apache Log4j 2 versions 2.0 to 2.14.1.

       

      Apache Livy version 0.7.0 version is being used by our team for processing the spark jobs . It uses the Log4j 1.x.x. which is not having any continued support.

      We would like to upgrade the Log4j versions to the latest stable version  2.15 without having any impact on the installations .

       

      Could you please recommend the possible ways to do the upgrade .Please note , we are not looking to upgrade the Livy version to 0.7.1 to resolve this issue .

      Our requirement is to retain the current installed version and configurations with only changes in the Log4j versions  

      Attachments

        Issue Links

        Activity

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

          People

            dacort Damon Cortesi
            tinujose Tinu Jose
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 2h 50m
                2h 50m

                Slack

                  Issue deployment