Hi Yonik,
thank you for your quick reply.
(((I just send my original e-mail a second time (I did not confirm the
subscription so I thought it might not have been send the first time, I’m
sorry.
We are using SOLR 6.1.0. Sorry, I should have mentioned.
The low number is because of the test
Hi all,
this is about using a function in nested facets, specifically the „sum()“
function inside a „terms“ facet using the json.facet api.
My json.facet parameter looks like this:
json.facet={shop_cat: {type:terms, field:shop_cat, facet:
{cat_pop:"sum(popularity)"}}}
A snippet of the resu
Hi all,
this is about using a function in nested facets, specifically the „sum()“
function inside a „terms“ facet using the json.facet api.
My json.facet parameter looks like this:
json.facet={shop_cat: {type:terms, field:shop_cat, facet:
{cat_pop:"sum(popularity)"}}}
A snippet of the res
Hi Ahmet!
Thank you for that information. I was wondering whether dismax is kind of
„deprecated“ or - if not - when would I use dismax in preference to edismax.
The documentation sounds to me like „edismax is dismax+ : is does everything
dismax does, and more“.
Chantal
Am 21.07.2016 um 14:43 s
Just for the records:
After realizing that with „defType=dismax“ I really do get the expected output
I’ve found out what I need to change in my edismax configuration:
false
Then this will work:
> q=Braun Series 9 9095CC Men's Electric Shaver Wet/Dry with Clean and Renew
> Charger
> // edismax
Hi Ahmet,
thank you for the link. It helped me to find more resources.
What I still don’t understand, though, is why the edismax returns one of the
documents with a partial hit and not the other:
q=Braun Series 9 9095CC Men's Electric Shaver Wet/Dry with Clean and Renew
Charger
// edismax wi
Hello all,
our index contains product offers from online shops. The fields we are indexing
have all rather short values: the name of the product, the brand, the price,
category and some fields containing identifiers like ASIN, GTIN etc. if
available. We do not index the description texts.
The
