This is an automated email from the ASF dual-hosted git repository.
fjy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git
The following commit(s) were added to refs/heads/master by this push:
new d87840d Minor updates to documentation. (#8665)
d87840d is described below
commit d87840d894bb3c1a9283002573e3909a943f0d30
Author: Abhishek Radhakrishnan <abhishek.r...@gmail.com>
AuthorDate: Sat Oct 12 09:11:03 2019 -0700
Minor updates to documentation. (#8665)
---
docs/design/segments.md | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/docs/design/segments.md b/docs/design/segments.md
index bd945f5..e783775 100644
--- a/docs/design/segments.md
+++ b/docs/design/segments.md
@@ -29,7 +29,7 @@ interval, where the time interval is configurable in the
`segmentGranularity` parameter of the
[`granularitySpec`](../ingestion/index.md#granularityspec). For Druid to
operate well under heavy query load, it is important for the segment
-file size to be within the recommended range of 300mb-700mb. If your
+file size to be within the recommended range of 300MB-700MB. If your
segment files are larger than this range, then consider either
changing the granularity of the time interval or partitioning your
data and tweaking the `targetPartitionSize` in your `partitionsSpec`
@@ -73,8 +73,7 @@ indexes* allow for quick filtering operations (specifically,
bitmaps
are convenient for quickly applying AND and OR operators). Finally,
the list of values in 2 is needed for *group by* and *TopN*
queries. In other words, queries that solely aggregate metrics based
-on filters do not need to touch the list of dimension values stored in
-2.
+on filters do not need to touch the list of dimension values stored in 2.
To get a concrete sense of these data structures, consider the ‘page’
column from the example data above. The three data structures that
@@ -216,7 +215,7 @@ foo_2015-01-01/2015-01-02_v1_1
foo_2015-01-01/2015-01-02_v1_2
```
-In the example segments above, the dataSource = foo, interval =
2015-01-01/2015-01-02, version = v1, partitionNum = 0.
+In the example segments above, the `dataSource = foo`, `interval =
2015-01-01/2015-01-02`, `version = v1`, and `partitionNum = 0`.
If at some later point in time, you reindex the data with a new schema, the
newly created segments will have a higher version id.
```
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org
For additional commands, e-mail: commits-h...@druid.apache.org
