sungwy commented on issue #2123: URL: https://github.com/apache/iceberg-python/issues/2123#issuecomment-3105370194
Hi @nvartolomei - thanks for raising this issue and thanks for jumping into look into this @kevinjqliu and @kris-gaudel I think if this bug is indeed there, it's a rather serious issue since it would suggest that the field names produced from each language library (Python vs Java) is different, and hence would lead to issues in data accessibility. I've tried replicating this issue with '😎' character and read it using duckdb, and unfortunately I was not able to replicate the issue: https://github.com/apache/iceberg-python/pull/2243 @nvartolomei Could you demonstrate how to replicate this issue? Is the e2e test I've added on that PR, and the one that @kevinjqliu mirrored from Java enough to demonstrate that the field name is sanitized in a duckdb compatible format? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
