Skip to content

feat(compactor): allow overriding header timestamp#75

Closed
corylanou wants to merge 1 commit into
mainfrom
codex/issue-74-compactor-timestamp
Closed

feat(compactor): allow overriding header timestamp#75
corylanou wants to merge 1 commit into
mainfrom
codex/issue-74-compactor-timestamp

Conversation

@corylanou
Copy link
Copy Markdown
Collaborator

@corylanou corylanou commented Feb 3, 2026

Summary

  • add optional Compactor.HeaderTimestamp override for the output header timestamp
  • keep default behavior when the override is unset
  • add test coverage for the timestamp override

Why

Compacted L1+ files currently inherit the latest input timestamp. For PITR, downstream tools need the earliest timestamp preserved after L0 retention.

Testing

  • go test ./...

Links

@corylanou corylanou changed the title feat(compactor): allow header timestamp override feat(compactor): allow overriding header timestamp Feb 3, 2026
@corylanou
Copy link
Copy Markdown
Collaborator Author

Closing based on Ben’s guidance: compacted LTX files represent the latest state only, so their header timestamp should remain the last input timestamp. Earliest timestamps aren’t valid PITR targets once L0 files are compacted, so this change would be misleading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compactor: allow preserving earliest input timestamp for PITR

1 participant