[ARROW-9788] Handle naming inconsistencies between SQL, DataFrame API and struct names

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: Rust - DataFusion
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/25835
• Assignee: Andy Grove
• Reporter: Jorge Leitão
• Created: 18/Aug/20 18:47
• Updated: 11/Jan/23 08:09
• Resolved: 19/Aug/20 13:28

Description

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.

Issue Links

• links to: GitHub Pull Request #7998