Hi,
can someone clarify on the following behaviour?
The docs say:
"Job services can be updated: If a new job is registered, and if there
is already a job with the same id, the old entry will be replaced."
https://docs.basex.org/wiki/Jobs_Module#Services
So when I try to update
Hi Daniel,
I have decided to remove the misleading information in the
documentation as it would probably be confusing to explain the full
background:
• If a job is currently registered for scheduled execution, a new job
with the same name will be rejected.
• If the job has been registered as
Hi, Christian.
Thanks for the recommendation. Actually I started thinking of a proxy in
between the two servers that would perform data compression.
The experiments with generic archivers on my typical xml datasets showed the
best results with 7zip, both in terms of compression rate and
…nice wording.
Zimmel, Daniel schrieb am Do., 6. Mai 2021, 14:24:
> Thank you for the insight on how this works:
> so you cannot update a scheduled job, but you can update the
> jobs-to-be-scheduled.
>
> Helps a lot,
> Daniel
>
> -Ursprüngliche Nachricht-
> Von: Christian Grün
>
Thank you for the insight on how this works:
so you cannot update a scheduled job, but you can update the
jobs-to-be-scheduled.
Helps a lot,
Daniel
-Ursprüngliche Nachricht-
Von: Christian Grün
Gesendet: Donnerstag, 6. Mai 2021 13:52
An: Zimmel, Daniel
Cc:
Hi Philippe,
here’s one way to solve your challenge:
let $csv := csv:doc('exemple.csv')
let $doc := doc('exemple1.xml')
return $doc update {
for $text in .//text()
return replace node $text with (
for $token in analyze-string($text, '\p{L}+')/*
let $record := $csv//record[entry[1] =
Christian, I have just implemented your recommendation on activating GZIP based
on Jetty server. It yielded in 40% speed improvement. In my scenario a 151 Mb
query result was deflated to 8 Mb size for transport. The Power BI refresh time
decreased to 35’’ from 57-60’’.
Thanks a lot!
Mikhail
7 matches
Mail list logo
