Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-6272

the JDBC connector should use PDX instances instead of JSON for composite keys

    XMLWordPrintableJSON

    Details

      Description

      As a GemFire user with composite keys
      I want to to replace JSON with PDX for these keys
      so that I can support any order for the keys and have minimal memory impact.


      Acceptance Criteria:
      Given a jdbc-mapping uses a composite key
      When I do CRUD operations on data in the region
      Then I must specify the key as a "stable" PDX instance that contains fields that match those specified by --id.

      Given an existing cache with a jdbc-mapping that uses a composite key
      When I want to specify a composite key for a CRUD operation
      Then I have a method on the cache to create a "stable" PDX instance.

      Given an existing cache with a jdbc-mapping that uses a composite key
      When I want to specify a composite key for a CRUD operation
      Then I have a method on the cache to create a "stable" PDX instance and the order of fields in the composite key doesn't matter.

      Given an existing cache with pdx-read-serialized is set to false
      When I do an operation that triggers deserialization of a "stable" PDX instance
      Then the "stable" PDX instance will be deserialized as the same "stable" PDX instance.

      Given a "stable" PDX instance
      When I call its getObject method
      Then it will return the same "stable" PDX instance.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dschneider Darrel Schneider
                Reporter:
                dschneider Darrel Schneider
              • Votes:
                0 Vote for this issue
                Watchers:
                2 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 - 1h 50m
                  1h 50m