Part & Pin for the Inverted Index Win "How to Partition Inverted Indexes in CockroachDB" Recently I worked with a CockroachDB user who had a GDPR locality requirement. Naturally CockroachDB was a fit since it sports geo-partitioning capabilities for data and objects. However, the user ran into a snafu where they could not partition and localize data in inverted indexes. The example they had was customer data existed in a JSONB data column that had an inverted index on it. The data in the table was already partitioned by country and pinned to servers / nodes that were in that country. So they were good with table partitioning and pinning. But the data in the inverted index could theoretically be distributed anywhere in the cluster and also needed to be partitioned and pinned to the proper locality. I.e. A German customer must remain in Germany. This caught me by surprise as well that you can not partition inverted indexes out of the box with CockroachDB. I
Comments
Post a Comment