Hi
We want to introduce a new wildcard **, to improve the DDL and DML of IoTDB-SQL.
As we all know, a time series is represented by a full path from the
root node to the measurement node in the metadata tree. The existing
wildcard *, when used in the path, represents one level of the
metadata tre
We want to introduce a new wildcard **, to improve the DDL and DML of IoTDB-SQL.
As we all know, a time series is represented by a full path from the
root node to the measurement node in the metadata tree. The existing
wildcard *, when used in the path, represents one level of the
metadata tree an
Hi
Precise path match means precise full path match. Users need to
construct the full path pattern, using wildcard or not, when writing
sql.
In your example, using "count timeseries root.sg.*.s.*" to count in
"root.sg.d.s.t " is what we want users to do.
" Select * " is a simple representation of
Hi,
I am lost when reading the content what is *" "* *precise etc.?
> In DDL, we want to replace the prefix path match with the *precise path
> match*
What is *precise path match*?
> For example the old versions query "count timeseries root.sg " will be
> implemented as "count timeserie
Hi
We want to introduce a new *wildcard ***, to improve the DDL and DML of
IoTDB-SQL.
Wildcard ** will represent one or more levels in the path and the existing
wildcard * will only represent one level in the path even if it's at the
tail of the path.
In DDL, we want to replace the prefix path ma
