[
https://issues.apache.org/jira/browse/ARROW-9788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Grove resolved ARROW-9788.
-------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
Issue resolved by pull request 7998
[https://github.com/apache/arrow/pull/7998]
> Handle naming inconsistencies between SQL, DataFrame API and struct names
> -------------------------------------------------------------------------
>
> Key: ARROW-9788
> URL: https://issues.apache.org/jira/browse/ARROW-9788
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Rust - DataFusion
> Reporter: Jorge
> Assignee: Andy Grove
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently, we have naming inconsistencies between the different APIs that
> make it a bit confusing. The typical example atm is
> `df.where().to_plan?.explain()` shows a "Selection" in the plan when
> "Selection" in SQL and many other query languages is a projection, not a
> filter.
> Other examples:
> ```
> name: Selection
> SQL: WHERE
> DF: filter
> ```
> ```
> name: Aggregation
> SQL: GROUP BY
> DF: aggregate
> ```
> ```
> name: Projection
> SQL: SELECT
> DF: select,select_columns
> ```
> I suggest that we align them with a common notation, preferably aligned with
> other more common query languages.
> I am assigning this to you [~andygrove] as you are probably the only person
> that can take a decision on this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
