You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/08/25 23:45:40 UTC

[GitHub] [druid] jon-wei commented on pull request #10315: Handle internal kinesis sequence numbers when reporting lag

jon-wei commented on pull request #10315:
URL: https://github.com/apache/druid/pull/10315#issuecomment-680322907


   >  Do you know if this issue can be simulated in an integration test?
   
   I think the unit test is sufficient here, to replicate it completely you would need to wait for the Kinesis retention period for the shards to expire (a minimum of 24 hours), and a different approach with putting the expired offsets in metadata for simulation purposes I don't think adds much more testing value than just the unit test.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org