EdwardShen125 commented on issue #566: URL: https://github.com/apache/arrow-go/issues/566#issuecomment-6541019301
I'd like to take this. I tested current main against pyarrow 26: every direct-key config I tried works now, pyarrow files read fine in Go (uniform GCM/CTR, AAD prefix, plaintext footer), and pyarrow reads a Go-written file. My guess is #596/#1390/#1412 solved most of that. What still fails is KMS files. pyarrow's CryptoFactory writes PKMT1 key material with a wrapped DEK, and arrow-go can't parse or unwrap it, so footer decryption fails unless you write a custom retriever (zeroshade posted one in #596). I'll start with the harness from this thread: Go tests that call pyarrow to generate files for each config and check reads in both directions. Tests skip when pyarrow isn't installed. Not sure how you want this in CI, I'll ask in the PR. #1438-style fixtures test fixed files, this would also test the current pyarrow release. After that, the KMS part: parsing and unwrapping PKMT1. Should that go into the library or stay an example retriever? @daniel-adam-tfs still planning to take this, or can I take it over? -- 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]
