Skip to content
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

[前端]增加Truncate数据功能,实时数仓重新刷流需要清除历史数据(bin/kafka-delete-records.sh) #1043

Closed
ZQKC opened this issue Jun 6, 2023 · 2 comments · Fixed by #1062
Assignees
Labels
P0 优先级:高 type: feature 新增特性
Milestone

Comments

@ZQKC
Copy link
Collaborator

ZQKC commented Jun 6, 2023

No description provided.

@ZQKC ZQKC added the type: feature 新增特性 label Jun 6, 2023
@zhugezifang
Copy link
Contributor

我来试着完成下这个feature

zhugezifang pushed a commit to zhugezifang/KnowStreaming that referenced this issue Jun 21, 2023
zhugezifang pushed a commit to zhugezifang/KnowStreaming that referenced this issue Jun 21, 2023
zhugezifang pushed a commit to zhugezifang/KnowStreaming that referenced this issue Jun 21, 2023
@ZQKC ZQKC linked a pull request Jun 26, 2023 that will close this issue
zhugezifang pushed a commit to zhugezifang/KnowStreaming that referenced this issue Jun 27, 2023
ZQKC pushed a commit that referenced this issue Jun 27, 2023
增加Truncate数据功能(#1043)

目前已经完成后端部分,前端待补充。

---------

Co-authored-by: duanxiaoqiu <[email protected]>
@ZQKC ZQKC reopened this Jun 27, 2023
@ZQKC
Copy link
Collaborator Author

ZQKC commented Jun 27, 2023

前端待完成。

@ZQKC ZQKC changed the title [前后端]增加Truncate数据功能,实时数仓重新刷流需要清除历史数据(bin/kafka-delete-records.sh) [前端]增加Truncate数据功能,实时数仓重新刷流需要清除历史数据(bin/kafka-delete-records.sh) Jun 27, 2023
@velee velee added the P0 优先级:高 label Jul 27, 2023
@velee velee added this to the v3.4.0 milestone Jul 27, 2023
Wyb7290 added a commit to Wyb7290/KnowStreaming that referenced this issue Sep 10, 2023
lucasun added a commit that referenced this issue Sep 14, 2023
请不要在没有先创建Issue的情况下创建Pull Request。

## 变更的目的是什么

XXXXX

## 简短的更新日志

XX

## 验证这一变化

XXXX

请遵循此清单,以帮助我们快速轻松地整合您的贡献:

* [ ] 一个 PR(Pull Request的简写)只解决一个问题,禁止一个 PR 解决多个问题;
* [ ] 确保 PR 有对应的 Issue(通常在您开始处理之前创建),除非是书写错误之类的琐碎更改不需要 Issue ;
* [ ] 格式化 PR 及 Commit-Log 的标题及内容,例如 #861 。PS:Commit-Log 需要在 Git Commit
代码时进行填写,在 GitHub 上修改不了;
* [ ] 编写足够详细的 PR 描述,以了解 PR 的作用、方式和原因;
* [ ] 编写必要的单元测试来验证您的逻辑更正。如果提交了新功能或重大更改,请记住在 test 模块中添加 integration-test;
* [ ] 确保编译通过,集成测试通过;
@ZQKC ZQKC closed this as completed Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 优先级:高 type: feature 新增特性
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants