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: Disable sloppyPattern in PipeHistoricalDataRegionTsFileAndDeletionExtractor & Fix TsFileInsertionEventTableParserTabletIterator does not perform type conversion when parsing data of Date type #13934

Merged
merged 2 commits into from
Oct 29, 2024

Conversation

luoluoyuyu
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-assigned this Oct 28, 2024
@SteveYurongSu SteveYurongSu changed the title Pipe: Fixed the issue that TsFileInsertionEventTableParserTabletIterator did not perform type conversion when parsing Date type Pipe: Disable sloppyPattern in PipeHistoricalDataRegionTsFileAndDeletionExtractor & Fix TsFileInsertionEventTableParserTabletIterator does not perform type conversion when parsing data of Date type Oct 29, 2024
@SteveYurongSu SteveYurongSu merged commit c372cab into apache:master Oct 29, 2024
27 checks passed
@luoluoyuyu luoluoyuyu deleted the fix-pipe-parser branch October 29, 2024 11:05
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.

2 participants