somandal commented on PR #15368:
URL: https://github.com/apache/pinot/pull/15368#issuecomment-2754812352
> ## Known problems
> So far the API `GET /tables/{tableName}/consumingSegmentsInfo` seems to
fail when the stream type is Kinesis. It might be due to the mis-alignment of
pinot partition ID and Kinesis's shard ID. Therefore
`maxBytesConsumingSegmentsToCatchUp` and
`bytesConsumingSegmentsToCatchUpPerServer` are not available for realtime table
with Kinesis stream.
Can you provide more details on how you tested this so far? And provide some
information on the error logs, exceptions, or the result returned by the above
API for Kinesis streams? What does your set up look like? I can try to look
into this today as well
--
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: commits-unsubscr...@pinot.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
