[Bug] insertTablet http api lost data event return SUCCESS_STATUS

[zhongwencool]

Search before asking

• I searched in the issues and found nothing similar.

Version

Using this syntax, data can be inserted in version 1.1.x, but it no longer works after upgrading to 1.3.0.

curl --location --request POST 'http://iotdb-1-3-0.docker-compose-file.orb.local:18080/rest/v2/insertTablet' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic cm9vdDpyb290' \
--data-raw '{"is_aligned":false,"device":"root.mqtt.topic.abc454","data_types":["TEXT","INT32","FLOAT"],"measurements":["foo","temp","weight"],"timestamps":[1713495895809,1713499707255,1713495893809,1713495892809,1713495891809,1713495890809,1713495889809,1713495888809,1713495887809,1713495893809,1713495892809,1713495891809,1713495890809,1713495889809,1713495888809],"values":[["bar",null,null,null,null,null,null,null,null,null,null,null,null,null,null],[null,41,32,33,34,39,38,37,36,null,null,null,null,null,null],[null,null,null,null,null,null,null,null,null,87.0,87.3,87.3,87.0,87.3,87.3]]}'
{"code":200,"message":"SUCCESS_STATUS"}

Weights are null.

IoTDB> select temp,weight,foo from root.mqtt.topic.abc454;
select temp,weight,foo from root.mqtt.topic.abc454;
+------------------------+---------------------------+-----------------------------+--------------------------+
|                    Time|root.mqtt.topic.abc454.temp|root.mqtt.topic.abc454.weight|root.mqtt.topic.abc454.foo|
+------------------------+---------------------------+-----------------------------+--------------------------+
|2024-04-19T03:04:47.809Z|                         36|                         null|                      null|
|2024-04-19T03:04:48.809Z|                         37|                         null|                      null|
|2024-04-19T03:04:49.809Z|                         38|                         null|                      null|
|2024-04-19T03:04:50.809Z|                         39|                         null|                      null|
|2024-04-19T03:04:51.809Z|                         34|                         null|                      null|
|2024-04-19T03:04:52.809Z|                         33|                         null|                      null|
|2024-04-19T03:04:53.809Z|                         32|                         null|                      null|
|2024-04-19T03:04:55.809Z|                       null|                         null|                       bar|
|2024-04-19T04:08:27.255Z|                         41|                         null|                      null|
+------------------------+---------------------------+-----------------------------+--------------------------+

Describe the bug and provide the minimal reproduce step

docker-compose yaml file

services:
  iotdb_1_3_0:
    container_name: iotdb130
    hostname: iotdb130
    image: apache/iotdb:1.3.0-standalone
    restart: always
    environment:
      - enable_rest_service=true
      - cn_internal_address=iotdb130
      - cn_internal_port=10710
      - cn_consensus_port=10720
      - cn_seed_config_node=iotdb130:10710
      - dn_rpc_address=iotdb130
      - dn_internal_address=iotdb130
      - dn_rpc_port=6667
      - dn_mpp_data_exchange_port=10740
      - dn_schema_region_consensus_port=10750
      - dn_data_region_consensus_port=10760
      - dn_seed_config_node=iotdb130:10710
    # volumes:
    #     - ./data:/iotdb/data
    #     - ./logs:/iotdb/logs
    expose:
      - "18080"
    # IoTDB's REST interface, uncomment for local testing
    # ports:
         - "18080:18080"

What did you expect to see?

I want to weight is fill as

select weight from root.mqtt.topic.abc454;
+------------------------+-----------------------------+
|                    Time|root.mqtt.topic.abc454.weight|
+------------------------+-----------------------------+
|2024-04-19T03:04:48.809Z|                         87.3|
|2024-04-19T03:04:49.809Z|                         87.3|
|2024-04-19T03:04:50.809Z|                         87.0|
|2024-04-19T03:04:51.809Z|                         87.3|
|2024-04-19T03:04:52.809Z|                         87.3|
|2024-04-19T03:04:53.809Z|                         87.0|
+------------------------+-----------------------------+

What did you see instead?

weight are null.

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[github-actions]

Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!

[CloudWise-Lukemiao]

Hello, are you upgrading IoTDB directly from version 1.1 to 1.3? Are there any other operations

[zhongwencool]

I didn't do any additional operations. I just used the official Docker image provided. apache/iotdb:1.3.0-standalone
Are there any other official 1.3.x images that I could try?

[CritasWang]

#12387

[zhongwencool]

@CloudWise-Lukemiao @CritasWang What version would this fix be included in, I don't see it in the latest version(1.3.1).

[CritasWang]

next version(1.3.2)