Thank you very much for the hints ;) > If it matters, you can call the _analyze API to produce the tokens before you inject your fields.
Is there an URL there I can call? Or only using the internal API? > Your cluster state will eventually become enormous. Yes, I saw it coming but was postponing in dev phase. Thanks for the solution, it will help very much!! Thanks again guys! --Pablo On Saturday, March 15, 2014 8:59:09 AM UTC-3, Clinton Gormley wrote: > > To add to what Binh said, you really shouldn't add field names like this: > On 14 March 2014 21:20, Pablo Musa <[email protected] <javascript:>>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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a5e3f166-7c40-4bdf-b1cc-4854abdb4595%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
