[
https://issues.apache.org/jira/browse/SOLR-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133049#comment-16133049
]
Yonik Seeley commented on SOLR-11244:
-------------------------------------
Great someone is tackling this! I had started a while ago with SOLR-4351
I think the approach I was taking was to combine JSON and local-params/qparser
at the Object level (i.e. the parsers end up operating more on Object graphs
that were produced from JSON or local params). Whenever one encounters a raw
String where a query is expected, then it can be parsed using the default
qparser. Allowing one back to "lucene syntax" at any point in a query tree
leads to more concise representations. From your description, it looks like you
have exactly that capability.
One reason I was thinking of changing QParsers to act on Object graphs instead
of Strings is because local params can't represent everything that JSON can,
and we want future QParsers (or existing qparsers) to be able to take JSON as
parameters as well as strings. I haven't looked at your patch yet, so I don't
know how this interface between strings and objects is implemented beyond your
note of "Basically, the json query object is converted into a local parameter
string."
> Query DSL for Solr
> ------------------
>
> Key: SOLR-11244
> URL: https://issues.apache.org/jira/browse/SOLR-11244
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Attachments: SOLR-11244.patch, Solr Query DSL - examples.html
>
>
> It will be great if Solr has a powerful query DSL. This ticket is an
> extension of [http://yonik.com/solr-json-request-api/].
> Here are several examples of Query DSL
> {code}
> curl -XGET http://localhost:8983/solr/query -d '
> {
> "query" : {
> "lucene" : {
> "df" : "content",
> "query" : "solr lucene"
> }
> }
> }
> {code}
> the above example can be rewritten as (because lucene is the default qparser)
> {code}
> curl -XGET http://localhost:8983/solr/query -d '
> {
> "query" : "content:(solr lucene)"
> }
> {code}
> more complex example:
> {code}
> curl -XGET http://localhost:8983/solr/query -d '
> {
> "query" : {
> "boost" : {
> "query" : {
> "lucene" : {
> "q.op" : "AND",
> "df" : "cat_s",
> "query" : "A"
> }
> }
> "b" : "log(popularity)"
> }
> }
> }
> {code}
> I call it Json Query Object (JQO) and It defined as :
> - It can be a valid query string for Lucene query parser, for example :
> "title:solr"
> - It can be a valid local parameters string, for example : "{!dismax
> qf=myfield}solr rocks"
> - It can be a json object with structure like this
> {code}
> {
> "query-parser-name" : {
> "param1" : "value1",
> "param2" : "value2",
> "query" : <JQO>,
> "another-param" : <JQO>
> }
> }
> {code}
> Therefore the above dismax query can be rewritten as ( be noticed that the
> query argument in local parameters, is put as value of {{query}} field )
> {code}
> {
> "dismax" : {
> "qf" : "myfield"
> "query" : "solr rocks"
> }
> }
> {code}
> I will attach an HTML, contain more examples of Query DSL.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
