Hi Yuan, I ran the iotdb-extras JDBC consumers against one server built from 7aa8e63a7c6, once with the 2.0.11 release driver and once with the driver from that commit.
Tested: examples/mybatis-generator (IoTDBGeneratorIT and the generator run), examples/mybatisplus-generator (IoTDBMapperIT and CodeGenerator), and, in the tree dialect, connectors/zeppelin-interpreter and connectors/grafana-connector. mybatis-generator and mybatis-support do not depend on iotdb-jdbc. None of the listed behavior changes breaks these modules. All ITs pass with both drivers, and the generated Java and mapper XML are the same, with one change for the better: for tables with a COMMENT, MyBatis Generator now writes the table's own comment. With 2.0.11, getTables ignored the table name and the generator used the first table's one. One thing for later: extras manages libthrift 0.23.0 and TsFile 2.4.0 to match 2.0.11. With those, the client from 7aa8e63a7c6 fails on its first connection with NoSuchMethodError, because of the Thrift 0.25.0 bump (#18793). So when extras moves to a release that contains it, those two versions have to move too; 0.25.0 and 2.5.0 work with both drivers. Zihan
