docs: fix small error #15158
Merged
docs: fix small error #15158
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I only fixed a small error in docs.
github-actions
bot
added
the
kind/docs
Contributor
|
PR approved by anyone and no changes requested. |
Collaborator
|
There are confilcts in this PR, could you plz resolve it? Thanks a lot! |
Zmaul04
reviewed
Jan 13, 2023
| Add a count column and import the data with the column value **equal to 1**. The result of `select count (*) from table;`is equivalent to `select sum (count) from table;` The query efficiency of the latter is much higher than that of the former. However, this method also has limitations, that is, users need to guarantee that they will not import rows with the same AGGREGATE KEY column repeatedly. Otherwise, `select sum (count) from table;`can only express the number of rows originally imported, not the semantics of `select count (*) from table;` | ||
|
|
||
| Another way is to **change the aggregation type of the count column above to REPLACE, and still weigh 1**. Then`select sum (count) from table;` and `select count (*) from table;` the results will be consistent. And in this way, there is no restriction on importing duplicate rows. | ||
| Another way is to **change the aggregation type of the count column above to REPLACE, and still weigh 1**. Then `select sum (count) from table;` and `select count (*) from table;` the results will be consistent. And in this way, there is no restriction on importing duplicate rows. |
| * 1./home/disk1/doris,medium:hdd : The storage medium is HDD; | ||
| * 2./home/disk2/doris,medium:ssd : The storage medium is SSD. | ||
|
|
||
| * BE webserver_port configuration |
There was a problem hiding this comment.
src/Essentials/src/Connectivity/Connectivity.uwp.cs
| * BE webserver_port configuration | ||
|
|
||
| If the BE componet is installed in hadoop cluster, you need to change the configuration `webserver_port=8040` in be.conf to avoid port conflicts. | ||
| If the BE component is installed in hadoop cluster, you need to change configuration `webserver_port=8040` to avoid port used. |
| If the BE componet is installed in hadoop cluster, you need to change the configuration `webserver_port=8040` in be.conf to avoid port conflicts. | ||
| If the BE component is installed in hadoop cluster, you need to change configuration `webserver_port=8040` to avoid port used. | ||
|
|
||
| * Set JAVA_HOME environment variable |
| * 1./home/disk1/doris,medium:hdd : The storage medium is HDD; | ||
| * 2./home/disk2/doris,medium:ssd : The storage medium is SSD. | ||
|
|
||
| * BE webserver_port configuration |
| Add a count column and import the data with the column value **equal to 1**. The result of `select count (*) from table;`is equivalent to `select sum (count) from table;` The query efficiency of the latter is much higher than that of the former. However, this method also has limitations, that is, users need to guarantee that they will not import rows with the same AGGREGATE KEY column repeatedly. Otherwise, `select sum (count) from table;`can only express the number of rows originally imported, not the semantics of `select count (*) from table;` | ||
|
|
||
| Another way is to **change the aggregation type of the count column above to REPLACE, and still weigh 1**. Then`select sum (count) from table;` and `select count (*) from table;` the results will be consistent. And in this way, there is no restriction on importing duplicate rows. | ||
| Another way is to **change the aggregation type of the count column above to REPLACE, and still weigh 1**. Then `select sum (count) from table;` and `select count (*) from table;` the results will be consistent. And in this way, there is no restriction on importing duplicate rows. |
Zmaul04
reviewed
Jan 14, 2023
| * 1./home/disk1/doris,medium:hdd : The storage medium is HDD; | ||
| * 2./home/disk2/doris,medium:ssd : The storage medium is SSD. | ||
|
|
||
| * BE webserver_port configuration |
| ``` | ||
|
|
||
| As you can see, this is a typical fact table of user information and access behavior. | ||
| In general star model, user information and access behavior are stored in dimension table and fact table respectively. Here, in order to explain Doris's data model more conveniently, we store the two parts of information in a single table. |
| When we import data, the same rows and aggregates into one row for the Key column, while the Value column aggregates according to the set `AggregationType`. `AggregationType`currently has the following four ways of aggregation: | ||
| When we import data, the same rows and aggregates into one row for the Key column, while the Value column aggregates according to the set `AggregationType`. `AggregationType` currently has the following four ways of aggregation: | ||
|
|
||
| 1. SUM: Sum, multi-line Value accumulation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I only fixed a small error in docs.
Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...