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, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Marko Friedemann <[email protected]> 于2019年3月7日周四 上午4:06写道： > Hey, > > I want to report an issue with tsfile, specifically its query capabilities. > > The two-argument constructor for org.apache.iotdb.tsfile.read.common.Path > that is now available in the apache incubator project still does not allow > proper construction of a path where the measurement name contains dots. > > Specifically, the issue is that the two-argument constructor concatenates > the two arguments with a path-separator character (the dot) and then splits > the result again, using the seperator (the dot), instead of just using the > supplied arguments as they are. > This results in the path components being incorrect (device basically runs > to lastIndexOf('.') for the full path) and the query failing. > > The rest of tsfile's write/read/query functionality doesn't seem to mind > measurement names that contain dots (think RDF and IRIs) and the intended > query can be run with a minor fix by sub-classing the Path class. > (Unfortunately, Path::init() is also private, so the work-around is not > readily possible.) > > Regards, > Marko Friedemann >
