Abacn commented on issue #40079: URL: https://github.com/apache/beam/issues/40079#issuecomment-5606037179
I've been thinking about this issue, but didn't find a good solution within current Beam portable schema framework. A quick solution is to exclude tuple from resolving to ArrayType, but fallback to Any. This would solve both scenario but currently working scenarios e.g. `tuple[str, ...]` or `tuple[int, int]` now all fallbacks to FastPrimitiveType A second solution would be to introduce logical types to represent a Python tuple - variable length tuple is backed by ArrayType, and convert to tuple - fixed length tuple is backed by Row (with anonymous, internal only field names) (internal bug context: b/518498022) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
