Skip to content

Commit 6bed9e1

Browse files
committed
call our theoritcal max vs real
1 parent 0405f3e commit 6bed9e1

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

docs/metrics.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -585,6 +585,8 @@ been observed since the start of the process.
585585
* You must account for the theoretical maximum number of attribute combinations.
586586
* This can be estimated by multiplying the number of possible values for each
587587
attribute.
588+
* If certain attribute combinations are invalid or will never occur in practice,
589+
you can reduce the limit accordingly.
588590

589591
###### Example - Fruit Sales Scenario
590592

@@ -593,9 +595,11 @@ Attributes:
593595
* `name` can be "apple" or "lemon" (2 values)
594596
* `color` can be "red", "yellow", or "green" (3 values)
595597

596-
You may observe up to 2 × 3 = 6 unique attribute sets.
598+
The theoretical maximum is 2 × 3 = 6 unique attribute sets.
597599

598-
**Set the cardinality limit to 6.**
600+
For this example, the simplest approach is to use the theoretical maximum and **set the cardinality limit to 6**.
601+
602+
However, if you know that certain combinations will never occur (for example, if "red lemons" don't exist in your application domain), you could reduce the limit to only account for valid combinations. In this case, if only 5 combinations are valid, **setting the cardinality limit to 5** would be more memory-efficient.
599603

600604
##### Choosing the Right Limit for Delta Temporality
601605

0 commit comments

Comments
 (0)