Hi,

I'm prepared to add a new feature in IoTDB as follows:

Currently, when doing a query like *`select s1 from root.sg.d1`*, the
result shows like:

| Time | root.sg.d1.s1|
|    ...   |          ...        |

The column name *includes all prefix paths which are complex* and seem
inflexible and inconvenient in some situations.

Therefore, I think we can add a new feature by adding the alias of time
series, which is like a relational database. For example, *`select s1 as
d1_temperature form root.sg.d1`*

The result will be like:

| Time | d1_temperature |
|   ...    |            ....           |


However, the new feature may be *limited* in IoTDB as a time series
database.
Because it's not matching one time series for one suffix path exactly in
SELECT Clause. For example, `select s1 as temperature from root.sg`. If two
devices d1 and d2 exist in root.sg, then they can't both be temperature. We
have to throw an exception here.

So we have to request that *every alias input by users is matching one time
series exactly.*


Any suggestions or questions are welcome! Thank you!



-- 
Best,
Xiangwei Wei

Reply via email to