laskoviymishka commented on issue #989: URL: https://github.com/apache/iceberg-go/issues/989#issuecomment-4479477750
@C-Loftus, thanks for jumping in! Honest answer: the sub-issues are mostly a linear chain (#990 → #991 → #992 → #993 → #994 → #995), and the first two are already with @happydave1. So nothing downstream is truly unblocked yet. That said, there are two good ways to start contributing on geo now: 1. **Cross-client fixtures.** The umbrella issue calls out Java / PyIceberg fixtures to pin the wire format at each step, and I don’t think anyone owns that yet. Building WKB sample tables, Java / PyIceberg round-trip test data, and GeoArrow conformance fixtures would be genuinely useful work. It doesn’t depend on the Go code landing first, and once it exists, every sub-issue can use it. Less glamorous than feature code, but really valuable for a multi-client spec like this. 2. **Pair with @happydave1 on #991.** WKB encoding + GeoArrow conversion is a hard piece of work, and it might make more sense to tackle it together than to split it cleanly on paper. Best place to sync is probably the Apache Iceberg Slack rather than issue comments — feel free to start a thread there and loop @happydave1 in. Also, reviewing PR #984 as it comes together would be a low-cost way to ramp on the codebase while you decide. -- 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]
