longdpt opened a new issue, #17564:
URL: https://github.com/apache/doris/issues/17564

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   doris-1.2.1-rc01
   
   
   ### What's Wrong?
   
           Streamload spent 1 week of data from kafka, about 5000W, about 500W 
in Table A (unique Module, 60 columns) and 10W+ in  primary key, fink storage 
window for 5 seconds, and multiple records in Table A in the same window 
(batch). Two Sequence column enabled schemes were tried:
   1、
   httpPut.setHeader("function_column.sequence_col", sequence_col)  -- Doris
   httpPut.setHeader("merge_condition", sequence_col)   -- StarRocks
   
   2. Specify the Sequence column when building the table:
   PROPERTIES (
   "function_column.sequence_col" = 'column_name',
   );
   
   
   Sequence Corresponding column values are used for binlog filename and the 
offset position,Multiple verification of the Sequence column value is no 
problem, and has been normally passed into the Streamload, the verification 
method as flow:
   1、record the unique key+ columnXX + SEQUENCE VALUE  and Verfirm that it is 
passed into the json array ;
   2、The same batch data into StarRocks, data normal (expected result);
   
   
   Results in doris:
   All primary key records are stored normally, but about 3-5% of the data are 
not stored in the expected order in column Sequence
   
   ### What You Expected?
   
   All the data are stored in the order of column Sequence
   
   ### How to Reproduce?
   
   _No response_
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to