I wonder why you are asking for this feature? If its because Java broke backward comp. on serialization of InetAddress that we use in our exceptions, then its a bug in Java serialization, hard for us to do something about it.
You will loose a lot by trying to serialize exceptions using JSON, and we prefer not to introduce dependency on ObjectMapper in Jackson, or try and serialize exceptions using Jackson. I would be very careful in introducing this just because of a (one time bug) in Java. On Friday, March 21, 2014 5:18:38 PM UTC+1, Chris Berry 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6ae5f173-a2b4-435c-8e5d-a43d377e2fb0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
