[Ryan McKinley] For starters, the order of multi-valued fields should
be maintained, so if you have:
Wait! I thougt documents and fields are sets in the Lucene index -
order is not preserved.
On Thu, Dec 31, 2009 at 7:47 PM, Chris Hostetter
wrote:
>
> : You could easily write your own query pars
: You could easily write your own query parser (QParserPlugin, in Solr's
: terminology) that internally translates queries like
:
:q = res_url:url AND res_rank:rank
:
: into
: q = res_ranked_url:"rank url"
:
: thus hiding the res_ranked_url field from the user/client.
:
: I'm not
Hi,
Thanks Sascha for your post, but i find it interresting, but in my case i
don't want to use an additionnal field, i want to be able with the same
schema to do a simple query like : "q=res_url:some url", and a query like
the other one;
You could easily write your own query parser (QParserPlug
Ya, structured data gets a little funny.
For starters, the order of multi-valued fields should be maintained,
so if you have:
http://aaa
5
http://bbb
4
the response will return result in order, so you can map them with
array indicies.
I have played some tricks with a JSON field ana
Thanks Sascha for your post, but i find it interresting, but in my case i
don't want to use an additionnal field, i want to be able with the same
schema to do a simple query like : "q=res_url:some url", and a query like
the other one;
in other word; is there any solution to make two or more multiv
Hi,
you could create an additional index field res_ranked_url that contains
the concatenated value of an url and its corresponding rank, e.g.,
res_rank + " " + res_url
Then, q=res_ranked_url:"1 url1" retrieves all documents with url1 as the
first url.
A drawback of this wor
