AFAICS, there is no easy way to do this so that the user of the Spring Data Cassandra schema is completely encapsulated from the fact that it's derived from the Spring Cassandra schema.
Solution for now is to simply have two schema files, one for SC & one for SDC, and maintain them in parallel. A future build enhancement could generate the two schema documents (via an XSLT or similar) so that there is no duplication in the source
spring-projects-issues commentedDec 11, 2013
David Webb opened DATACASS-54 and commented
Create the XML Namespace for spring-data-cassandra and reuse the schema from spring-cassandra where applicable
Affects: 1.0 M1 (Dijkstra)
Issue Links:
("is duplicated by")
Referenced from: commits df990d2
The text was updated successfully, but these errors were encountered: