alamb opened a new issue, #146:
URL: https://github.com/apache/parquet-site/issues/146

   I am filing a. ticket to track the idea of writing Parquet specific blog 
posts on features and other general interest topics to the broader Parquet 
community. 
   
   In my somewhat biased opinion, the main parquet website 
https://parquet.apache.org/docs  now has good technical reference documentation 
that will stay up to date with the format (thanks to @emkornfield 's work to 
synch it with parquet format in 
https://github.com/apache/parquet-site/issues/140)
   
   However, I think it would be useful to also have content, published on 
https://parquet.apache.org/blog/
   1. aimed at a broader audience to explain Parquet concepts at a slightly 
higher
   2. The intended audience is for those using (or contemplating using) Parquet 
rather than implementing parquet
   
    @julienledem also suggested this on the mailing list: 
https://lists.apache.org/thread/m6p5shlt1hfk1b3h5y1pbqg8tpkwpcgz
   
   > I was thinking that we should talk more about the new features in Parquet.
   > Specifically, write blog posts about Variant or Geo types.
   > How they came to be, what they enable, how they are integrated in the
   > ecosystem.
   > The Parquet blog is only the release announcements for now (
   > https://parquet.apache.org/blog/) and we can make it an opportunity to
   > spotlight some of the recent additions to the project.
   
   Some sources of inspiration:
   - https://arrow.apache.org/blog/
   - https://openlineage.io/blog
   - https://datafusion.apache.org/blog/
   
   
   I'll link some related tickets here shortly


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