Uploaded image for project: 'Apache Gora'
  1. Apache Gora
  2. GORA-257

Use separate class loaders for each module

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 1.0
    • gora-core, maven, storage
    • None

    Description

      Some modules require conflicting versions of dependent libraries. For example, HBase and Solr require conflicting versions of the Zookeeper client library. In order to use both stores in the same VM they should each load and use their own version of the library. Decoupling the module dependencies from the core of Gora allows for independent versioning as well as multiple versions.

      To accomplish this, each module needs its own class loader. I think this could be done in one of two places: Either Gora core creates the class loader and assigns it to a module, or each module starts with a pared-down class with no external library dependencies and creates a class loader for the rest.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sstults Scott Stults
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: