alamb opened a new pull request, #4903:
URL: https://github.com/apache/arrow-datafusion/pull/4903

   # Which issue does this PR close?
   
   re https://github.com/apache/arrow-datafusion/issues/3058 and 
https://github.com/apache/arrow-datafusion/issues/1814
   
   # Rationale for this change
   
   I attended a conference last week 
[CIDR](https://www.cidrdb.org/cidr2023/index.html) and it was clear to me that 
DataFusion is more widely applicable than it is currently used, and part of 
that is lack of awareness in the broader community. Thus I wanted to try and 
communicate what DataFusion was / was good for more clearly.
   
   Also as we have gathered more users we can now point to some more concrete 
examples
   
   I also hope/plan to try and writeup a "datafusion architecture guide" soon 
as an additional way to encourage / grow our user base by making it more 
accessable for new people to see what we have (which is a lot!). Related to 
https://github.com/apache/arrow-datafusion/issues/980 from @xudong963 
   
   
   # What changes are included in this PR?
   1. Update the main readme with: more specific information about what 
datafusion is, and what it has been used for
   2. Added some compare/contrast with pola.rs, DuckDB and Velox.
   
   See the rendered page here: 
https://github.com/alamb/arrow-datafusion/tree/alamb/improve_user_docs#datafusion
   
   # Discussion
   
   Dicsussion:
   How much of this content should go in the user guide 
https://arrow.apache.org/datafusion?
   
   I like the idea of all the non-release specific content being in the user 
guide . However, the website isn't updated all that often (as it takes a manual 
process as I recall)
   
   The README is what shows up on the main crates.io page: 
https://crates.io/crates/datafusion as well as the landing page of github.
   
   
   


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

Reply via email to