Changes

This [[Module Library|XQuery Module]] provides functions for evaluating XQuery expressions in separate threadsorganizing scheduled, queued, running and cached jobs. Query execution Jobs can both be parallelized and postponed to be executed asynchronouslycommands, queries, client or HTTP requests.

All functions in this module are assigned to the <code><nowiki>http://basex.org/modules/asyncjobs</nowiki></code> namespace, which is statically bound to the {{Code|asyncjobs}} prefix. Errors will be bound to the same prefix.

=Parallelized ExecutionServices=

A job can be registered as ''service'' by supplying the {{Code|service}} option to {{Function|Jobs|jobs:eval}}: <syntaxhighlight lang="xquery">(: register job as service; will be run every day at 1 am :)jobs:eval('db:drop("tmp")', (), map { 'id':'cleanup', 'start':'01:00:00', 'interval':'P1D', 'service': true() }), (: list registered services :)jobs:services(),(: result: <job base-uri="..." id="cleanup" interval="P1D" start="01:00:00">db:drop("tmp")</job> :) (: unregister job :)jobs:stop('cleanup', map { 'service': true() })</syntaxhighlight> '''Some more notes:''' * All job services will be scheduled for evaluation when the BaseX server or BaseX HTTP server is started.* If a job service is outdated (e.g. because a supplied end time has been exceeded), it will be removed from the jobs file at startup time.* The job definitions are stored in a {{Code|jobs.xml}} file in the database directory. It can also be edited manually. =Basic Functions= ==asyncjobs:forkcurrent== {| width='100%'|-join| width='120' | '''Signatures'''|{{Func|jobs:current||xs:string}}|-| '''Summary'''|Returns the id of the current job.|} ==jobs:list==

|{{Func|asyncjobs:fork-joinlist|$functions as function(*)*|item()*}}<br/ >{{Func|async:fork-join|$functions as function(*)*, $options as map(xs:string, xs:string)|item()*}}<br/ >

|'''Summary'''|This function executes Returns the supplied functions in parallelids of all jobs that are currently registered. The following {{Code|$options}} are available:* <code>threads</code>: maximum number of parallel threads (default: available number of cores)* <code>thread-size</code>: number of functions to be evaluated by each thread (default: <code>1</code>)list includes scheduled, queued, running, stopped, and finished jobs with cached results.

