C-Loftus opened a new issue, #1090:
URL: https://github.com/apache/iceberg-go/issues/1090

   ### Feature Request / Improvement
   
   Parent: https://github.com/apache/iceberg-go/issues/989
   
   As mentioned in 
https://github.com/apache/iceberg-go/issues/989#issuecomment-4479477750 There 
is a need for `Building WKB sample tables, Java / PyIceberg round-trip test 
data, and GeoArrow conformance fixtures`.  According to my interpretation this 
would essentially mean generating small test cases for a variety of standard 
geoarrow data and edge cases generated by multiple different clients to ensure 
the go implementation works across the iceberg ecosystem.
   
   I am happy to work on contributing this as I've done GeoArrow work in the 
past so that seems like a good intro to the codebase. I have created a new 
issue here since I did not see an existing one to track this and didn't want to 
clutter the main geo issue.
   
   I have a few questions before I begin if you don't mind @laskoviymishka :
   
   1. In which directory would these fixtures be placed in the iceberg-go 
codebase? 
       - I am assuming these live in this repo but if they also go anywhere 
else please let me know
   3. Do you have preferences regarding the format / metadata of test data    
      - Since I am relatively new to iceberg, wasn't clear if putting a small 
iceberg table directly in the git repo would be too heavy. Is there a better 
way to do this?
      - Is there a specific package manager you prefer for Python/Java, etc. 
for the purposes of pinning the script which generates the test data (assuming 
you want that?)


-- 
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]

Reply via email to