This is a bug in Lingo3G. It will only manifest itself if you have
single tokens ("words") that exceed over 30k in UTF8... So in reality
it shouldn't be the case unless you're trying to cluster languages
without whitespace delimiters (and with incorrect language
preprocessing option for Lingo3G).
Could you provide a repeatable test case to my e-mail address if the
above is not the case? We will try to fix the bug in the next release
but I still think you should cluster on fields that don't contain such
awkward tokens.
Dawid
On Mon, Mar 3, 2014 at 1:22 PM, prashy <[email protected]> wrote:
> Ok Dawid, waiting for your reply...
>
>
>
> --
> View this message in context:
> http://elasticsearch-users.115913.n3.nabble.com/Error-ReduceSearchPhaseException-tp4050531p4050805.html
> Sent from the ElasticSearch Users mailing list archive at Nabble.com.
>
> --
> 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/1393849374162-4050805.post%40n3.nabble.com.
> For more options, visit https://groups.google.com/groups/opt_out.
--
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/CAM21Rt91S143TKxrfxbBiO1xMLjg6F9TcFJTq6KKLMv%2BaXEy8A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
