Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add global and regional tables to patterns docs #10465

Merged
merged 1 commit into from
May 10, 2021

Commits on May 10, 2021

  1. Add global and regional tables to patterns docs

    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 committed May 10, 2021
    Configuration menu
    Copy the full SHA
    f89ebe4 View commit details
    Browse the repository at this point in the history