Hui Wang 664f337c70 stream aggregation: fix possible duplicated aggregation results (#7118) ... When ingesting samples with the same labels(duplicated samples or samples with the same labels after `by` or `without` options). They could register different entries for the same labelset in LabelsCompressor. For example, both index 99 and 100 can be assigned to label `foo=1` in two concurrent pushes. Then due to differing label indexes in encoded keys, the samples will appear as distinct in aggrState, resulting in duplicated results after decompressing the label indexes. fbde238cdc/lib/streamaggr/streamaggr.go (L933) In this pull request, since we need to store `idxToLabel` first to ensure the idx can be searched after `lc.labelToIdxStore`, the `lc.idxToLabel` still could contain a duplicated entries [100]="foo=1". But given the low likelihood of this issue and the size of idxToLabel, it should be fine.		2024-09-30 14:24:59 +02:00
..
_index.md	docs: move changelog to dir (#6853)	2024-08-21 17:26:54 +02:00
CHANGELOG_2020.md	docs: fix broken links to prev changelogs	2024-08-31 16:34:21 +02:00
CHANGELOG_2021.md	docs: fix broken links to prev changelogs	2024-08-31 16:34:21 +02:00
CHANGELOG_2022.md	docs: fixes misspelled typos	2024-09-13 12:14:24 +02:00
CHANGELOG_2023.md	docs: fixes misspelled typos	2024-09-13 12:14:24 +02:00
CHANGELOG.md	stream aggregation: fix possible duplicated aggregation results (#7118)	2024-09-30 14:24:59 +02:00