Details
-
Bug
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
In general metaQuery, if the schema is empty, we may get the following results 
:
IoTDB> show timeseries +----------+-----+--------+--------+--------+-----------+----+----------+--------+------------------+--------+ |Timeseries|Alias|Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|ViewType| +----------+-----+--------+--------+--------+-----------+----+----------+--------+------------------+--------+ +----------+-----+--------+--------+--------+-----------+----+----------+--------+------------------+--------+ IoTDB> show devices +------+---------+--------+---+ |Device|IsAligned|Template|TTL| +------+---------+--------+---+ +------+---------+--------+---+ IoTDB> count timeseries +-----------------+ |count(timeseries)| +-----------------+ | 0| +-----------------+ IoTDB> count devices +--------------+ |count(devices)| +--------------+ | 0| +--------------+
But in active metadata query, we get the following confusing results 
IoTDB> show timeseries where time < 6 +----+ |Time| +----+ +----+ IoTDB> show devices where time < 6 +----+ |Time| +----+ +----+ IoTDB> count timeseries where time < 6 Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count timeseries where time < 6". executeStatement failed. null IoTDB> count devices where time < 6 Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count devices where time < 6". executeStatement failed. null
We should fix and unify these. 
Attachments
Issue Links
- links to