Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-701

New JDBC CacheStore implementation w/ more flexible vendor-specific extension and binary key column support

    XMLWordPrintable

Details

    Description

      The current JDBC CacheStore implementation has the following shortcomings:

      • poor support for vendor specific queries (e.g. MySQL's replace into)
      • complex configuration is required to support the key types that cannot be converted to a String easily.

      To address this issue:

      • Introduce a single unified JDBC CacheStore implementation.
      • Support an arbitrary key type as long as it can be serialized via Marshaller.
      • Support both text and binary key.
      • Encode the binary key into a text key using an efficient text encoding if the target database doesn't support binary key column.
      • Provide much more flexibility in supporting vendor specific extensions. Let the user extend our CacheStore implementation and override the DB access (no more TableManipulation).

      Once implemented, the existing JDBC CacheStore could be deprecated.

      Configuring this would be, for example, GenericJdbcCacheStore which would have no vendor-specific optimisations, and MySqlJdbcCacheStore (subclasses GenericJdbcCacheStore) which would contain MySQL specific optimisations, etc.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. ISPN-686 JdbcStringBasedCacheStore loads previous data from store before an insert

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ISPN-965 Query for loading some rows from CacheStore is not correct for HSQLDB 1.8.0.7

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-20 check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ISPN-1592 Jdbc binary cache store throwing conversion error when working with Sybase DB

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2082 JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-1204 Make JDBC cache store use implicit schemas for database tables

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              remerson@redhat.com Ryan Emerson
              trustin_jira Trustin Lee (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: