daniel-awake commented on issue #2203: URL: https://github.com/apache/parquet-java/issues/2203#issuecomment-3353979176
In our project, we are rethinking our own storage of IP addresses in Parquet, looking for a representation that might be more upstreamable. Our current implementation maximizes compatibility with Postgres, and simply stores a postgres struct (basically https://doxygen.postgresql.org/structinet__struct.html ) in a Parquet BYTE_ARRAY. We're looking at a representation that ideally preserves those characteristics: * unified type for IPv4 and IPv6: application code is much simpler when you don't need different types for these. * subnet mask length: really handy for those address-in-subnet checks. * address family flag: while one could pack IPv4 addresses as zero-padded IPv6 addresses, it would be certainly nice to avoid the shim code to adapt the values to/from application code. We *could* just stick with what we have, but feel like we *should* be able to do better than just dumping in a Postgres `struct`. Anyway, we wanted to see if anyone else had strong opinions, and this Github issue seems to be where it's at. -- 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]
