[infinispan-dev] [hibernate-dev] JSON version of Hibernate Search query

[Gunnar Morling]

Would creating a "real" query language instead of a serialized object
representation make sense then?

This would allow for a conciser syntax, making it easier to write (that's
why I asked who would be writing such queries), but probably it'd be more
work to create such a language. I guess a sub-set of JPQL would work for
some parts, but additional elements would be needed for facets etc.

For other applications (at least Java ones) which are creating queries
programmatically it could also be an option to extend the DSL to allow for
specifying the output format:

    String query = buildQueryBuilder()
        .forEntity( Hypothesis.class )
        .get()
        .all()
        .createQuery( Format.JSON );

    //submit query...

The DSL implementation would create an actual Lucene query, a JSON string
etc., depending on the given format.

Not sure what makes sense, just throwing out some ideas.

--Gunnar




2013/6/12 Emmanuel Bernard <emmanuel at hibernate.org>

> In the end there is always a human (so far) but think of it as used in
> the same way SQL is. SQL is sued by both humans and programs (ORMs).
>
> Emmanuel
>
> On Wed 2013-06-12 15:03, Gunnar Morling wrote:
> > Hi,
> >
> > Just out of interest, what are the use cases for such a serialized form?
> Is
> > this intended to be written by humans or other applications?
> >
> > --Gunnar
> >
> >
> >
> >
> > 2013/6/11 Emmanuel Bernard <emmanuel at hibernate.org>
> >
> > > Hey everyone,
> > >
> > > Sanne and I discussed Hibernate Search queries and serialization in
> > > general. I did play around that to represent Hibernate Search DSL
> > > queries into JSON.
> > >
> > > https://gist.github.com/emmanuelbernard/5760676
> > >
> > > It is a very first draft (not reviewed). What is really nice is that I
> did
> > > not have to
> > > do much adaptation, the Query DSL is expressive enough to have a one to
> > > one port thanks to its context nature.
> > >
> > > I did not work on some of the quirk cases nor tried to optimize the
> > > "80%" use case.
> > >
> > > A nice effect is that I manage to unify the FullTextQuery (including
> the
> > > types filtering), the lucene query part, the faceting definitions and
> > > the faceting selection.
> > >
> > > Let me know what you think.
> > > _______________________________________________
> > > hibernate-dev mailing list
> > > hibernate-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20130613/f3ff8e33/attachment-0001.html