Partitioning for Inverted Indexes

Knew from sql: Partitioning for Inverted Indexes · Issue #43643 · cockroachdb/cockroach · GitHub that right now inverted index does not support partition.

Want to know what’s the difference between partition inverted index and non-partition index, for both case the functionality are the same? partition inverted index would gain better performance right?

thank you very much.

“kcheng.mvp via Cockroach Labs” cockroachlabs@discoursemail.com
writes:

Want to know what’s the difference between partition inverted index
and non-partition index, for both case the functionality are the same?
partition inverted index would gain better performance right?

Hi kcheng.mvp!

Basically yes AIUI. Partitioning is used to exercise finer control over
where the data underlying the index is stored. You can use this control
to get better latencies, etc. in geo-distributed clusters.

More information is also in the docs at
https://www.cockroachlabs.com/docs/stable/partitioning:

CockroachDB allows you to define table partitions, thus giving you
row-level control of how and where your data is stored. Partitioning
enables you to reduce latencies and costs and can assist in meeting
regulatory requirements for your data.

thank you very much.

np!