Isolation Key Overview
An overview of isolation key-based object groups and their benefits
You create object groups to define the cloud object storage files to index by using object name prefixes and/or regular expressions to uniquely identify the files.
One object group can filter and index many source objects that have the same format and compression using the same index rules. You could create multiple separate object groups to index different collections of source files, but this is typically best when source file format schemas are different, the input source file filters are different, or if factors like compression or indexing rules are different.
If the format, compression, and indexing rules are the same for a collection of object store files, it could be possible and more efficient to use one live object group to do the work of many object groups. For live object groups, each with its own small reserve of compute resources, that minimal set of resources can add up quickly, limiting the compute resources available for other tasks like querying.
The isolation key feature can keep the index data segregated in slices for data isolation and visibility/analysis needs.
Carefully plan the regular expressions for the object group filter and for the isolation key rule to ensure that you have a good storage object file match for the overall group, and that the isolation key expression creates the correct separations that will be used as filters by the Refinery views (created later).
Updated about 2 months ago
Choosing to use isolation keys, or not: