HTHou edited a comment on issue #2493: URL: https://github.com/apache/iotdb/issues/2493#issuecomment-760070194
I think we can support sql like this. ``` IoTDB> show timeseries +-------------+-----+-------------+--------+--------+-----------+----+----------+ | timeseries|alias|storage group|dataType|encoding|compression|tags|attributes| +-------------+-----+-------------+--------+--------+-----------+----+----------+ |root.sg.d1.s3| null| root.sg| INT32| RLE| SNAPPY|null| null| |root.sg.d1.s1| null| root.sg| INT32| RLE| SNAPPY|null| null| |root.sg.d1.s2| null| root.sg| INT32| RLE| SNAPPY|null| null| +-------------+-----+-------------+--------+--------+-----------+----+----------+ Total line number = 3 It costs 0.026s IoTDB> show child paths root.sg.d1 +-------------+ | child paths| +-------------+ |root.sg.d1.s1| |root.sg.d1.s2| |root.sg.d1.s3| +-------------+ Total line number = 3 It costs 0.015s IoTDB> show child nodes root.sg.d1 +-----------+ |child nodes| +-----------+ | s1| | s2| | s3| +-----------+ Total line number = 3 It costs 0.142s ``` To implement it, just consider a modification of the method `findChildNodePathInNextLevel` in https://github.com/apache/iotdb/blob/master/server/src/main/java/org/apache/iotdb/db/metadata/MTree.java ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
