Cassandra type resolution is handled currently in CassandraMappingContext by using annotation-based configuration from BasicCassandraPersistentEntity
This arrangement isn't ideal because:
- CassandraMappingContext requires a UserTypeResolver that uses Cassandra infrastructure to look up type
- 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