goutamadwant commented on issue #18866: URL: https://github.com/apache/pinot/issues/18866#issuecomment-5199881276
Hi @Jackie-Jiang, I’d like to work on this. I reproduced the current timeout behavior in QueryRoutingTest on current master. though one design detail I’d like to confirm first: the request ID is currently available only after the DataTable is successfully deserialized, while a server channel can have multiple in-flight requests. For a malformed response, the broker therefore cannot reliably identify the individual query. Would you prefer closing the channel and marking all affected in-flight responses from that server as failed on a per-server basis, preserving partial results from healthy servers, or introducing a compatibility-safe way to carry the request ID outside the serialized DataTable? Once confirmed, I can add the focused regression coverage and distinct deserialization error handling. Let me know thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
