LiuYuHui opened a new pull request, #2642:
URL: https://github.com/apache/arrow-datafusion/pull/2642
# Which issue does this PR close?
Closes #2606.
# Rationale for this change
# What changes are included in this PR?
When the user executes the `DESCRIBE <table>`, the output will be the
following.
```sql
❯ create table foo as select * from (values (1), (3), (2), (10), (8));
+---------+
| column1 |
+---------+
| 1 |
| 3 |
| 2 |
| 10 |
| 8 |
+---------+
5 rows in set. Query took 0.013 seconds.
❯ describe foo;
+-------------+-----------+-------------+
| column_name | data_type | is_nullable |
+-------------+-----------+-------------+
| column1 | Int64 | YES |
+-------------+-----------+-------------+
1 row in set. Query took 0.016 seconds.
```
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
# Does this PR break compatibility with Ballista?
<!--
The CI checks will attempt to build
[arrow-ballista](https://github.com/apache/arrow-ballista) against this PR. If
this check fails then it indicates that this PR makes a breaking change to
the DataFusion API.
If possible, try to make the change in a way that is not a breaking API
change. For example, if code has moved
around, try adding `pub use` from the original location to preserve the
current API.
If it is not possible to avoid a breaking change (such as when adding enum
variants) then follow this process:
- Make a corresponding PR against `arrow-ballista` with the changes required
there
- Update `dev/build-arrow-ballista.sh` to clone the appropriate
`arrow-ballista` repo & branch
- Merge this PR when CI passes
- Merge the Ballista PR
- Create a new PR here to reset `dev/build-arrow-ballista.sh` to point to
`arrow-ballista` master again
_If you would like to help improve this process, please see
https://github.com/apache/arrow-datafusion/issues/2583_
-->
--
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]
