You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@paimon.apache.org by "jackylee-ch (via GitHub)" <gi...@apache.org> on 2026/08/03 13:17:42 UTC
[PR] fix(spec): say precision, not length, in two type-parse errors [paimon-rust]
jackylee-ch opened a new pull request, #662:
URL: https://github.com/apache/paimon-rust/pull/662
`LocalZonedTimestampType::from_str` and `TimeType::from_str` both parse a
`precision_str` into a `precision` field, but report `"Invalid <T> length. Unable to
parse length as a u32."` The sibling `TimestampType::from_str` already has the right
wording, so this copies it. `BINARY`, `CHAR`, `VARBINARY` and `VARCHAR` keep
"length" — those really are lengths.
Also a README typo (`bug reportor` -> `bug report`), `rust` -> `Rust` in the tagline
to match `docs/mkdocs.yml`, and a trailing space.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@paimon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] fix(spec): say precision, not length, in two type-parse errors [paimon-rust]
Posted by "JingsongLi (via GitHub)" <gi...@apache.org>.
JingsongLi merged PR #662:
URL: https://github.com/apache/paimon-rust/pull/662
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@paimon.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org