[mapping] "short name" too strict in 2.0 compared to the 1.7 version


(Camilo Sierra) #1

Ok i undestand that in your *example title is ambiguous, and in this case it'is important the full path !
*ES example :
https://www.elastic.co/guide/en/elasticsearch/reference/2.1/breaking_20_mapping_changes.html#_fields_cannot_be_referenced_by_short_name .

but i have "vdu" a simple object with two attributes, in this case if i use "vdu" there is no ambiguity!

Mapping :

"vdu": {
	"type": "object",
	"properties": {
		"vdu": {
			"type": "integer"
		},
		"vid": {
			"type": "integer"
		}
	}
}

in 1.7 version i use only "vdu", this allow me to request two different index at the same time. One aggregated (using type object) and current month index (not aggregated) where vdu is an integer.

ok now in 2.0 i will split the request, in two request one case using vdu.vdu and the other one vdu, :frowning:

it was a cool feature..


(system) #2