-
Notifications
You must be signed in to change notification settings - Fork 68
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
livequery process, keeps throwing errors when the live result is not the first in the processing queue #36
Comments
Hi, We're trying to incorporate LiveQuery in our node project and always receive a particular error once multiple updates are carried out in quite a short time. db.liveQuery("LIVE SELECT FROM FooClass").on('live-update', function(data) { is returning: We're using OrientDB 2.1.12 (but has been observed since 2.1.8) and OrientJS 2.1.11. Also tried with the respective 2.2 versions but in that case the callback is never called (although the very same database has cleanly been imported into both OrientDB instances), we just can't get it running in 2.2. Are any additional configuration steps necessary for 2.2 to make LiveQuery in node.js work? (btw also tried with the OrientJS 2.2.x branch - no luck). We also tried the suggested fix (#43 transport fix for live query) - but unfortunately this lead to other errors. Anyone experiencing similar issues? Thanks |
hi @kaYcee i'm looking at it now. I will let you know |
I'm having the same issue with OrientDb v.2.2.2. The callback for LiveQuery is NEVER called! |
hey @kaYcee any news when this will be fixed...Live Query has been unusable for me since i'm relying the orientjs API. |
hi @iamlogiq which version of OrientDB and OrientJS? |
@maggiolo00 The callbacks ('live-insert, live-delete, live-update) for LiveQuery are NEVER called! |
can you provide a test script ? they are running fine in tests https://github.com/orientechnologies/orientjs/blob/master/test/db/live-query.js |
can you add the config
in the configuration? it should resolve |
@maggiolo00 Which config file are you referring to? |
In cases when the processing queue contains LIVE_RESULT only on the second or third member it throws an
Unhandled rejection OrientDB.ProtocolError:
Unsupported operation status: 6
while 6 is the LIVE_RESULT operation status and should be fully supported
this mostly happens when quite a few updates are very quickly emited
The text was updated successfully, but these errors were encountered: