If you wanted to adhere the http spec, the best you really have is 200 with
details in the response about it being incomplete. If the user put in limits
and you return partial results due to those limits, it’s a successful
request/response. 206 is specifically for a request with range headers.
timeAllowed typically returns partial results. The feature I'm working on
is allowing it to short circuit when the user knows that partial results
are not useful.
On Sun, Mar 31, 2024 at 11:21 PM David Smiley wrote:
> It was an 8x but it's more hypothetical if /update were to support
> this. It
It was an 8x but it's more hypothetical if /update were to support
this. It does where I work :-)
Weird that you got status=0 and fewer results without specifying
shards.tolerant=true
On Sun, Mar 31, 2024 at 4:41 PM Gus Heck wrote:
>
> Hmm, I took the initial statement about returning 500 at fa
Hmm, I took the initial statement about returning 500 at face value when I
wrote my response above, but with actual testing I'm not seeing that
behavior in any recent version... (tested 9.1, 9.4, 9.5, main) this cause a
some confusion since I am working in that code right now and having read
this I
