-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Refactor] Refactor GlobalStateMgr #6268
[Refactor] Refactor GlobalStateMgr #6268
Conversation
run starrocks_fe_unittest |
run starrocks_fe_unittest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
result.add(frontend); | ||
} | ||
} | ||
private LocalMetastore localMetastore; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: how about moving this into metadatamgr?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This global instance is used in this stage, and the usage method will be uniformly rectified later
[FE PR Coverage check]😞 fail : 41 / 310 (13.23%) file detail
|
Goals: - Refactoring GlobalStateMgr (the original Fe catalog) is to prepare for building the connector framework. - Reduce globalstatemgr redundant code, The original code is reduced from 8000 lines to 3000 lines. Most of the code in globalstatemgr is transferred to three parts: - NodeMgr: It is mainly used to manage Fe/Be/Broker, heartbeat and Fe start BDB nodes. - LocalMetastore: It is mainly responsible for managing metadata related to internal catalog. It includes Cluster/Database/Table/Partition/Tablet/ Replica, and implements the API of `ConnectorMetadata` - XXXMgr in GlobalStateMgr Some methods, such as loadxxx and savexxx, transfer them to the corresponding manager instance. For example, transfer `loadExportJob()` and `saveExportJob()` in `GlobalStateMgr` to `ExportMgr`
…tarRocks#6315) * Add doc for covar/corr etc funtion Signed-off-by: before-Sunrise <unclejyj@gmail.com> --------- Signed-off-by: before-Sunrise <unclejyj@gmail.com> Co-authored-by: evelyn.zhaojie <everlyn.zhaojie@gmail.com> (cherry picked from commit c3f1994) Co-authored-by: before-Sunrise <71162020+before-Sunrise@users.noreply.github.com> (cherry picked from commit e0d425c) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
…s#6268) (StarRocks#6315)" (StarRocks#6316) This reverts commit 2d87a5e.
* Add doc for covar/corr etc funtion Signed-off-by: before-Sunrise <unclejyj@gmail.com> --------- Signed-off-by: before-Sunrise <unclejyj@gmail.com> Co-authored-by: evelyn.zhaojie <everlyn.zhaojie@gmail.com> (cherry picked from commit c3f1994) Co-authored-by: before-Sunrise <71162020+before-Sunrise@users.noreply.github.com>
Signed-off-by: stephen-shelby stephen5217@163.com
What type of PR is this:
Which issues of this PR fixes :
related with: #6272
related with #5062
Problem Summary(Required) :
Goals:
Most of the code in globalstatemgr is transferred to three parts:
It is mainly used to manage Fe/Be/Broker, heartbeat and Fe start BDB nodes.
It is mainly responsible for managing metadata related to internal catalog. It includes Cluster/Database/Table/Partition/Tablet/ Replica, and implements the API of
ConnectorMetadata
Some methods, such as loadxxx and savexxx, transfer them to the corresponding manager instance. For example, transfer
loadExportJob()
andsaveExportJob()
inGlobalStateMgr
toExportMgr