I believe I've discovered a workaround. If you use:
{
"store": "redhat_efi_feature_store",
"name": "case_description_issue_tfidf",
"class": "org.apache.solr.ltr.feature.SolrFeature",
"params": {
"q":"{!dismax qf=text_tfidf}${text}"
}
}
i
It turns out my last comment on that Jira was mistaken. Multi-term EFI
arguments still exhibit unexpected behavior. Binoy is trying to help me
figure out what the issue is. I plan on updating the Jira once we've
figured out the problem.
On Thu, Oct 12, 2017 at 3:41 AM, alessandro.benedetti
wrote:
I don't think this is actually that much related to LTR Solr Feature.
In the Solr feature I see you specify a query with a specific query parser
(field).
Unless there is a bug in the SolrFeature for LTR, I expect the query parser
you defined to be used[1].
This means :
"rawquerystring":"{!field f
that does not work.
--Brian
-Original Message-
From: Binoy Dalal [mailto:binoydala...@gmail.com]
Sent: Wednesday, October 11, 2017 10:51 AM
To: SOLR users group
Subject: Parsing of rq queries in LTR
Hi,
For an LTR query, is there any way of checking how the `rq` is being parsed? or
sp
Hi,
For an LTR query, is there any way of checking how the `rq` is being
parsed? or specifically how the `efi` queries are treated?
For e.g. let's say my `rq` looks like this:
"rq":"{!ltr model=my_efi_model efi.text=my car}"
And my corresponding feature is:
SolrFeature [name=my_efi, params={q={!f
