Jefffrey opened a new issue, #5247:
URL: https://github.com/apache/arrow-datafusion/issues/5247
**Describe the bug**
A clear and concise description of what the bug is.
When using SQL, can use SORT BY keyword though it has no effect
**To Reproduce**
Steps to reproduce the behavior:
```sql
❯ select * from test1 sort by a;
+---+---+---+
| a | b | c |
+---+---+---+
| 1 | 2 | 3 |
| 4 | 5 | 6 |
+---+---+---+
2 rows in set. Query took 0.007 seconds.
❯ explain select * from test1 sort by a;
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| plan_type | plan
|
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| logical_plan | Projection: test1.a, test1.b, test1.c
|
| | TableScan: test1 projection=[a, b, c]
|
| physical_plan | ProjectionExec: expr=[a@0 as a, b@1 as b, c@2 as c]
|
| | RepartitionExec: partitioning=RoundRobinBatch(12),
input_partitions=1
|
| | CsvExec: files={1 group:
[[home/jeffrey/Code/arrow-datafusion/datafusion-cli/test.csv]]},
has_header=true, limit=None, projection=[a, b, c] |
| |
|
+---------------+-------------------------------------------------------------------------------------------------------------------------------------------------+
2 rows in set. Query took 0.004 seconds.
```
**Expected behavior**
A clear and concise description of what you expected to happen.
Should raise error as invalid SQL, even though it does not affect the
generated plan
**Additional context**
Add any other context about the problem here.
--
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]
