aihuaxu commented on issue #147: URL: https://github.com/apache/parquet-site/issues/147#issuecomment-3739570110
> > > I believe [@aihuaxu](https://github.com/aihuaxu) said on the mailing list https://lists.apache.org/thread/278m3oyvg3okl819xo55m4ttogbzbjlc that he was working on one > > > > Agree. We started to write a little bit for variant and I can take variant blog. > > > > > > [@alamb](https://github.com/alamb) We have published one here https://www.snowflake.com/en/engineering-blog/apache-iceberg-v3-variant-type/. I guess we cannot directly reuse it and I can work on top of it for Parquet blog? > > Thanks [@aihuaxu](https://github.com/aihuaxu) -- that blog is a nice read. I think much of it could be re-used for a Parquet blog (with you and Snowflake's permission of course) > > However I think the fact the blog also talks about Iceberg makes it a bit unclear where the boundary between the two items are and I think the blog (understandably) seems to have an intended audience of "end users" of Variant > > For a parquet blog I was envisioning something which: > > 1. Is focused on parquet > 2. Target audience is people implementing Variant (and those who are interested in such a level of detail) > 3. Has some examples of encodings (maybe we can use the example shredding from the snowflake blog) > 4. Also emphasizes that this is a major addition to Parquet that has seen rapid uptake across its ecosystem (Java, C++, Rust, Go, DuckDB, etc), as an example of how the format continues to evolve. > > (to be clear, I am not saying you have to write such a blog, I am just articulating what I think would be most valuable for Parquet) That's right. The current one is more intended for end user. Thanks for the feedback and that makes sense to me. Let me draft one. -- 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]
