Merged
Conversation
jt2594838
approved these changes
Mar 31, 2026
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
2 participants
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.
Summary
Fix path parsing inconsistency between ANTLR4 and fallback flows.
What changed
Moved Path parsing into library .cc (library-controlled behavior).
Fixed fallback split_device_id_string to normalize split results instead of returning raw token splits.
Added unit test for root.sg1.FeederA fallback semantics.
Previously, ENABLE_ANTLR4 was checked in headers, so it depended on user-side compile flags and could be ignored in real usage.
Impact
Prevents device/measurement path mismatches that could make IoTDB queries return empty results even when TsFile content is valid.