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
I have a similar question. I performing my feature extraction with the
following:
fl= [features+efi.query=bakeware 3-piece set]
I'm pretty sure the dash is causing my query to error. But I'm also not sure
how the spaces impacts the efi param. I tried putting the term in quotes, but
that does n
