JanKaul commented on PR #12: URL: https://github.com/apache/iceberg-rust/pull/12#issuecomment-1651064346
Ah okay, I think I had a different idea for the lookup tables. Generally you could think of different lookup tables, these could be: 1. Lookup table to obtain the full field name (i.e. "position.lat") from a field id 2. Lookup table to obtain the index in the storage vector from a field id (not nested) 3. Lookup table to obtain the index in the storage vector from a field name (not nested) I've currently implemented 2 & 3 with the goal to speed up the access of a structfield. I didn't think of nested structs and that you need to obtain the full field name. That opens the question how best to implement this. We could use two lookup tables (field id -> full field name, field name -> storage index) which means that an access by field id has to always perform a field name lookup first. -- 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]
