Hi, Thanks for proposing this out! Extending the tag to support data query is what we want to for a long time :)
There are some aspects to consider: We add tags on timeseries, influxdb or other TSDBs add tags on device. This is a difference but may not a problem in insertion, since on timeseries could cover on device. This impacts the query... For influxdb, the table format is 【time, tag1, tag2, tag3, field1, field2, field3】 so they could use select tag1, tag2, field1, field2 from measurement where tag=xx For us, which view could we give users to write the sql? Same with influxdb or use this【time, tag1, tag2, tag3, fieldname, value】? This is a big topic. Maybe we need to give some result format example to see. Thanks, ————————————————— Jialin Qiao Apache IoTDB PMC Eric Pai <ericpa...@hotmail.com> 于2022年6月24日周五 16:48写道: > Great! Let's wake up those tags! > > 在 2022/6/24 16:42,“Wz”<zhongwang...@qq.com.INVALID> 写入: > > Hi guys, > > > > > To handle multidimensional queries, we plan to implement data > filtering and aggregation on top of the MPP framework. Here's a description > of the scenario: > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache-iotdb.feishu.cn%2Fdocx%2FdoxcnOfxK6kYK159X86gxBVFwts&data=05%7C01%7C%7Cb785c20dd27a423032e408da55bd62e4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637916569203467291%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZsdsIVgCMgthC0g6vGDv6FMoIsU3oUUWN2xuLf5FqWY%3D&reserved=0 > > > > > Any suggestions are welcome. Thanks, Zhong Wang > >