mirror of
				https://github.com/spring-projects/spring-data-elasticsearch.git
				synced 2025-10-30 14:18:46 +00:00 
			
		
		
		
	
							parent
							
								
									cdb92f6ee4
								
							
						
					
					
						commit
						ae88ea3506
					
				| @ -9,7 +9,7 @@ This section describes breaking changes from version 4.0.x to 4.1.x and how remo | |||||||
| .Definition of the id property | .Definition of the id property | ||||||
| It is possible to define a property of en entity as the id property by naming it either `id` or  `document`. | It is possible to define a property of en entity as the id property by naming it either `id` or  `document`. | ||||||
| This behaviour is now deprecated and will produce a warning. | This behaviour is now deprecated and will produce a warning. | ||||||
| PLease us the `@Id` annotation to mark a property as being the id property. | Please use the `@Id` annotation to mark a property as being the id property. | ||||||
| 
 | 
 | ||||||
| .Index mappings | .Index mappings | ||||||
| In the `ReactiveElasticsearchClient.Indices` interface the `updateMapping` methods are deprecated in favour of the `putMapping` methods. | In the `ReactiveElasticsearchClient.Indices` interface the `updateMapping` methods are deprecated in favour of the `putMapping` methods. | ||||||
| @ -44,5 +44,5 @@ With the introduction of the `ReactiveIndexOperations` it became necessary to ch | |||||||
| [[elasticsearch-migration-guide-4.0-4.1.breaking-changes.returntypes-2]] | [[elasticsearch-migration-guide-4.0-4.1.breaking-changes.returntypes-2]] | ||||||
| === Return types of DocumentOperations.bulkIndex methods | === Return types of DocumentOperations.bulkIndex methods | ||||||
| 
 | 
 | ||||||
| These methods were returing a `List<String>` containing the ids of the new indexed records. | These methods were returning a `List<String>` containing the ids of the new indexed records. | ||||||
| Now they return a `List<IndexedObjectInformation>`; these objects contain the id and information about optimistic locking (seq_no and primary_term) | Now they return a `List<IndexedObjectInformation>`; these objects contain the id and information about optimistic locking (seq_no and primary_term) | ||||||
|  | |||||||
| @ -251,7 +251,7 @@ In this case, writing the type hint will produce an error, as the field cannot b | |||||||
| 
 | 
 | ||||||
| Type hints can be disabled for the whole application by overriding the method `writeTypeHints()` in a configuration class derived from `AbstractElasticsearchConfiguration` (see <<elasticsearch.clients>>). | Type hints can be disabled for the whole application by overriding the method `writeTypeHints()` in a configuration class derived from `AbstractElasticsearchConfiguration` (see <<elasticsearch.clients>>). | ||||||
| 
 | 
 | ||||||
| As an alternativ they can be disabled for a single index with the `@Document` annotation: | As an alternative they can be disabled for a single index with the `@Document` annotation: | ||||||
| 
 | 
 | ||||||
| ==== | ==== | ||||||
| [source,java] | [source,java] | ||||||
|  | |||||||
| @ -79,7 +79,7 @@ interface ReactivePersonRepository extends ReactiveSortingRepository<Person, Str | |||||||
| parameters. | parameters. | ||||||
| <9> Count all entities with matching `firstname`. | <9> Count all entities with matching `firstname`. | ||||||
| <10> Check if at least one entity with matching `firstname` exists. | <10> Check if at least one entity with matching `firstname` exists. | ||||||
| <11> Delete all entites with matching `firstname`. | <11> Delete all entities with matching `firstname`. | ||||||
| ==== | ==== | ||||||
| 
 | 
 | ||||||
| [[elasticsearch.reactive.repositories.configuration]] | [[elasticsearch.reactive.repositories.configuration]] | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user