[IOTDB-240] query problem for iotdb filter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: EJTTianyu
• Created: 25/Sep/19 13:55
• Updated: 03/Feb/20 03:06
• Resolved: 02/Feb/20 11:12

Description

When querying a timeseries that does not exist, iotdb shows different behavior for SQL with or without filter.
After starting a new iotdb instance, The following steps in iotdb-client below could reproduce the problem.
Step 1: set storage group to root.demo
Step 2: CREATE TIMESERIES root.demo.ZT31 WITH DATATYPE=INT64, ENCODING=RLE
Step 3:insert into root.demo(timestamp,ZT31) values(1,1)
when using sql:
1.select ZT1 from root.demo
iotdb-client responds with message "Msg: Execute statement error: do not select any existing series"
2.select ZT1,ZT31 from root.demo
iotdb-client responds with
-----------------------------------------------+

Time	root.demo.ZT31

-----------------------------------------------+

1970-01-01T08:00:00.001+08:00

1

-----------------------------------------------+
3.select ZT1,ZT31 from root.demo where ZT1>0
iotdb-client responds with message "Msg: Execute statement error: Index: 0, Size: 0"

Timeseries ZT1 does not exist in condition 2 and condition 3. However, without using ZT1 as filter to query multiple sensors(at least one exists), iotdb could respond with datapoints. When using ZT1 as filter, the returned msg confused users.

In my opinion, both condition 2 and 3 should respond with message "Msg: Execute statement error: do not select any existing series". Or condition 2 responds with datapoints, condition 3 responds with "Msg: Execute statement error: do not select any existing series".

Issue Links

• is broken by: IOTDB-447 Support query on time series which are not created
• links to: GitHub Pull Request #423
• links to: GitHub Pull Request #443