This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/skywalking-banyandb.git
The following commit(s) were added to refs/heads/main by this push:
new df34a836 polish doc (#291)
df34a836 is described below
commit df34a83663d66af9687ff484884ceae669c83980
Author: Harry <[email protected]>
AuthorDate: Fri Jun 30 14:40:34 2023 +0800
polish doc (#291)
---
docs/concept/data-model.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/concept/data-model.md b/docs/concept/data-model.md
index 53abbc36..06b719fb 100644
--- a/docs/concept/data-model.md
+++ b/docs/concept/data-model.md
@@ -50,7 +50,7 @@ Every other resource should belong to a group. The `catalog`
indicates which kin
* `MEASURE`: [`Measure`](#streams).
* `STREAM`: [`Stream`](#measures).
-[Group Registration Operations](api-reference.md#groupregistryservice)
+[Group Registration Operations](../api-reference.md#groupregistryservice)
### Measures
@@ -270,9 +270,9 @@ expire_at: '2121-04-15T01:30:15.01Z'
IndexRuleBinding binds IndexRules to a subject, `Stream` or `Measure`. The
time range between `begin_at` and `expire_at` is the effective time.
-[IndexRule Registration Operations](api-reference.md#indexruleregistryservice)
+[IndexRule Registration
Operations](../api-reference.md#indexruleregistryservice)
-[IndexRuleBinding Registration
Operations](api-reference.md#indexrulebindingregistryservice)
+[IndexRuleBinding Registration
Operations](../api-reference.md#indexrulebindingregistryservice)
### Index Granularity
@@ -294,9 +294,9 @@ The indexed target would be the combination of the series
ID and timestamp, whic
The following is a comparison of the indexing granularity, performance, and
flexibility of `Stream` and `Measure` indices:
-| Indexing Granularity | Performance | Flexibility |
-| --- | --- | --- |
+| Indexing Granularity
|
Performance | Flexibility
|
+|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------|
| Measure indices are constructed for each series and are based on the entity
field of the Measure. Each indexed value has to represent a unique seriesID. |
Measure index is faster than Stream index. | Measure index is less flexible and
requires more care when indexing tags that are not part of the entity field. |
-| Stream indices are constructed for each element and are based on the series
ID and timestamp. | Stream index is slower than Measure index. | Stream index
is more flexible than Measure index and can index any tag value. |
+| Stream indices are constructed for each element and are based on the series
ID and timestamp. |
Stream index is slower than Measure index. | Stream index is more flexible than
Measure index and can index any tag value. |
In general, `Measure` indices are faster and more efficient, but they require
more care when indexing tags that are not part of the `entity` field. `Stream`
indices, on the other hand, are slower and take up more space, but they can
index any tag value and do not have the same side effects as `Measure` indices.
