[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
hossman_luc...@fucit.org wrote:
: You could easily
: 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
position of key1 results
and i would like that solr consider this when executing queries.
Any helps please; and thanks for all :)
--
View this message in context:
http://old.nabble.com/how-to-do-a-Parent-Child-Mapping-using-entities-tp26956426p26965478.html
Sent from the Solr - User mailing
of key1 results
and i would like that solr consider this when executing queries.
Any helps please; and thanks for all :)
--
View this message in context:
http://old.nabble.com/how-to-do-a-Parent-Child-Mapping-using-entities-tp26956426p26965478.html
Sent from the Solr - User mailing list archive
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
and i would like that solr consider this when executing queries.
Any helps please; and thanks for all :)
--
View this message in context:
http://old.nabble.com/how-to-do-a-Parent-Child-Mapping-using-entities-tp26956426p26956426.html
Sent from the Solr - User mailing list archive at Nabble.com.
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