On Sat, 2022-02-19 at 16:05 -0500, Jonathan Robie wrote:
> If I am running my queries and updates on a typical laptop, would
> they run much faster if I ran them on a suitably configured instance
> in the cloud?
"suitably configured" is very subjective. Potentially your queries
could run a lot
I recently learned that BaseX offers no true support for access to a
database given directly by its path.
In contrast, opening a database by file path is a well-established
pattern in embedded databases, seen for example in SQLite, which
permits use of any database given by an arbitrary path,
If I am running my queries and updates on a typical laptop, would they run
much faster if I ran them on a suitably configured instance in the cloud?
I know this is a very general question, but I'm wondering what experiences
y'all have had with this.
Jonathan
I have some processes that update databases, taking a long time to do so.
I would like other processes to be able to read the last complete snapshot
while this happens. Is that possible?
Jonathan
No worries—I’ll try to make something smaller at some point. I’m sorry my
initial attempt didn’t work. Did not mean to waste your time with that. The
orchestration bit is possibly useful as a standalone thing so might be worth
taking the effort to package it as its own little github project.
I still get numerous parsing errors when opening your project files
with BaseX, and I’m sorry I don’t have time to track all this down. If
you believe that anything of your code that can still be dropped, feel
free to give it a go. See e.g. [1] for some hints on some suggestions.
[1]
Let me remake the sample code—it should all be there—with my now-working job
construction log.
The issue with the unit tests not seeing the results of the jobs remains.
I’ve attached take 2 of the code, which fixes my earlier bug with job creation
and running, so that, for example, the
I guess the function dutils:getDirectReferences is still missing in
your example.
But I’m glad to hear you’ve already found the bug.
FYI, I’ve fixed the bugs in my job construction logic. Constructing a
non-trivial XQuery from XQuery can be a challenge. Thank goodness for string
consructors in XQuery 3.
Cheers,
E.
_
Eliot Kimber
Sr Staff Content Engineer
O: 512 554 9368
M: 512
Attached is a Zip with two directories:
* repo/ contains the deployed modules—just copy now/ into basex/repo
* test/ contains test-orchestration.xqy, which should run correctly using
the TEST command
The tests I’m focused on are test:runJob1, test:runJob2, and
test:runMultipleJobs():
I can provide an example but I think I see what’s happening: The jobs are not
run until the unit tests complete—I see all the messages from the jobs emitted
after all the messages from any unit tests. The fact that the jobs do run and
do what I expect supports that analysis.
I’ll put together
Could you provide us with a little self-contained example?
Thanks in advance,
Christian
On Sat, Feb 19, 2022 at 3:56 PM Eliot Kimber
wrote:
>
> I’m working out my new-and-improved orchestration mechanism using the
> job-chaining approach and I’m not getting the unit test behavior I was
>
I’m working out my new-and-improved orchestration mechanism using the
job-chaining approach and I’m not getting the unit test behavior I was
expecting.
My current unit test is:
declare %unit:after("test:runMultipleJobs") function
test:afterRunMultipleJobs() {
(
for $database in
13 matches
Mail list logo
