ClickHouse / ClickHouse/dbt-clickhouse
Question: How optimal is snapshot for large tables?
- Dominant language
- Python
- Stars
- 362
- Forks
- 177
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 8
Description
I was thinking about using the snapshot function to manage slowly changing updates to 'large' tables. I was wondering if this is recommended, or if it is best suited for small tables? Do you have any idea of the kind of optimal table size is appropriate?
(Thanks for all the recent work on the plugin. Lots of great new features and fixes.)
Contributor guide
Research direction
The issue names snapshot usage for large tables but provides no files, tests, or entry points to inspect. Start by locating the snapshot implementation and existing guidance, then document a supported recommendation about table size and suitability; done means the guidance answers the question with a clear basis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, python
- Domain
- databases, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100