Re: Treat predicate whose time series doesn't exist as false

[Jialin Qiao]

+1, return empty is better than throwing an exception.
—
Jialin Qiao
Apache IoTDB PMC

冯 庆新  于2022年10月8日周六 21:25写道：
>
> Hi,
> I support you in this improvement.
>
> 获取 Outlook for iOS
> 
> 发件人: Zhou Yifu 
> 发送时间: Friday, October 7, 2022 3:48:43 PM
> 收件人: dev@iotdb.apache.org 
> 主题: 回复: Treat predicate whose time series doesn't exist as false
>
> Yes, I agree with you. Query should not return an exception except for a 
> syntax error.
>
> Thanks,
> Yifu Zhou
>
> 从 Windows 版邮件发送
>
> 发件人: Yuan Tian
> 发送时间: 2022年10月7日 14:56
> 收件人: dev
> 主题: Treat predicate whose time series doesn't exist as false
>
> Hi,
>
> Currently in IoTDB, if users write a non-exist time series in
> select clause, we will simply ignore that and don't display it in
> result columns instead of throwing exceptions. However, if users write
> a non-exist time series in where clause, we will throw an exception
> like: `the path 'root.test.g_0.d1.s2' in WHERE clause does not exist`.
> It's inconsistent with the select clause, so we prepare to just treat
> predicate whose time series doesn't exist as false instead of throwing
> exception, same as InfluxDB.
> How do you guys think?
> The JIRA is https://issues.apache.org/jira/browse/IOTDB-4576
>
>
> Best,
> --
> Yuan Tian
>

Re: Treat predicate whose time series doesn't exist as false

[冯 庆新]

Hi,
I support you in this improvement.

获取 Outlook for iOS

发件人: Zhou Yifu 
发送时间: Friday, October 7, 2022 3:48:43 PM
收件人: dev@iotdb.apache.org 
主题: 回复: Treat predicate whose time series doesn't exist as false

Yes, I agree with you. Query should not return an exception except for a syntax 
error.

Thanks,
Yifu Zhou

从 Windows 版邮件发送

发件人: Yuan Tian
发送时间: 2022年10月7日 14:56
收件人: dev
主题: Treat predicate whose time series doesn't exist as false

Hi,

Currently in IoTDB, if users write a non-exist time series in
select clause, we will simply ignore that and don't display it in
result columns instead of throwing exceptions. However, if users write
a non-exist time series in where clause, we will throw an exception
like: `the path 'root.test.g_0.d1.s2' in WHERE clause does not exist`.
It's inconsistent with the select clause, so we prepare to just treat
predicate whose time series doesn't exist as false instead of throwing
exception, same as InfluxDB.
How do you guys think?
The JIRA is https://issues.apache.org/jira/browse/IOTDB-4576


Best,
--
Yuan Tian

Re: Change Of Load Syntax

[Xiangdong Huang]

Hi Sicheng,

It is impossible to read this email as there are too many  ""


---
Xiangdong Huang
School of Software, Tsinghua University


yusicheng <928623...@qq.com.invalid> 于2022年10月5日周三 10:07写道：
>
> Hi everybody! I noticed that whether metadata is created automatically 
> when writing is controlled by ENABLE_AUTO_CREATE_SCHEMA in 
> iotdb-datanode.properties, but the load statement for loading external tsfile 
> has its own control parameter AUTOREGISTER, and the two functions overlap, so 
> I want to remove the AUTOREGISTER parameter from the load statement and let 
> ENABLE_AUTO_CREATE_SCHEMA control whether metadata is created automatically 
> when loading, consistent with writing.
>  In addition, I noticed that some users don't want to delete the source 
> tsfiles after loading them, so I want to add the parameter ONSUCCESS to the 
> load statement, which means how to handle the successfully loaded tsfiles. 
> There are two ways to handle it, DELETE, which deletes the source tsfiles 
> after successful loading, and NONE, which keeps the source tsfile after 
> successful loading.
>  In summary, I would like to design the new load statement as follows:
>  load ' [sglevel=int][verify=true/false][onSuccess=delete/none]
>  for reference, the origin load statement is calmed as follows:
>  load ' [autoregister=true/false][,verify=true/false][,sglevel=int]
> 
> best,
>
>
>
>
>
>Sicheng Yu