Uploaded image for project: 'Spring Data for Apache Cassandra'
  1. Spring Data for Apache Cassandra
  2. DATACASS-470

Move Cassandra type resolution into MappingCassandraConverter

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 3.0 RC1 (Neumann)
    • Component/s: Mapping
    • Labels:
      None
    • Last commented by a User:
      true
    • Sprint:
      Neumann RC1

      Description

      Cassandra type resolution is handled currently in CassandraMappingContext by using annotation-based configuration from BasicCassandraPersistentEntity
      and BasicCassandraPersistentProperty.

      This arrangement isn't ideal because:

      1. CassandraMappingContext requires a UserTypeResolver that uses Cassandra infrastructure to look up type
      2. CassandraCustomConversions introduces a cycle to o.s.d.cassandra.core.convert.

      We should move type resolution to CassandraConverter entirely to resolve the package cycle and to move the infrastructure dependency to a higher abstraction level.

      This change would require a switch in dependencies in CassandraSessionFactoryBean: The factory bean now uses CassandraMappingContext only to create/drop the schema. After the change, CassandraSessionFactoryBean requires CassandraConverter

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mp911de Mark Paluch
              Reporter:
              mp911de Mark Paluch
              Last updater:
              Mark Paluch
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 18 weeks, 6 days ago