DATACASS-284 - Documentation.
This commit is contained in:
@@ -7,7 +7,7 @@ David Webb, Matthew Adams, John Blum, Mark Paluch
|
||||
:spring-data-commons-docs: ../../../../spring-data-commons/src/main/asciidoc
|
||||
:spring-framework-docs: http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/
|
||||
|
||||
(C) 2008-2017 The original author(s).
|
||||
(C) 2008-2018 The original author(s).
|
||||
|
||||
NOTE: Copies of this document may be made for your own use and for distribution to others, provided that you do not
|
||||
charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed
|
||||
|
||||
@@ -8,6 +8,7 @@ This chapter summarizes changes and new features for each release.
|
||||
* New annotations for `@CountQuery` and `@ExistsQuery`.
|
||||
* Template API extended with `count(…)` and `exists(…)` methods accepting `Query`.
|
||||
* <<cassandra.template.query.fluent-template-api,Fluent API>> for CRUD operations.
|
||||
* Cassandra Tuple support via `TupleValue`.
|
||||
|
||||
[[new-features.2-0-0]]
|
||||
== What's new in Spring Data for Apache Cassandra 2.0
|
||||
|
||||
@@ -613,7 +613,7 @@ NOTE: `SchemaAction.RECREATE`/`SchemaAction.RECREATE_DROP_UNUSED` will drop your
|
||||
|
||||
==== Enabling Tables and User-Defined Types for Schema Management
|
||||
|
||||
<<mapping.usage>> explains object mapping using conventions and annotations. Schema management is only active for entities annotated with `@Table` and user-defined types annotated with `@UserDefinedType` to prevent unwanted classes from being created as table/type. Entities are discovered by scanning the class path. Entity scanning requires one or more base packages.
|
||||
<<mapping.usage>> explains object mapping using conventions and annotations. Schema management is only active for entities annotated with `@Table` and user-defined types annotated with `@UserDefinedType` to prevent unwanted classes from being created as table/type. Entities are discovered by scanning the class path. Entity scanning requires one or more base packages. Tuple typed columns using `TupleValue` do not provide any typing details hences you must annotate such column properties with `@CassandraType(type = TUPLE, typeArguments = …)` to specify the desired column type.
|
||||
|
||||
.Specifying Entity Base Packages via XML
|
||||
====
|
||||
|
||||
@@ -73,6 +73,9 @@ for further details.
|
||||
| `java.util.UUID`
|
||||
| `timeuuid`
|
||||
|
||||
| `TupleValue`
|
||||
| `tuple<…>`
|
||||
|
||||
| `UDTValue`, mapped User-Defined Types
|
||||
| user type
|
||||
|
||||
|
||||
Reference in New Issue
Block a user