Hi Xiangdong,
thanks for the clarification, indeed, then I was wrong.
In the light of that, I'm unsure whether I like the idea to allow dots for the
names or if these should keep forbidden.
This makes it (visibily) clear what part is the measurement and what is the
"path".
Julian
Am
Hi,
@Julian I think we support what you want now..
for example, you can create 3 timeseries by:
```
set storage group to root.sg1;
create timeseries root.sg1.location1.deviceType1.deviceID.m1 with
datatype=FLOAT, encoding=RLE;
create timeseries root.sg1.location1.deviceType2.deviceID.m1 with
Hi Xiangdong,
what do you think of a subtile generalization of the current "device" approach.
If we would allow dots in the name, we could the possibility to create "trees"
like its done e.g. for akka actors [1] or MQTT Topics [2].
What I mean is that one could add more information in the "path"
Hi,
It seems this will cause a big modification... (Change the Path class is
easy, but it will lead to a confusion for SQL layer..) A solution is needed
to let SQL recognize that.
I have created a issue on JIRA:
https://issues.apache.org/jira/browse/IOTDB-38
Best,