Repository navigation
WIP: Add Performing Daily Operations with ColdFront - #110
susan-pgedge wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Up to standards ✅🟢 Issues
|
| partitions and dropping or detaching expired ones - with no Iceberg | ||
| or DuckDB involved. | ||
|
|
||
| Regardless of mode, normal `SELECT`, `INSERT`, `UPDATE`, and `DELETE` |
There was a problem hiding this comment.
I don't find this paragraph relevant at all in this spot, and the mention of RETURNING is confusing.
There was a problem hiding this comment.
What you see here is just an early draft - I told Claude to (based on your content) provide an outline/reference for the steps that a user will need to perform on a day to day basis to use ColdFront. Your usage guide is action packed, but too hard to wade through on a daily basis - we might want to break the sections apart even, into other pages for ease of use and maintenance.
Summary
(
docs/maintaining_coldfront.md), covering the full lifecycle of adeployment: getting it running (pointer to Installing and
Configuring ColdFront), using the three table modes day to day,
scheduling the archiver/partitioner/compactor cron jobs, and
ongoing operational upkeep (access grants, Lakekeeper's encryption
key, mesh/bakery health, vended credentials).
This is a work in progress: the "Getting ColdFront Running"
section is complete (it just points at the existing install/configure
guide), but the other three sections are currently a bullet-point
outline to be expanded into full content in follow-up commits.
Test plan
mkdocs build --strictpasses locally