Update "Define Table Partitions" to point most users to new multi-region features #10319

rmloveland · 2021-04-13T20:43:17Z

The Define table partitions page talks a lot about
geo-partitioning and reducing latency, which most users can now
better achieve using the new multi-region patterns.

Estimated scope of work:

At minimum, add a note to the page under "Why use table partitioning" saying that most users should use the new MR abstractions instead, rather than doing manual partitioning
We should probably explain that the new MR patterns are implemented on top of partitioning, so you only need to read this stuff if you care about that, or have some advanced use case, etc.
???

Fixes #9268 Fixes #9266 Fixes #9265 Fixes #9264 Fixes #10425 Fixes #10319 Addresses #10051 Addresses #10401 Addresses #10461 Addresses #10463 Summary of changes: - Update multi-region "topology patterns" as follows: - Deemphasize "topology" for these patterns, since it really isn't - it's per-table - Add "global tables" as a pattern - Add "regional tables" as a pattern - Remove "duplicate indexes" and "geo-partitioned foos" pages and have them redirect to the above, as appropriate - Fix up ~all links in the docs to point to the new things - Update mentions of partitioning throughout the docs to note that most users should use new v21.1+ multi-region capabilities instead of explicit partitioning - Also removed mention of partitioning from several places as part of deemphasing explicit partitioning generally, since most use cases are covered by MR abstractions - Update `cockroach demo` to deemphasize partitioning and point to new MR things - Update disaster recovery pages to mention most users of new deployments should just use multi-region survival goals - Update various licensing docs to point to the new multi-region things - Update replication reports to mention the new MR things, in lieu of further updates - Renamed a bunch of links that used the phrase "geo-partitioning" to refer to the multi-region latency tutorial, which now goes by the name "Multi-Region Performance" - Note: we explicitly did *not* touch anything related to the multi-region Flask app, since that work is happening via #10394

Fixes #9268 Fixes #9266 Fixes #9265 Fixes #9264 Fixes #10425 Fixes #10319 Addresses #10051 Addresses #10401 Addresses #10461 Addresses #10463 Summary of changes: - Update "topology patterns" docs as follows: - Move them as a sub-section under "Multi-Region Capabilities", since they are mostly relevant to multi-region usage - Deemphasize "topology" for these patterns, since these are not network topologies, they are mostly per-table configurable behaviors - Add "global tables" to replace the "duplicate indexes" page - Add "regional tables" to replace the "geo-partitioned XYZ" pages - Fix up ~all links in the docs to point to the new things - Update mentions of partitioning throughout the docs to note that most users should use the new v21.1+ multi-region capabilities instead of explicit partitioning - Also removed mention of partitioning from several places as part of deemphasing explicit partitioning generally, since most use cases are covered by multi-region abstractions - Update the 'Cost-Based Optimizer' page to remove the old skool "nearest index" partitioning stuff, since now we have GLOBAL tables - This required removing links to the above from all the "enterprise features" lists and replacing with links to the new 'Multi-Region Capabilities' page - Update `cockroach demo` to deemphasize partitioning and point to new multi-region things - Update disaster recovery pages to mention most users of new deployments should just use multi-region survival goals - Update various licensing docs to point to the new multi-region things - Update replication reports to mention the new multi-region things, in lieu of further updates - Renamed a bunch of links that used the phrase "geo-partitioning" to refer to the multi-region latency tutorial, which now goes by the name "Multi-Region Performance" - Note: we explicitly did *not* touch anything related to the multi-region Flask app, since that work is happening via #10394

Fixes #9268 Fixes #9266 Fixes #9265 Fixes #9264 Fixes #10425 Fixes #10319 Addresses #10051 Addresses #10401 Addresses #10461 Addresses #10463 Summary of changes: - Update "topology patterns" docs as follows: - Move them as a sub-section under "Multi-Region Capabilities", since they are mostly relevant to multi-region usage - Deemphasize "topology" for these patterns, since these are not network topologies, they are mostly per-table configurable behaviors - Add "global tables" to replace the "duplicate indexes" page - Add "regional tables" to replace the "geo-partitioned XYZ" pages - Fix up ~all links in the docs to point to the new things - Update mentions of partitioning throughout the docs to note that most users should use the new v21.1+ multi-region capabilities instead of explicit partitioning - Also removed mention of partitioning from several places as part of deemphasing explicit partitioning generally, since most use cases are covered by multi-region abstractions - Update the 'Cost-Based Optimizer' page to remove the old skool "nearest index" partitioning stuff, since now we have GLOBAL tables - This required removing links to the above from all the "enterprise features" lists and replacing with links to the new 'Multi-Region Capabilities' page - Update `cockroach demo` to deemphasize partitioning and point to new multi-region things - Update disaster recovery pages to mention most users of new deployments should just use multi-region survival goals - Update various licensing docs to point to the new multi-region things - Update replication reports to mention the new multi-region things, in lieu of further updates - Renamed a bunch of links that used the phrase "geo-partitioning" to refer to the multi-region latency tutorial, which now goes by the name "Multi-Region Performance" - Updated 'ALTER TABLE ... SET LOCALITY REGIONAL BY ROW' to include info about locality optimized search - Note: we explicitly did *not* touch anything related to the multi-region Flask app, since that work is happening via #10394

rmloveland self-assigned this Apr 13, 2021

rmloveland added the A-multi-region label Apr 13, 2021

rmloveland added this to the 21.1 milestone Apr 13, 2021

rmloveland mentioned this issue Apr 29, 2021

Add global and regional tables to patterns docs #10465

Merged

rmloveland closed this as completed in #10465 May 10, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update "Define Table Partitions" to point most users to new multi-region features #10319

Update "Define Table Partitions" to point most users to new multi-region features #10319

rmloveland commented Apr 13, 2021

Update "Define Table Partitions" to point most users to new multi-region features #10319

Update "Define Table Partitions" to point most users to new multi-region features #10319

Comments

rmloveland commented Apr 13, 2021