Skip to content
This repository was archived by the owner on Aug 23, 2023. It is now read-only.

handle duplicate datapoints in a consistent manner#1276

Closed
Dieterbe wants to merge 1 commit intomasterfrom
fix_1201
Closed

handle duplicate datapoints in a consistent manner#1276
Dieterbe wants to merge 1 commit intomasterfrom
fix_1201

Conversation

@Dieterbe
Copy link
Copy Markdown
Contributor

@Dieterbe Dieterbe commented Apr 10, 2019

this is awoods' work

fixes #1201

Without the reorder_buffer, MT only persists the first value received for each timestamp. With the re-order buffer we should do the same.

fixes #1201

Without the reorder_buffer, MT only persists the first value received for each timestamp. With the re-order buffer we should do the same.
@Dieterbe
Copy link
Copy Markdown
Contributor Author

my feedback on this is in #1201

@Dieterbe
Copy link
Copy Markdown
Contributor Author

this needs a bit of tweaking as discussed in #1201 (comment)

@fkaleo
Copy link
Copy Markdown
Contributor

fkaleo commented Apr 17, 2019

Deprecated by #1288

@Dieterbe Dieterbe closed this Apr 18, 2019
@Dieterbe Dieterbe deleted the fix_1201 branch April 18, 2019 12:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

duplicate datapoints are handled differently depending on whether re-orderBuffer is used

3 participants