question

Hi rambalac, Some move requests can be asynchronous, depending on if the node being moved is a folder or a file. This can also be a race condition between when the node is moved and when the search index is updated. How long after the move operation are the queries incorrect? Do they stay incorrect or does it go away after a short time?

Incorrect result happens with in about half a second, later it's correct. But what race condition here if server is already sending item without parentid used in request? Obviously server already has information about parent change. Yes, workaround is simple [i]Send folder children request -> from response remove all children whose parentId does not contain parentId in request[/i]. At least documentation should mention that filtered request can return response with items not matching request. Message was edited by: rambalac

This is expected behavior. Node storage and node searching are separate systems with eventual consistency. We will update our documentation to be more explicit about this behavior. Thanks!