Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Garanteed order for child messages #2

Open
pjuza opened this issue Nov 15, 2014 · 0 comments
Open

Garanteed order for child messages #2

pjuza opened this issue Nov 15, 2014 · 0 comments
Assignees
Milestone

Comments

@pjuza
Copy link
Member

pjuza commented Nov 15, 2014

When new asynchronous child message is created then it has identical msgTimestamp as parent message. There is SQL query for garanteed order where you can find "ORDER BY m.msgTimestamp".
From this is not clear which message (parent or child) will be processed firstly - if first is parent message then child message won't be processed anymore, if first is child message then it will be ok.

Reference: CLVBUS-168

@pjuza pjuza added the bug label Nov 15, 2014
@pjuza pjuza self-assigned this Nov 15, 2014
@pjuza pjuza modified the milestones: Version 1.1, CleverBus 1.1, CleverBus 1.2 Nov 15, 2014
@pjuza pjuza added the Core label Nov 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants