Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-14119

Default JSR-107 Configuration

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.9.1
    • None
    • cache
    • None
    • AWS Linux 2

    • Docs Required, Release Notes Required

    Description

      When requesting a caching provider it is difficult to configure it.

      for (final CachingProvider cachingProvider : Caching.getCachingProviders()) {
        final javax.cache.CacheManager cacheManager = cachingProvider.getCacheManager();
      ...

      The biggest issues are:

      • org.apache.ignite.cache.CacheManager defaults to a Server configuration
      • when providing a uri, Spring needs to be installed.

      Suggestion:

      in CacheManager or CachingProvider create the ability to statically set a default configuration

      • via uri for Spring (irrelevant for me)
      • via providing a default IgniteConfiguration

       

      public static void setDefaultConfiguration(IgniteConfiguration cfg) {
        s_defaultConfiguration = cfg;
      }
      private static IgniteConfiguration s_defaultConfiguration;
      
      // and in the constructor of CacheManager
      IgniteConfiguration cfg = s_defaultConfiguration == null ? new IgniteConfiguration() : s_defaultConfiguration;
      
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            jorg.janke@accorto.com Jorg Janke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: