This is a bit of an odd one, although not really for those of us who work
in the eCommerce world I suppose.
I work for one of the largest children's retailers in the UK. We're
currently knocking together a demonstration of our eCommerce platform with
everything running off Elasticsearch rather than the 3rd party solution we
currently use for our search. The 3rd party solution costs us thousands of
£ every month, where as the architecture needed to run our entire site
(search, range pages and product details pages) off ES actually costs a
fraction of that.
I currently have most of the functionality working via ES just fine.
However, our content co-ordinators really require the ability (via a CMS of
our design) to boost certain VIP products, but based on the query provided.
They know the document ID, and they know the query string they want to
boost products for. I can write the CMS with a connector to get this
information into ES but I'm unsure of what to do next.
Two options I have considered are as follows:
- A separate ES index containing containing the document id (this is
the product id), the query string to boost for and then the boost factor.
- A property on the document itself that contains the query string to
boost for and the boost factor.
These boost factors would then be applied using the function_score
mechanism. Which one would you choose? Why? Is there an option I'm missing?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a3b951a6-5d90-45b0-8223-494032d830d9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.