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(a)hibernate.org&gt; > 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

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(a)hibernate.org&gt; > > > 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(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > >

On 13 Jan 2013, at 8:47 AM, Gunnar Morling <gunnar(a)hibernate.org&gt; wrote: > Would creating a "real" query language instead of a serialized object > representation make sense then? You mean the Lucene query language - http://lucene.apache.org/core/old_versioned_docs/versions/3_4_0/querypars...) In the end it comes down to that.

What would the purpose of a new query language be? I guess it would be more object centric, but is this relevant for a user?

> 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. I just don't see users of a finished app being exposed to such query functionality. I see the JSON representation just as a way to serialise the query. To which means I am not sure at the moment.

--Hardy