tool
/
starrocks
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[Doc] add behavior change to 2.5 rn (#17084) 

* [Doc] add behavior change to 2.5 rn

Signed-off-by: evelynzhaojie <everlyn.zhaojie@gmail.com>

* update of system variables

Signed-off-by: evelynzhaojie <everlyn.zhaojie@gmail.com>

---------

Signed-off-by: evelynzhaojie <everlyn.zhaojie@gmail.com>
This commit is contained in:
evelyn.zhaojie 2023-01-31 11:34:07 +08:00 committed by GitHub
parent 2d915f3299
commit fbe9339d2a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 13 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/reference/System_variable.md
View File

@ -153,29 +153,31 @@ SELECT /*+ SET_VAR(query_timeout = 1) */ sleep(3);
* forward_to_master
Used to set whether some commands will be forwarded to the leader FE node for execution. The default value is false, meaning no forwarding. There are multiple FE nodes in StarRocks, one of which is the leader node. Normally, users can connect to any FE node for full-featured operation. However, some information is only available from the leader FE node.
Used to specify whether some commands will be forwarded to the leader FE for execution. The default value is `false`, meaning not forwarding to the leader FE. There are multiple FEs in a StarRocks cluster, one of which is the leader FE. Normally, users can connect to any FE for full-featured operations. However, some information is only available on the leader FE.
For example, if the `SHOW BACKENDS;` commend is not forwarded to the leader FE node, only basic information (e.g., whether the node is alive or not) can be seen. Forwarding to the leader FE can get more detailed information including the node start time, last heartbeat time, etc.
For example, if the SHOW BACKENDS command is not forwarded to the leader FE, only basic information (for example, whether the node is alive) can be viewed. Forwarding to the leader FE can get more detailed information including the node start time and last heartbeat time.
The commands affected by this parameter are as follows:
* `SHOW FRONTENDS`: Forwarding to leader allows users to view the last heartbeat message.
* SHOW FRONTENDS: Forwarding to the leader FE allows users to view the last heartbeat message.
* `SHOW BACKEND`: Forwarding to leader allows users to view the boot time, last heartbeat information, and disk capacity information.
* SHOW BACKENDS: Forwarding to the leader FE allows users to view the boot time, last heartbeat information, and disk capacity information.
* `SHOW BROKER`: Forwarding to leader allows users to view the boot time and last heartbeat information.
* SHOW BROKER: Forwarding to the leader FE allows users to view the boot time and last heartbeat information.
* `SHOW TABLET`;
* `ADMIN SHOW REPLICA DISTRIBUTION`;
* `ADMIN SHOW REPLICA STATUS`: Forwarding to leader allows users to view the tablet information stored in the leader FE metadata. Normally, the tablet information in the different FE metadata should be the same. In case of a problem, you can use this method to compare the differences in metadata of the current FE and the leader FE.
* SHOW TABLET
* `Show PROC`: Forwarding to leader allows users to view the PROC information stored in the metadata. This is mainly used for metadata comparison.
* ADMIN SHOW REPLICA DISTRIBUTION
* ADMIN SHOW REPLICA STATUS: Forwarding to the leader FE allows users to view the tablet information stored in the metadata of the leader FE. Normally, the tablet information should be the same in the metadata of different FEs. If an error occurs, you can use this method to compare the metadata of the current FE and the leader FE.
* Show PROC: Forwarding to the leader FE allows users to view the PROC information stored in the metadata. This is mainly used for metadata comparison.
* hash_join_push_down_right_table
Used to control whether the data of the left table can be filtered by using the filter condition against the right table in the Join query. If so, it can reduce the amount of data that needs to be processed during the query.
If “true”, indicating the operation is allowed and the system will decide whether the left table can be filtered. If “false”, indicating the operation is disabled. The default value is true.
`true` indicates the operation is allowed and the system decides whether the left table can be filtered. `false` indicates the operation is disabled. The default value is `true`.
* init_connect

1
docs/release_notes/release-2.5.md
View File

@ -71,6 +71,7 @@ The following bugs are fixed:
- Renamed session variable `is_report_success` to `enable_profile`, which can be queried using the SHOW VARIABLES statement.
- Added four reserved keywords: `CURRENT_DATE`, `CURRENT_TIME`, `LOCALTIME`, and `LOCALTIMESTAMP`. [# 14319](https://github.com/StarRocks/starrocks/pull/14319)
- The maximum length of table and database names can be up to 1023 characters. [# 14929](https://github.com/StarRocks/starrocks/pull/14929) [# 15020](https://github.com/StarRocks/starrocks/pull/15020)
- BE configuration items `enable_event_based_compaction_framework` and `enable_size_tiered_compaction_strategy` are set to `true` by default, which significantly reduces compaction overheads when there are a large number of tablets or a single tablet has large data volume.
### Upgrade Notes