You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Andrew Lamb (Jira)" <ji...@apache.org> on 2021/01/11 11:24:00 UTC
[jira] [Assigned] (ARROW-11165) [Rust] [DataFusion] Document the
desired SQL dialect for DataFusion
[ https://issues.apache.org/jira/browse/ARROW-11165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Lamb reassigned ARROW-11165:
-----------------------------------
Assignee: Andrew Lamb
> [Rust] [DataFusion] Document the desired SQL dialect for DataFusion
> -------------------------------------------------------------------
>
> Key: ARROW-11165
> URL: https://issues.apache.org/jira/browse/ARROW-11165
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Andrew Lamb
> Assignee: Andrew Lamb
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As discussed https://github.com/apache/arrow/pull/9108#issuecomment-755791235
> We would like to pick a single SQL dialect in DataFusion to avoid what happened with Spark SQL where functions, https://spark.apache.org/docs/latest/api/sql/index.html, were added seemingly ad-hoc making their usage very difficult and no clear feature matrix available.
> Using an existing dialect will also allow us to re-use the documentation (and other tools) from that dialect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)