Implement approximate time to latest in Kinesis Indexing Service

[jsun98]

Kinesis Indexing Service (#6431)

Kinesis records have a ApproximateArrivalTimestamp as a server side timestamp, which can be used to approximate the time from the latest record in the Kinesis stream. This is similar to Kafka's offset lag. This should be implemented in the protected void scheduleReporting(ScheduledExecutorService reportingExec) method of KinesisSupervisor

Each Amazon Kinesis record includes a value, ApproximateArrivalTimestamp, that is set when a stream successfully receives and stores a record. This is commonly referred to as a server-side time stamp, whereas a client-side time stamp is set when a data producer creates or sends the record to a stream (a data producer is any data source putting data records into a stream, for example with PutRecords). The time stamp has millisecond precision. There are no guarantees about the time stamp accuracy, or that the time stamp is always increasing. For example, records in a shard or across a stream might have time stamps that are out of order.

see also
https://aws.amazon.com/about-aws/whats-new/2015/09/amazon-kinesis-server-side-timestamp/
https://docs.aws.amazon.com/kinesis/latest/APIReference/API_GetRecords.html

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

[stale]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.