This is an automated email from the ASF dual-hosted git repository.

abhishek pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git


The following commit(s) were added to refs/heads/master by this push:
     new 60b4fa0f75 Docs: Fix column name in ingestion rollup doc (#12036)
60b4fa0f75 is described below

commit 60b4fa0f753043bddb45bb508aadb2dd55433584
Author: Kashif Faraz <[email protected]>
AuthorDate: Tue May 10 05:05:59 2022 -0700

    Docs: Fix column name in ingestion rollup doc (#12036)
    
    Fix the referred column name from "count" to "num_rows" as "count" vs. 
"COUNT(*)" might be a little confusing in this example.
---
 docs/ingestion/rollup.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/ingestion/rollup.md b/docs/ingestion/rollup.md
index 6fb5204f48..18e9d0d01b 100644
--- a/docs/ingestion/rollup.md
+++ b/docs/ingestion/rollup.md
@@ -40,10 +40,10 @@ If you have conflicting needs for different use cases, you 
can create multiple t
 
 ## Maximizing rollup ratio
 
-To measure the rollup ratio of a datasource compare the number of rows in 
Druid (`COUNT`) with the number of ingested events. For example, run a [Druid 
SQL](../querying/sql.md) query where "count" refers to a `count`-type metric 
generated at ingestion time as follows:
+To measure the rollup ratio of a datasource, compare the number of rows in 
Druid (`COUNT`) with the number of ingested events. For example, run a [Druid 
SQL](../querying/sql.md) query where "num_rows" refers to a `count`-type metric 
generated at ingestion time as follows:
 
 ```sql
-SELECT SUM("cnt") / (COUNT(*) * 1.0) FROM datasource
+SELECT SUM("num_rows") / (COUNT(*) * 1.0) FROM datasource
 ```
 The higher the result, the greater the benefit you gain from rollup. See 
[Counting the number of ingested events](schema-design.md#counting) for more 
details about how counting works with rollup is enabled.
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to