Re: LTR - OriginalScore query issue

2018-03-19 Thread Alessandro Benedetti
>From Apache Solr tests : loadFeature( "SomeEdisMax", SolrFeature.class.getCanonicalName(), "{\"q\":\"{!edismax qf='title description' pf='description' mm=100% boost='pow(popularity, 0.1)' v='w1' tie=0.1}\"}"); *qf='title description'* Can you try again using the proper

Re: LTR - OriginalScore query issue

2018-03-16 Thread ilayaraja
Yes, I have tried that too: But it was throwing error while feature extraction: "Exception from createWeight for SolrFeature [name=originalLuceneScore, params={q={!dismax qf=tem_type_all^30.0 ..}${user_query}}] Failed to parse feature query. at org.apache.solr.ltr.LTRScoringQuery.crea

Re: LTR - OriginalScore query issue

2018-03-16 Thread Alessandro Benedetti
I understood your requirement, the SolrFeature feature type should be quite flexible, have you tried : { name: "overallEdismaxScore", class: "org.apache.solr.ltr.feature.SolrFeature", params: { q: "{!dismax qf=item_typel^3.0 brand^2.0 title^5.0}${user_query}" }, store: "myFeatureStoreDemo",

Re: LTR - OriginalScore query issue

2018-03-15 Thread ilayaraja
I do have the features defined as below for field specific (title..) matching etc: features: [ { name: "productNewness", class: "org.apache.solr.ltr.feature.SolrFeature", params: { q: "{!func}recip( ms(NOW,launchdate_pl), 3.16e-11, 1, 1)" }, store: "myFeatureStoreDemo", }, { name: "originalScore",

Re: LTR - OriginalScore query issue

2018-03-15 Thread Alessandro Benedetti
>From the snippet you posted this is the query you run : q=id:"13245336" So the original score ( for each document in the result set) can only be the score associated to that query. You then pass an EFI with a different text. You can now use that information to calculate another feature if you wa

LTR - OriginalScore query issue

2018-03-15 Thread ilayaraja
solr/collection/select?fl=id,score,[features+store=myFeatureStore+efi.user_query='black shoes']&wt=json&q=id:"13245336"&debugQuery=on When we fire this query during feature extraction, the originalScore feature gets the score of the "id" match but not the actual user query which is in this case 'b