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

Pipe: Cancelled useless flush at historical extractor & enable gracefully dropping pipe and avoid pre-mature report & fixed potential lose point bug caused by cancelled flush by historical extractor #11974

Closed
wants to merge 19 commits into from

Conversation

Caideyipi
Copy link
Contributor

Description

As the title said.


This PR has:

  • been self-reviewed.
    • concurrent read
    • concurrent write
    • concurrent read and write
  • added documentation for new or modified features or behaviors.
  • added Javadocs for most classes and all non-trivial methods.
  • added or updated version, license, or notice information
  • added comments explaining the "why" and the intent of the code wherever would not be obvious
    for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold
    for code coverage.
  • added integration tests.
  • been tested in a test IoTDB cluster.

Key changed/added classes (or packages if there are too many classes) in this PR

@SteveYurongSu SteveYurongSu self-requested a review January 25, 2024 09:04
@SteveYurongSu SteveYurongSu self-assigned this Jan 25, 2024
@Caideyipi Caideyipi changed the title Pipe: fixed potential lose point bug due to cancelled flush at historical extractor Pipe: Cancelled useless flush at historical extractor & enable gracefully dropping pipe and avoid pre-mature report Feb 5, 2024
@Caideyipi Caideyipi changed the title Pipe: Cancelled useless flush at historical extractor & enable gracefully dropping pipe and avoid pre-mature report Pipe: Cancelled useless flush at historical extractor & enable gracefully dropping pipe and avoid pre-mature report & fixed potential lose point bug caused by cancelled flush by historical extractor Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants