To add to what Binh said, you really shouldn't add field names like this:
On 14 March 2014 21:20, Pablo Musa <pablitom...@gmail.com> wrote:
> {
> "title":"The greatest band ever - Urban Legion",
> "greatest_x" : 1,
> "band_x" : 1,
> "ever_x" : 1,
> "Urban_x": 1,
> "Legion_x" : 1,
> "greatest_y" : [],
> "band_y" : [],
> "ever_y" : [],
> "Urban_y": [],
> "Legion_y" : []
> }
>
You end up with an explosion of fields, and each field has an inverted
index associated with it. Your cluster state will eventually become
enormous. Any change to the cluster state (eg adding a field, changing an
index, changes to nodes etc) results in the cluster state being copied to
every node in the cluster. If the state is very large you will experience a
significant slow down.
Instead of:
[{ custom_foo: xxx }, { custom_bar: yyy }]
Use nested fields with eg
[
{ type: "custom_foo", value: "xxx" },
{ type: "custom_bar", value: "yyy" }
]
That way you have only two fields.
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAPt3XKSwR4p4pi_z9cbS%3DLXcn-%3Dd_OnzKzJM9P8MiXK_4xpumg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
