ChunkInfo start time may be too early

[gjacoby126]

In ChunkInfo for a ReadWriteChunk, we initialize dataEndTimeEpochMs to a high sentinel value so that the first message's end time will always become the first end time, and then it can expand upward from there if any messages come in later with later timestamps.

However, we initialize dataStartTimeEpochMs to the chunk creation time, and it can then shrink earlier if any messages with earlier timestamps come in. This will lead to incorrect values if no message comes in with a timestamp earlier than or equal to the chunk creation time.

This doesn't seem to affect correctness, but it means that we may examine a chunk unnecessarily during search. Instead, the start time should be initialized to a low sentinel value so that the start time of the first message is always used.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[bryanlb]

@allcontributors please add @gjacoby126 for bug

[allcontributors]

@bryanlb

I've put up a pull request to add @gjacoby126! 🎉