Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
no edit summary
|-
| '''Summary'''
|Returns information on all jobs that are currently registered. The list includes scheduled, queued, running jobs, and cached jobs. A string representation of the job , or its URI, will be returned in the text nodeas value. The returned elements have additional attributes:
* <code>id</code>: job id
* <code>type</code>: type of the job (command, query, REST, RESTXQ, etc.)
|-
| '''Summary'''
|Waits for the completion of a job with the specified {{Code|$id}}:* The function will terminate immediately if the job id is unknown. This is the case if a future job has not been queued yet, or if the id has already been discarded after job evaluation.* If the function is called with the id of a queued job, or repeatedly executed job, it may stall and never terminate.
|-
| '''Errors'''
map { 'start': 'PT5S' }
)
</pre>
|}
==jobs:invoke==
{{Mark|Introduced with Version 8.7}}
{| width='100%'
|-
| width='120' | '''Signatures'''
|{{Func|jobs:invoke|$uri as xs:string|xs:string}}<br />{{Func|jobs:invoke|$uri as xs:string, $bindings as map(*)?|xs:string}}<br />{{Func|jobs:invoke|$uri as xs:string, $bindings as map(*)?, $options as map(xs:string, xs:string)|xs:string}}<br />
|-
| '''Summary'''
|Schedules the evaluation of the XQuery expression located at {{Code|$uri}} and returns a query id. The semantics and remaining arguments are identical to [[#jobs:eval|jobs:eval]].
|-
| '''Errors'''
|{{Error|overflow|#Errors}} Query execution is rejected, because too many jobs are queued or being executed. {{Option|CACHETIMEOUT}} can be decreased if the default setting is too restrictive.<br/>{{Error|range|#Errors}} A specified time or duration is out of range.<br/>{{Error|id|#Errors}} The specified id is invalid or has already been assigned.
|-
| '''Examples'''
|
* Runs an XQuery expression that may perform some cleanups:
<pre class='brush:xquery'>
jobs:invoke("cleanup.xq", (), ())
</pre>
|}
)
</pre>
Please note that queries of this query kind can easily cause a deadlock deadlocks. For example, if both the original query and the query to be executed asynchronously perform updates on the same database, the second query would only be run after the first one has been executed , and the first query will be queuedwait forever. In practice. In practice, This is why you should avoid this pattern in practice and resort to [[XQuery Module#xquery:fork-join|xquery:fork-join]] if you want to do things in parallel.
|}
=Changelog=
;Version 8.7
* Added: [[#jobs:invoke|jobs:invoke]]
;Version 8.6
