Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-6996

Change javax.cache library implementation from JSR107 to Apache Geronimo

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 3.0.0-beta1
    • 2.9.0, 3.0.0-beta1
    • None
    • None
    • Reviewed

    Description

      With YARN Federation, we added YARN-3672, which adds the following to

          <groupId>javax.cache</groupId>
          <artifactId>cache-api</artifactId>
      

      This third-party library has some murky license history, as documented in this really long comment thread. The summary of the thread is that "the library is officially APL (take our word for it), but there hasn't been a subsequent release with the license file change".

      LEGAL-325 has been filed to discuss the validity of this license for Apache.

      Before we get to final Hadoop 3 release, I'm wondering if anyone else has concerns about using this library. Just from looking at the various javax Maven artifacts in our pom.xml files, I see a lot of other javax.* library entries (although we may not ship the .jars if they're part of the Java runtime).

      Attachments

        1. YARN-6996.001.patch
          2 kB
          Ray Chiang

        Issue Links

        Activity

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

          People

            rchiang Ray Chiang
            rchiang Ray Chiang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment