Closed shuiyisong closed 3 months ago
The recent updates bring two primary changes: First, the yaml_string
function in the ETL processor module has been adjusted to no longer trim whitespace, preserving the original string from the YAML document. Second, commentary in the test file for Python built-ins has been refined for clarity without changing any code logic.
File | Change Summary |
---|---|
src/pipeline/src/etl/processor/mod.rs | Removed whitespace trimming from yaml_string function. |
src/script/src/python/rspython/builtins/... | Improved comments for clarity in test.rs . |
In code's winding ways so stern,
A change was made, let whitespace return.
YAML strings kept whole and fair,
With comments rewritten with utmost care.
Celebrate, a rabbit's cheer,
For clarity and data dear.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.68%. Comparing base (
b5c6c72
) to head (757a691
).
There are some typos
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Pipeline engine uses
yaml_rust
to parse raw yaml file. It already trims spaces in value as possible, but keeps spaces if deliberately included between quotes. For exampleIn pipeline engine transformation there is a extra
trim()
that removes the space, which is neither necessary nor compatible with the origin behavior of yaml.This pr mainly fixes this issue by removing the
trim()
invoke.Checklist
Summary by CodeRabbit
Bug Fixes
Documentation