MarcosZyk opened a new pull request, #12327:
URL: https://github.com/apache/iotdb/pull/12327
## Description
### Supported Features
1. create table
2. describe table
3. show tables
### Result
```
IoTDB> create database db_1;
Msg: The statement is executed successfully.
IoTDB> create table db_1.t_1(device TEXT ID, attr TEXT ATTRIBUTE, time INT64
TIME, s INT32 MEASUREMENT);
Msg: The statement is executed successfully.
IoTDB> use db_1
Msg: The statement is executed successfully.
IoTDB> create table t_2(region TEXT ID, code TEXT ID, type TEXT ATTRIBUTE,
price TEXT ATTRIBUTE, time INT64 TIME, s_1 INT32 MEASUREMENT, s_2 FLOAT
MEASUREMENT);
Msg: The statement is executed successfully.
IoTDB> show tables
+---------+----+
|TableName| TTL|
+---------+----+
| t_2|null|
| t_1|null|
+---------+----+
Total line number = 2
It costs 0.043s
IoTDB> describe t_2
+----------+--------+-----------+
|ColumnName|DataType| Category|
+----------+--------+-----------+
| region| TEXT| ID|
| code| TEXT| ID|
| type| TEXT| ATTRIBUTE|
| price| TEXT| ATTRIBUTE|
| time| INT64| TIME|
| s_1| INT32|MEASUREMENT|
| s_2| FLOAT|MEASUREMENT|
+----------+--------+-----------+
Total line number = 7
It costs 0.008s
IoTDB> describe db_1.t_1
+----------+--------+-----------+
|ColumnName|DataType| Category|
+----------+--------+-----------+
| device| TEXT| ID|
| attr| TEXT| ATTRIBUTE|
| time| INT64| TIME|
| s| INT32|MEASUREMENT|
+----------+--------+-----------+
Total line number = 4
It costs 0.005s
```
### Content3 ...
<!--
In each section, please describe design decisions made, including:
- Choice of algorithms
- Behavioral aspects. What configuration values are acceptable? How are
corner cases and error
conditions handled, such as when there are insufficient resources?
- Class organization and design (how the logic is split between classes,
inheritance, composition,
design patterns)
- Method organization and design (how the logic is split between methods,
parameters and return types)
- Naming (class, method, API, configuration, HTTP endpoint, names of
emitted metrics)
-->
<!-- It's good to describe an alternative design (or mention an alternative
name) for every design
(or naming) decision point and compare the alternatives with the designs
that you've implemented
(or the names you've chosen) to highlight the advantages of the chosen
designs and names. -->
<!-- If there was a discussion of the design of the feature implemented in
this PR elsewhere
(e. g. a "Proposal" issue, any other issue, or a thread in the development
mailing list),
link to that discussion from this PR description and explain what have
changed in your final design
compared to your original proposal or the consensus version in the end of
the discussion.
If something hasn't changed since the original discussion, you can omit a
detailed discussion of
those aspects of the design here, perhaps apart from brief mentioning for
the sake of readability
of this PR description. -->
<!-- Some of the aspects mentioned above may be omitted for simple and small
changes. -->
<hr>
This PR has:
- [ ] been self-reviewed.
- [ ] concurrent read
- [ ] concurrent write
- [ ] concurrent read and write
- [ ] added documentation for new or modified features or behaviors.
- [ ] added Javadocs for most classes and all non-trivial methods.
- [ ] added or updated version, __license__, or notice information
- [ ] added comments explaining the "why" and the intent of the code
wherever would not be obvious
for an unfamiliar reader.
- [ ] added unit tests or modified existing tests to cover new code paths,
ensuring the threshold
for code coverage.
- [ ] added integration tests.
- [ ] been tested in a test IoTDB cluster.
<!-- Check the items by putting "x" in the brackets for the done things. Not
all of these items
apply to every PR. Remove the items which are not done or not relevant to
the PR. None of the items
from the checklist above are strictly necessary, but it would be very
helpful if you at least
self-review the PR. -->
<hr>
##### Key changed/added classes (or packages if there are too many classes)
in this PR
--
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: reviews-unsubscr...@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
