Closed jkim650 closed 2 months ago
3.2.x?
This should be a bug, and I will fix it later. Could you first specify the label explicitly as a workaround?
3.2.4 @tracymacding
This should be a bug, and I will fix it later. Could you first specify the label explicitly as a workaround?
Sure. Thanks.
@jkim650 I checks the current implementation of transaction stream load again, and it actually relies on the user provided label at begin. The behavior is as expected, and since 2.5. So I will fix the wrong document description.
Steps to reproduce the behavior (Required)
CREATE DATABASE IF NOT EXISTS test_db;
CREATE TABLE IF NOT EXISTS test_db.test_table (id INT NOT NULL) ENGINE=OLAP PROPERTIES ("replication_num" = "1");
curl --location-trusted -uroot: -H "Expect: 100-continue" -H "db: test_db" -H "table: test_table" -XPOST http://localhost:8030/api/transaction/begin -v
Expected behavior (Required)
Starrocks returns
"Status": "OK"
with a generated"Label"
as documented in https://docs.starrocks.io/docs/loading/Stream_Load_transaction_interface/#precautions.Real behavior (Required)
Starrocks returned
"Status": "FAILED"
withempty label
message.StarRocks version (Required)