jadami10 opened a new pull request, #14612:
URL: https://github.com/apache/pinot/pull/14612
This is an API enhancement so servers give a reason for why time boundary
advance failing. We've found with tables wtih 10k+ segments, this API will
repeatedly fail, but there's no way to debug what segment failed or why.
I added a unit test to ensure parsing still works without "invalidReason".
I also tested this on a cluster by manually changing the segment CRC in the
zk metadata.
Calling the API when the controller was upgraded but the server wasn't gave
back "null" as the error.
```
{
"code": 412,
"error": "Table segment validation failed. error=null"
}
```
Calling the API with bot components upgraded gave back the actual error.
```
{
"code": 412,
"error": "Table segment validation failed. error=Segment
<table_name>_1732579200000_1733356800000_1733450209949 is in ONLINE state, but
has CRC mismatch. zk_metadata_crc=1408182336,
segment_data_manager_crc=1408182337"
}
```
--
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]
