Add out-of-order data concept page#454
Merged
Merged
Conversation
New /docs/concepts/out-of-order-data/ page with per-ingestion-method behavior, engine mechanics, write amplification monitoring (per-table via tables() and cluster-wide via Prometheus), tuning, and common scenarios. Notes that write amplification also comes from incremental materialized view refreshes and UPDATE, not only out-of-order writes. Shrinks the OOO subsection in designated-timestamp.md and adds inbound links from partitions, write-ahead-log, capacity-planning, schema-design-essentials, ILP overview, CSV import, and time-series-optimizations. Adds a tip on the date-time functions page pointing at the dedicated timestamp() function page, and a sort-order warning to the SELECT subsection of that page.
|
🚀 Build success! Latest successful preview: https://preview-454--questdb-documentation.netlify.app/docs/ Commit SHA: 729cd39
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/docs/concepts/out-of-order-data/page consolidating what was previously scattered across designated-timestamp, partitions, capacity-planning, ILP overview, CSV import, WAL, and time-series-optimizations. Covers per-ingestion-method behavior, engine mechanics, write amplification (with the recently exposedtable_write_amp_*columns and a more honest framing of what "high" means, validated against Slack discussions with the engineering team), tuning, and common scenarios.timestamp()function page (which is otherwise hard to find), and the SELECT subsection of that page gets a warning about silent wrong results when data isn't sorted by the elected column. Also corrected an inline typo whereLATEST BYwas listed twice.