My idea is to use 3rd party scoring service (REST), and currently I'd like
to use native scripts and play with NativeScriptFactory.
The approach has many drawbacks.
Here is my problem - assume we have two entities - products and product
prices. I should filter by price.
Price is a complex thing, because it depends on many factors, like request
date, remote user information, custom provided parameters. In case of
regular parent - child relation and has_child query it's too complex and
too slow to implement it using scripting (currently mvel).
Also one more condition - i have not many products - around 25K, and around
25M different base price items (which are basic for future price
There are next ideas:
- Have a service, which returns exact price for all product by custom
parameters like. The drawback is - there should be 5 same calls from each
shard (if 5 by default). In this case it doesn't matter, where base prices
are stored - in elasticsearch index, in database or in in-memory storage.
- Write a code, which operates over child price documents on concrete
shard. In this case it will generate prices only for all properties from
particular shard. But I don't know, if I can access shard index or make
calls to the index from concrete shard in NativeScriptFactory class.
Could you point me the right way?
P.S. Initially I was interested in Redis-Elasticsearch
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/893b22dc-1415-475b-8675-596119f4f1f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.