Youngwb commented on issue #3930: URL: https://github.com/apache/incubator-doris/issues/3930#issuecomment-656441161
> > > I think it's better to handle the problem in load. > > > If you want to preserve the ordering, you can speculate the behavior in the load command. > > > CreateTable should not catch this logic, otherwise it's confused to people to understand the create table. > > > > > > If a sequence column is generated during the Load command phase, we need to consider the case where the user first load and specified a sequence column and then did not, or did not specify a sequence column the first time and then specified a sequence column. This will make the analysis of the load phase more complicated > > I think it's a problem about stable sort. If we can ensure the data received lately been flushed lately. > It seems can solve the problem rightly? yes, it's a problem about stable sort, I don't understand this "data received lately been flushed lately." . I think the node responsible for flush data does not guarantee orderly receipt of dataļ¼for example, the Broker Load will scan in multiple BE at the same time and send to the corresponding node, so that the order of sending data in the same key column cannot be guaranteed, and the results will be different even if the same source data is loaded multiple times ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
