a584807f1f
* feat(influxdb3): Core/Enterprise: Upgrade instance or cluster:- Addresses recent internal requests for upgrade steps- Provide examples for Core or Enterprise single node (instance)- Provide steps recommended by Engineering and examples- Link from related pages * Apply suggestion from @sanderson Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com> * Apply suggestion from @sanderson Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com> * Apply suggestion from @sanderson Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com> * Apply suggestion from @sanderson Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com> * Apply suggestion from @sanderson Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com> * docs(enterprise): clarify catalog version constraints for v3.3.x to v3.4.x upgrade - Specify that catalog modification constraint applies when upgrading from v3.3.x (or earlier) to v3.4.x - Add troubleshooting section noting that different version transitions may have different constraints - Direct users to check release notes for version-specific upgrade requirements Resolves review comment from hiltontj about catalog version boundaries. --------- Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| databases | ||
| distinct-value-cache | ||
| last-value-cache | ||
| object-storage | ||
| query-system-data | ||
| tables | ||
| tokens | ||
| _index.md | ||
| backup-restore.md | ||
| mcp-server.md | ||
| performance-tuning.md | ||
| upgrade.md | ||