I see. Thanks.
I wasnt expecting to have to check for shard failures.
Would it make sense to have a config or request setting whereby any shard
failures are reported as exceptions (java api).
In the space where we have been using elastic, partial results are bad. We
would end up having to
If it fails on the primary shard, then a failure is returned. If it worked, and
a replica failed, then that replica is deemed a failed replica, and will get
allocated somewhere else in the cluster. Maybe an example of where a failure on
all shards would help here?
On Jun 18, 2014, at 11:45,
On Fri, Jun 20, 2014 at 7:08 AM, Shay Banon kim...@gmail.com wrote:
If it fails on the primary shard, then a failure is returned. If it
worked, and a replica failed, then that replica is deemed a failed replica,
and will get allocated somewhere else in the cluster. Maybe an example of
where a
Ahh, I see. If its related to searches, then yea, the search response includes
details about the total shards that the search was executed on, the successful
shards, and failed shards. They are important to check to understand if one
gets partial results.
In the REST API, if there is a total
Every man and his own business requirements and SLAs. Many scenarios I've
seen would consider two-thirds of shards responding as an OK scenario and
not even show a notice about results being partial. But of course it makes
sense to throw an exception if your business requires / expects that.
