I would be very interested in that pull request, too. Changing every exception transport to a textual JSON error seems a proper alternative. I haven't tried Jackson ObjectMapper on the exception classes that are present in ES but it should be possible.
Jörg On Fri, Mar 21, 2014 at 5:18 PM, Chris Berry <chriswbe...@gmail.com> wrote: > Greetings, > > Let me say up-front, I am a huge fan and proponent of Elasticsearch. It is > a beautiful tool. > > So, that said, it surprises me that Elasticsearch has such a pedestrian > flaw, and serializes it's Exceptions using Java Serialization. > In a big shop it is quite difficult (i.e. next to impossible) to keep all > the ES Clients on the same exact JVM as Elasticsearch, and thus, it is not > uncommon to get TransportSerializationExceptions instead of the actual > underlying problem. > I was really hoping this would be corrected in ES 1.0.X, but no such luck. > (As far as I can tell...) > > It seems that this is pretty easily fixed? > Just switch to a JSON representation of the basic Exception and gracefully > (forwards-compatibly) attempt to re-hydrate the actual Exception class. > You'd just have to drop an additional "header" in the stream that tells > the code it is a JSON response and route to the right Handler it > accordingly. If the header is missing, then do things the old way with Java > Serialization?? > > Are there any plans to fix this? Or perhaps to entertain a Pull Request? > It may seem just an annoyance, but it is actually pretty bad, in that it > keeps Clients from seeing their real issues. Especially in shops where it > is difficult to see the Production logs of Elasticsearch itself. > > Thanks much, > -- Chris > > > -- > 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/1e02778a-a1d0-44b5-8b1f-e8de7de33668%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/1e02778a-a1d0-44b5-8b1f-e8de7de33668%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAKdsXoFxv%3D%3DNFxXkLaT7%2BKcuBApO0NZfwN77mi_BS_BhNeG0tA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