|<code>jobs:list()</code> returns the same job id as {{Function|Jobs|jobs:current}} if no other job is registered.|} * The following function sleeps in parallel; it will be finished in 1 second if your system has at least 2 cores==jobs:list-details==<pre class{| width='brush:xquery100%'>async:fork|-join( for $i in 1 to 2| width='120' | '''Signatures''' return function|{{Func|jobs:list-details||element(job) *}}<br/>{ prof{Func|jobs:list-details|$id as xs:sleepstring|element(1000job) *}}|-| '''Summary'''|Returns information on all jobs that are currently registered, or on a job with the specified {{Code|$id}} (or an empty sequence if this job is not found). The list includes scheduled, queued, running jobs, and cached jobs. A string representation of the job, or its URI, will be returned as value. The returned elements have additional attributes:* <code>id</precode>: job id* In <code>type</code>: type of the following job (command, query, up to two URLs will be requested in parallel:REST, RESTXQ, etc.)* <code>state<pre class='brush:xquery'/code>let $urls := (1 to 4) ! ('httpcurrent state of the job:<code>scheduled</code>, <code>queued</code>, <code>running</url.comcode>, <code>cached</path' || .)code>let $funcs * <code>user</code>:= $urls ! function() { httpuser who started the job* <code>duration</code>:send-request(evaluation time (included if a job is running or if the result was cached), .) },return async* <code>start</code>:fork-joinnext start of job ($funcs, map { 'threads': 2 }included if a job will be executed repeatedly)* <code>time</precode>: time when job was registered

|'''ErrorsExamples'''|{{Error|unexpected|#Errors}} an unexpected error occurred while <code>jobs:list-details()</code> returns information on the currently running job and possibly others:<syntaxhighlight lang="xml"><job id="job1" type="XQuery" state="running a query or function in a separate thread" user="admin" duration="PT0.001S"> XQUERY jobs:list-details()<br/job>{{Error|out-of-range|#Errors}} a supplied option is out of range.<br/syntaxhighlight>

=Asynchronous Execution=jobs:finished==

{| width='100%'|-| width=async'120' | '''Signatures'''|{{Func|jobs:evalfinished|$id as xs:string|xs:boolean}}|-| '''Summary'''|Indicates if the evaluation of an already running job with the specified {{Code|$id}} has finished. As the ids of finished jobs will usually be discarded, unless caching is enabled, the function will also return <code>true</code> for unknown jobs.* <code>false</code> indicates that the job id is scheduled, queued, or currently running.* <code>true</code> will be returned if the job has either finished, or if the id is unknown (because the ids of all finished jobs will not be cached).|} ==jobs:services==

|{{Func|asyncjobs:evalservices|$query as xs:string|xs:string}}<br />{{Func|async:eval|$query as xs:string, $bindings as mapelement(*job)|xs:string}}<br />{{Func|async:eval|$query as xs:string, $bindings as map(*), $options as map(xs:string, xs:string)|xs:string}}<br />

|Prepares the supplied {{Code|$query}} string for asynchronous execution and returns Returns a query id. The query will be queued list of all jobs that have been persistently registered as described in the article on [[Transaction Management]].<br/>Variables and context items can be declared via {{Code|$bindings}} (see [[XQuery Module#xquery:evalServices|xquery:eval]Services] for more details). The {{Code|$options}} parameter contains evaluation options:* {{Code|check}}: indicates if the query result will be cached.* {{Code|base-uri}}: set [https://www.w3.org/TR/xquery-31/#dt-static-base-uri base-uri property] for the query. This URI will be used when resolving relative URIs by functions such as {{Code|fn:doc}}.

|{{Error|updatingservices|#Errors}} the query contains update operationsRegistered services cannot be parsed.|-| '''Examples'''|* {{Code|async:eval("1+3")}} returns a query id, e.g. {{Code|Query-abc}}. The result can be retrieved via a second query in the same BaseX context: {{Code|async:result("Query-abc")}}<br />

=Execution=async There are cases in which a client does not, or cannot, wait until a request is fully processed. The client may be a browser, which sends an HTTP request to the server in order to start another time-consuming query job. The functions in this section allow you to register a new query job from a running query. Jobs can be executed immediately (i.e., as soon as the [[Transaction Management#Concurrency Control|Concurrency Control]] allows it) or scheduled for repeated execution. Each registered job gets a job id, and the id can be used to retrieve a query result, stop a job, or wait for its termination. ==jobs:updateeval== {{Mark|Updated with Version 9.5}}: Integers added as valid start and end times.

|{{Func|asyncjobs:updateeval|$query as xs:stringanyAtomicItem|xs:string}}<br />{{Func|asyncjobs:updateeval|$query as xs:stringanyAtomicItem, $bindings as map(*)?|xs:string}}<br />{{Func|asyncjobs:updateeval|$query as xs:stringanyAtomicItem, $bindings as map(*)?, $options as map(xs:string, xs:string*)?|xs:string}}<br />

|Prepares Schedules the evaluation of the supplied {{Code|$query}} string for asynchronous execution and returns a query id. The query will be queued as described in , and the article on result will optionally be cached. Queries can be updating. The query can be a URI or a string, and variables and context items can be declared via {{Code|$bindings}} (see [[Transaction ManagementXQuery Module#xquery:eval|xquery:eval]]for more details).The following {{Code|$options}} can be supplied:* {{Code|cache}}: indicates if the query result will be cached or ignored (default: <code>false<br/code>See ):** The result will be cached in main-memory until it is fetched via [[#asyncjobs:evalresult|asyncjobs:evalresult]] , or until {{Option|CACHETIMEOUT}} is exceeded.** If the query raises an error, it will be cached and returned instead.* {{Code|start}}: a dayTimeDuration, time, dateTime or integer can be specified to delay the execution of the query:** If a dayTimeDuration is specified, the query will be queued after the specified duration has passed. Examples for information on valid values are: <code>P1D</code> (1 day), <code>PT5M</code> (5 minutes), <code>PT0.1S</code> (100 ms). An error will be raised if a negative value is specified.** If a dateTime is specified, the query will be executed at this date. Examples for valid values are: <code>2018-12-31T23:59:59</code> (New Year's Eve 2018, close to midnight). An error will be raised if the specified time lies in the past.** If a time is specified, the query will be executed at this time of the day. Examples for valid times are: <code>02:00:00</code> (2am local time), <code>12:00:00Z</code> (noon, UTC). If the time lies in the past, the query will be executed the next day.** An integer will be interpreted as minutes. If the specified number exceeds the minutes of the current hour, the query will be executed one hour later.* {{Code|interval}}: a dayTimeDuration string can be specified to execute the query periodically. An error is raised if the specified interval is less than one second (<code>$bindingsPT1S</code> ). If the next scheduled call is due, and if a query with the same id is still running, it will be skipped.* {{Code|end}}: scheduling can be stopped after a given time or duration. The string format is the same as for {{Code|start}}. An error is raised if the resulting end time is smaller than the start time.* {{Code|base-uri}}: sets the [https://www.w3.org/TR/xquery-31/#dt-static-base-uri base-uri property] for the query. This URI will be used when resolving relative URIs, such as with {{Code|fn:doc}}.* {{Code|id}}: sets a custom job id. The id must not start with the standard <code>$optionsjob</code> argumentsprefix, and it can only be assigned if no job with the same name exists.* {{Code|service}}: additionally registers the job as [[#Services|service]]. Registered services must have no variable bindings.* {{Code|log}}: writes the specified string to the [[Logging|database logs]]. Two log entries are stored, one at the beginning and another one after the execution of the job.

|{{Error|non-updatingoverflow|#Errors}} Query execution is rejected, because too many jobs are queued or being executed. {{Option|CACHETIMEOUT}} can be decreased if the query does not contain any update operationsdefault 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.<br/>{{Error|options|#Errors}} The specified options are conflicting.

* Cache query result. The returned id can be used to pick up the result with [[#jobs:result|jobs:result]]:<codesyntaxhighlight lang="xquery">asyncjobs:updateeval("delete node db:open1+3", (), map { 'dbcache': true() })<//textsyntaxhighlight>* A happy birthday mail will be sent at the given date:<syntaxhighlight lang="xquery">jobs:eval("import module namespace mail='mail'; mail:send('Happy birthday!')", (), map {'start': '2018-09-01T06:00:00' })}}</syntaxhighlight>* The following [[RESTXQ]] functions can be called to execute a query at 2 am every day. An id will be returned by the first function, which can be used to stop the scheduler via the second function:<syntaxhighlight lang="xquery">declare %rest:POST("{$query}") %rest:path('/start-scheduling') function local:start($query) { jobs:eval($query, (), map { 'cachestart': '02:00:00', 'interval': 'P1D' })};declare %rest:path('/stop-scheduling/{$id}') function local: falsestop($id) { jobs:stop($id)});</codesyntaxhighlight> returns a * Query execution is scheduled for every second, and for 10 seconds in total. As the query iditself will take 1. 5 seconds, it will only be executed every second time:<syntaxhighlight lang="xquery">jobs:eval("prof:sleep(1500)", (), map { 'interval': 'PT1S', 'end': 'PT10S' })</syntaxhighlight>* The text nodes of query in the database specified file will be evaluated once:<codesyntaxhighlight lang="xquery">dbjobs:eval(xs:anyURI('cleanup.xq'))</codesyntaxhighlight> * The following expression, if stored in a file, will be deleted once the database is available for write access.evaluated every 5 seconds:<syntaxhighlight lang="xquery">jobs:eval( static-base-uri(), map { }, map { 'start': 'PT5S' })</syntaxhighlight>

==asyncjobs:result==

|{{Func|asyncjobs:result|$id as xs:string|item()*}}

|Returns the cached result of an asynchronously executed query a job with the specified query job {{Code|$id}}:* Results can only be retrieved once. After retrieval, the cached result will be discardeddropped.* If the query original job has raised an error, the cached error will be raised instead.

|{{Error|is-running|#Errors}} the query job is still running.<br/>{{Error|unknown|#Errors}} the supplied query id is unknown: The query id is unknown, or the result may has already have been retrieved, or query execution may have been stopped.<br/>

| * The following [[RESTXQ]] function will either return the result of a previously started job or raise an error:<syntaxhighlight lang="xquery">declare %rest:path('/result/{$id}') function local:result($id) { jobs:result($id)};</syntaxhighlight>* The following query returns demonstrates how the results of an asynchronously executed query. It will succeed, because both can be returned within the main and the asynchronous same query do not include write operations on concurrently used databases(see below why you should avoid this pattern in practice):<pre classsyntaxhighlight lang='brush:"xquery'">let $query := asyncjobs:eval('(1 to 10000000)[. = 1]', map { }, map { 'cache': true() })

hofjobs:until( function($result) { not(async:is-runningwait($query)) }, function($curr) { prof:sleep(10) }, () ), asyncjobs:result($query)

</presyntaxhighlight>Queries of this kind can cause deadlocks! If the original query and the new query perform updates on the same database, the second query will only be run after the first one has been executed, and the first query will wait for the second query forever. You should resort to [[XQuery Module#xquery:fork-join|xquery:fork-join]] if you want to have full control on parallel query execution.

==asyncjobs:is-runningstop==

|{{Func|asyncjobs:is-runningstop|$id as xs:string|xs:booleanempty-sequence()}}

|Indicates if Triggers the cancelation of a query job with the specified query {{Code|$id}} , drops the cached result of a query, or cancels a scheduled job. Unknown ids are ignored. All jobs are gracefully stopped; it is currently being evaluatedup to the process to decide when it is safe to shut down. The following {{Code|$options}} can be supplied:* {{Code|service}}: additionally removes the job from the [[#Services|job services]] list.

| '''ErrorsExamples'''|{{Error|unknown|#Errors}} the supplied query id is unknown<code>jobs:list()[. != jobs:current()] ! jobs: The query result may already have been retrieved, or query execution may have been stoppedstop(.)<br/code>stops and discards all jobs except for the current one.

==asyncjobs:stopwait==

|{{Func|asyncjobs:stopwait|$id as xs:string|xs:booleanempty-sequence()}}

|Cancels Waits for the execution completion of a query job with the specified query {{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.

|{{Error|unknownself|#Errors}} the supplied query id The current job is unknown: The query result may already have been retrieved, or query execution may have been stoppedaddressed.<br/>

|{{Code|unexpectedoptions}}| An unexpected error occurred while running a query or function in a separate threadThe specified options are conflicting.

|{{Code|out-of-rangeid}}| The supplied option specified id is out of rangeinvalid or has already been assigned.

|{{Code|updatingoverflow}}| A Too many queries or query is expected to be non-updating, but it performs updatesresults are queued.

|{{Code|nonrange}}| A specified time or duration is out of range.|-updating|{{Code|running}}| A query is expected to still running.|-|{{Code|self}}| The current job cannot be addressed.|-|{{Code|service}}| Registered services cannot be updatingparsed, but it does not perform updatesadded or removed.

;Version 89.05* Updated: {{Function|Jobs|jobs:eval}}: integers added as valid start and end times. ;Version 9.4* Updated: {{Function|Jobs|jobs:eval}}: option added for writing log entries.* Updated: {{Function|Jobs|jobs:list-details}}: interval added. ;Version 9.2* Deleted: jobs:invoke (merged with {{Function|Jobs|jobs:eval}})

;Version 9.1* Updated: Bound values may now contain no or more than one item in [[#client{{Function|Jobs|jobs:query|clientlist-details}}:query]]registration time added.

;Version 79.50* Added: {{Function|Jobs|jobs:invoke}}, [[#Services|Services]]

;Version 8.6* AddedUpdated: [[#client{{Function|Jobs|jobs:info|clienteval}}:info]]<code>id</code> option added.

The module was introduced with Version 78.35.