Queries in MarkLogic always run at a fixed point in time with a consistent view of database state throughout. The query will never see changes to the database while it's running, so there is nothing to worry about there.
This part of the ML docs explains Point In Time Queries: https://docs.marklogic.com/guide/app-dev/point_in_time This is Jason Hunter's markLogic internal paper, which will explain MVCC and all the other magic going on inside: http://developer.marklogic.com/inside-marklogic --- Ron Hitchens {[email protected]} +44 7879 358212 On Jun 20, 2014, at 11:02 AM, Prasanth N V R <[email protected]> wrote: > Hi, > > I have a cts:search() query that executes on a particular document which > contains thousands of nodes. > > cts:search(//element , > cts:and-query(( > cts:document-query("/document.xml"), > ..... cts:queries with conditions.... > )) > ) > > In our scenario, this search query will get called recursively and accumulate > the output nodes from this document. > > When this query is executing at a time frame(15mins) , if the document got > deleted in the middle by different transaction what will happen. > > Let me know whether the query still continue running against the same > document in memory or the execution will stop. > > What will happen if an update operation happens in the middle of query > execution for the same document. > > Thanks, > Prasanth > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
