Merged
Conversation
|
Related Documentation 1 document(s) may need updating based on files changed in this PR |
Member
|
我们能否不依赖内核仓库,将依赖的公共代码抽离出来,减小构建体积。 |
Contributor
Author
|
@xuthus5 直接依赖的代码有的还会依赖其它代码,抽离出来可能也是一大堆文件,后续评估后可以考虑,目前考虑先以这样的方式。 |
ea36991 to
5c59a38
Compare
Signed-off-by: royal_111 <royal_111@qq.com>
5c59a38 to
d7dbc48
Compare
xuthus5
approved these changes
Sep 3, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem does this PR solve?
1.Issue Number: fix #10 #14 .
What is changed and how it works?
支持数据导出到本地和远程数据库
用法
1.支持将数据导出txt/csv格式,需要指定数据存储的data目录、wal目录以及数据库名称,可选参数:表名、保留策略、时间戳范围、压缩数据等
使用示例如下:
2.支持断点续传:导出任务中断后再次启动时,自动跳过已完成的 TSSP 文件(例如已导出 4/9 个文件),并从后续文件(第 5 个)继续导出,确保数据导出的幂等性和资源高效利用。
3.支持将a节点的数据导出到b节点(跨数据库)
Checklist:
✅ My code follows the style guidelines of this project
✅ I have performed a self-review of my own code
✅ I have commented my code, particularly in hard-to-understand areas
❌ I have made corresponding changes to the documentation
✅ My changes generate no new warnings
❌ I have added tests that prove my fix is effective or that my feature works
✅ New and existing unit tests pass locally with my changes
✅ Any dependent changes have been merged and published in downstream modules