I just upgrade the Apache IoTDB version from 1.1.0 to 1.3.1. I try to execute SELECT * FROM root.nm_p1.line1.**.**.result where Batch = 'E4P2BC1932' statement, but an error reported: [701][ALIGN BY DEVICE: the datatypes of the same measurement column should be the same across devices]. The previous version can generate this command, but the newer version can’t. I wonder are there any updates that causes this problem?

I checked the version 1.2 user guide tutorial, and it said that currently, IoTDB to IoTDB data synchronization implementation does not support DDL synchronization, that is, operations such as ttl, trigger, alias, template, view, create/delete sequence, create/delete database, etc. However, my scenario required to synchronize time series that automatically generated based on the data collection scene. If I still want to synchronize these time series, any solutions for this case?

I have a question about the combination use of TTL and data synchronization between multiple Apache IoTDB database. The two databases require different data storage durations. One IoTDB database is for handling expired data using TTL. The other IoTDB database stores all historical data and synchronize the data source from the previous IoTDB database. I wonder whether expired data set by TTL in the previous IoTDB will be synchronized and delete again in the later IoTDB. If it still will be synchronize and delete, are there any other better way?

I am trying to connect Apache IoTDB server using REST API, and it kept reported failed to connect to iotdb service. Get "http://172.16.10.101:18080/grafana/v1/login". dial tcp 172.16.10.101:18080: connectex: No connection could be made because the target machine actively refused it.
I have no firewall set in the system, and the REST API service configuration has already been set to true. Anyone know other reasons that may cause this?

I would like to ask why did I fail to create the view using the sql statement example on the official website? The error reported View is not supported. My statements executed in step order are:

I use cluster version 1.2.0 of Apache IoTDB now, and has 3 ConfigNodes and 3 DataNodes. The cluster reported ERROR o.a.i.d.q.e.e.RegionReadExecutor:91 - Execute FragmentInstance in ConsensusGroup SchemaRegion[0] failed. org.apache.iotdb.consensus.exception.RatisUnderRecoveryException: Raft Server is redoing Raft Log and cannot serve read requests now. Please try read later: org.apache.ratis.protocol.exceptions.ReadIndexException: Failed to getReadIndex 289575 since the term is not yet committed. The DataNode status reflected unknown. I tried to restart the cluster, and the status turned normal, but another error appeared org.apache.iotdb.consensus.exception.RatisRequestFailedException: Ratis request failed org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: DEADLINE_EXCEEDED: deadline exceeded after -5.819248744s. Anyone know why these two errors appeared?

The query result feedback when using order by limit 1 is not the largest value for version 1.2.2 of Apache IoTDB. Anyone know what the reason? My whole query statement is select d_206871005.flow_d from root.default.flow_steam_hot_cold_day.** where time>= 1970-01-01 08:00:00 and time < 2024-04-17 23:59:59 order by d_206871005.flow_d desc limit 1, and the value returned is the second largest value, validated by using desc statment only. How to solve the problem?