prometheus/CHANGELOG.md

## master / unreleased

 - `LastCheckpoint` used to return just the segment name and now it returns the full relative path.
 - `NewSegmentsRangeReader` can now read over miltiple wal ranges by using the new `SegmentRange` struct.
 - `CorruptionErr` now also exposes the Segment `Dir` which is added when displaying any errors.
 - `Head.Init()` is changed to `Head.Init(minValidTime int64)` where `minValidTime` is taken from the maxt of the last persisted block and any samples below `minValidTime` will not be loaded from the wal in the head. The same value is used when using the `Heah.Appender()` to disallow adding samples below the `minValidTime` timestamp. This change was nececary to fix a bug where a `Snapshot()` with the head included would create a block with custom time range(not bound to the default time ranges) and the next block population from the head would create an overlapping block.  
    - https://github.com/prometheus/tsdb/issues/446
refactor NewSegmentsRangeReader to take multi WAL ranges (#449) * refactor NewSegmentsRangeReader to take multi WAL ranges In case of an error when checkpointing the WAL the error doesn't show the exact WAL index that is corrupter. this is because it uses MultiReader to read multiply WAL files. This refactoring allows the NewSegmentsRangeReader to take more than a single WAL range and it reads all of the ranges by iterating each one. this changes the logs from create checkpoint: read segments: corruption after 4841144384 bytes:... to create checkpoint: read segments: corruption in segment data/wal/00017351 at 123142208: ... Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com> 6 years ago			`## master / unreleased`

			- `LastCheckpoint` used to return just the segment name and now it returns the full relative path.
			- `NewSegmentsRangeReader` can now read over miltiple wal ranges by using the new `SegmentRange` struct.
			- `CorruptionErr` now also exposes the Segment `Dir` which is added when displaying any errors.
no overlapping on compaction when an existing block is not within default boundaries. (#461) closes https://github.com/prometheus/prometheus/issues/4643 Signed-off-by: Krasi Georgiev <kgeorgie@redhat.com> 6 years ago			- `Head.Init()` is changed to `Head.Init(minValidTime int64)` where `minValidTime` is taken from the maxt of the last persisted block and any samples below `minValidTime` will not be loaded from the wal in the head. The same value is used when using the `Heah.Appender()` to disallow adding samples below the `minValidTime` timestamp. This change was nececary to fix a bug where a `Snapshot()` with the head included would create a block with custom time range(not bound to the default time ranges) and the next block population from the head would create an overlapping block.
			`- https://github.com/prometheus/tsdb/issues/446`