Caideyipi commented on PR #11489: URL: https://github.com/apache/iotdb/pull/11489#issuecomment-1803771870
> > I finally discovered that when an event is collected in a connector, it's sequence is eliminated....Maybe the commitId must be assigned before any subtask picking this event, and the commitId may better be something like "static Map<connectorAttributes, commitId>" or "static Map<pendingQueue, commitId>".... > > Maybe we can assign the commitId atomically when the connectorSubtask polls an event. But some events are created inside transfer() when parsing pattern, do they need a commitId? I missed that, you can also use lock to make sure a connector assign an commitID right after poll... Then the sequence can be sure. It depents on your choice to realize it. -- 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]
