[hibernate-dev] [Search] Elasticsearch - Translating exceptions?

[Emmanuel Bernard]

I mentioned 6 because I'm not even sure this mapping brings a lot of
value, so it could be tagged to the release "duke nukem forever" if you
see what I mean, unless we get concrete user feedback.

On Mon 2016-02-29 18:33, Sanne Grinovero wrote:
> I'd agree it's a non essential nice-to-have, but I'd not want to push
> things for 6.x if they can be done before that (6.x is large enough).
> 
> You can mark such issues for 5.7 - a version which we might do or
> maybe skip - and then we can decide if we want to implement it before
> 6.x depending on if we (you?) find a clean solution for it.
> 
> On 29 February 2016 at 16:55, Emmanuel Bernard <emmanuel at hibernate.org> wrote:
> > Yes that's a pretty significant body of work that I would move as an
> > idea for 6.x along the API cleaning.
> >
> > On Mon 2016-02-29 16:08, Guillaume Smet wrote:
> >> Hi,
> >>
> >> I have a question regarding the Elasticsearch backend: should we try to
> >> translate the Elasticsearch exceptions to Hibernate Search exceptions (the
> >> ones from the loggers) when possible?
> >>
> >> Good examples of it are in
> >> SpatialIndexingTest#testNonGeoDistanceSortOnNonSpatialField and
> >> #testNonGeoDistanceSortOnMissingField.
> >>
> >> I think it might make sense for these particular examples but I wonder if
> >> it won't be a maintenance burden in the long term.
> >>
> >> Thoughts?
> >>
> >> --
> >> Guillaume
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev