Hi Marcus
> thank you for your reply.
> here's my gist
https://gist.github.com/mintbass/5044004 for sample
> mapping and sample data.
Just as a side note, you are specifying that the _id should be extracted
from the field _uid in your documents, but you're not passing a _uid.
Also, in general, don't use field names beginning with an underscore, as
these are reserved for internal Elasticsearch field names, and you may
end up with a conflict.
> the _fields is dynamically changed by data types so i need the
> multi_field mapping and i want _value field not to be analyzed.
Then, you have completely misunderstood how multi-fields work. And you
can't have dynamic field names represented by "$name" - it just won't
work.
A multi-field expects to receive a single key/value pair, eg
{"my_field": "my value"}
and then it will index "myvalue" in one or more ways. For instance:
{ my_field: {
type: "multi_field",
fields: {
my_field: { type: "string" },
raw: { type: "string", index: "not_analyzed" }
}
}
If you index a document like { "my_field": "my value" } then you will
have two searchable fields:
- "my_field.my_field" (also accessible as "my_field")
containing terms ["my","value"]
- "my_field.raw"
containing the term ["my value"]
You can use "dynamic templates"
http://www.elasticsearch.org/guide/reference/mapping/root-object-type.html to auto-map new fields, but it would be much simpler to just define the field types ahead of time.
clint
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/groups/opt_out.
Locked
