Jackie-Jiang commented on issue #7264:
URL: https://github.com/apache/pinot/issues/7264#issuecomment-903033843
@yupeng9 Current pinot behavior will always return the available results,
and set exceptions for unexpected scenarios such as unable to reach to a
server. For now I would suggest
Jackie-Jiang commented on issue #7264:
URL: https://github.com/apache/pinot/issues/7264#issuecomment-903026216
We need to think about how to set this `partialResponse` flag. What
scenarios should be count as partial
--
This is an automated message from the Apache Git Service.
To respond
Jackie-Jiang commented on issue #7264:
URL: https://github.com/apache/pinot/issues/7264#issuecomment-902318772
I'd suggest adding different errors for each scenario described above to the
`QueryException`, and users can decide on how to proceed based on the error
type (error code). We
Jackie-Jiang commented on issue #7264:
URL: https://github.com/apache/pinot/issues/7264#issuecomment-98623
@amrishlal Partial and approximation are different, where approximation
usually gives bounded error rate. The cases we want to notify the user here is
when some segments are not
Jackie-Jiang commented on issue #7264:
URL: https://github.com/apache/pinot/issues/7264#issuecomment-895539754
We don't have that flag in OSS. IIRC the logic for that flag is check if
`numServersQueried` matches `numServersResponded` and whether there are
exceptions.
We don't model
Jackie-Jiang commented on issue #7264:
URL: https://github.com/apache/pinot/issues/7264#issuecomment-895487473
We don't really have that for case 1 and 2. For case 3, we should not expect
normal users to check `numServersQueried` and `numServersResponded` and compare
them to tell whether
