Lars-Kristian Svenøy
07/19/2022, 4:16 PMKishore G
Lars-Kristian Svenøy
07/19/2022, 4:28 PMKishore G
Lars-Kristian Svenøy
07/19/2022, 4:30 PMKishore G
Lars-Kristian Svenøy
07/19/2022, 4:35 PMentityId: String
groupIds: List of strings
status: String
And a query looking like this
SELECT COUNT(*) FROM table WHERE entityId = 'ID' AND groupIds CONTAINS 'group_1' AND status = 'ONLINE'
If there are 2 billion rows here, this could be a very intense query. If the star tree index could pre-aggregate on each value in groupId, you could potentially make this lookup much more performant.
This is pretty much a problem we have today. A group can contain multiple entities, and an entity can be in multiple groups. There is a many to many relationship, meaning this is a dynamic constraint of our queries.
Some queries will ignore group, (that would be the star node), while some need to access the aggregation on a group basis.Lars-Kristian Svenøy
07/19/2022, 4:35 PMLars-Kristian Svenøy
07/19/2022, 4:36 PMKishore G
Kishore G
Lars-Kristian Svenøy
07/20/2022, 2:56 PMLars-Kristian Svenøy
07/20/2022, 2:57 PMLars-Kristian Svenøy
07/20/2022, 2:57 PMLars-Kristian Svenøy
07/20/2022, 2:58 PMKishore G
Lars-Kristian Svenøy
07/21/2022, 10:32 AMLars-Kristian Svenøy
07/21/2022, 10:43 AM