BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

Edit to https://docs.basex.org/wiki/Database_Server and question
by Patrick Durusau 08 Mar '22

08 Mar '22

Greetings! I edited https://docs.basex.org/wiki/Database_Server to change: Add the stop keyword to gracefully shut down the server. to: Use |basexserverstop| or |basexserverstop.bat| to gracefully shut down the server. Question, in the first paragraph following this list, the text reads: "Pressing |Ctrl+c| will close all connections and databases and gracefully shut down the server process." True? False? Somewhere in between? If true it should be the third alternative after basexserverstop.bat, but then why the scripts if we can always Ctrl+c? What am I missing? Thanks! Patrick -- Patrick Durusau patrick(a)durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

2 3

Re: [basex-talk] Keyboard issue on MacBook (Apple M1 Pro)
by Alexander Holupirek 07 Mar '22

07 Mar '22

> Hello, I'm having a small but annoying issue with keyboard input in the BaseX GUI on a new MacBook (M1 Pro). I tend to use the U.S. International keyboard layout for ease of typing accented characters: e.g., using the apostrophe/quotation key as a dead key when typing é or ü. However, with this keyboard layout, the apos/quot key doesn't register at all in the BaseX GUI. It works as expected everywhere else. I've tried switching fonts, but that doesn't seem to help. Any ideas? Thanks in advance! Tim Hi Tim, I just tried what you described on a M1. Using 'International - PC' as keyboard layout and pressing three keys, namely 'SHIFT' + 'QUOT' + 'A' gives me the following behaviour: Terminal-App (and other apps): App | Keys | Description -------------|-----------|----------------------------------------------- Terminal-App | SHIFT | (nothing happens) | " | a double quot sign (") in a (yellow) highlighted square | a | the german umlaut a (ä) on default background appears In BaseXGUI: App | Keys | Description -------------|-----------|----------------------------------------------- BaseXGUI | SHIFT | (nothing happens) | " | (nothing happens) | a | the german umlaut a (ä) on default background appears So it seems that the indication / user feedback is missing in BaseXGUI, but the umlaut character can nevertheless be entered. Do you experience the same? Alex

2 3

Results of some experiments for improving full-text search speeds
by Tamara Marnell 05 Mar '22

05 Mar '22

Good morning--I hope everyone in Europe is safe and well. This week I've been working on improving the speed of full-text searches in our website, and I wanted to share what I've found to be helpful and not so helpful. Our project: We run a website of finding aids from 47 archival repositories in the western US. Archivists submit their finding aids as EADs through a CMS that indexes each document for full-text searching in BaseX, with other custom indexes for facets like subject, material type, etc. https://archiveswest.orbiscascade.org/ Our issue: We need to perform full-text searches that match documents with all of the terms in the query. The BaseX full-text index and ft:search() function work at the text node level. So we need to use the mode "any word," then group by a unique identifier in the root and run an ft:contains() with the mode "all words," like this: for $db_id in tokenize($d, '\|') for $result in ft:search($db_id, $terms, map{'mode':'any word','fuzzy':$f}) let $ead := $result/ancestor::ead let $ark := normalize-space($ead/eadheader/eadid/@identifier) (: Other node values fetched here :) group by $ark where ft:contains(string-join($result, ' '), $terms, map{'mode':'all words','fuzzy':$f}) (: Custom ranking calculations based on other node values performed here :) return <ark>{$ark}</ark> Most users of the site are interested in their repositories only, and they use only a few words to find known collections, so most of the time results are delivered in less than 5 seconds. If users want to search for multiple terms across all 47 repositories, though, the search was taking 30-40 seconds. What I DIDN'T find helpful: Modifying the XQuery 1. Performing a separate search for each term and mapping to fetch with db:open-id() later, instead of searching for all terms at once and grouping. This was slightly slower: for $db_id in tokenize($d, '\|') let $results := fold-left( (: Get the ft:search() results as a map of node IDs and results :) ) for $node_id in map:keys($results) let $ead := db:open-id($db_id, $node_id) (: Ranking etc. :) 2. For multi-term queries, creating a temporary table to search instead of the complete full-text indexes of all databases. a. Create a database like temp123456 with a full-text index. b. For the first term, loop through all databases add the documents to temp123456 with db:add($temp_id, db:path($ead)) and optimize. c. For subsequent terms, map the results of a full-text search temp123456 instead of looping through all 47 databases, and then loop through all EADs in the temp database and remove the ones that don't match with... if (not(exists($temp_results(db:node-id($ead))))) then db:delete($temp_id, db:path($ead)) d. For the final term, return the usual ranked <ark /> values, then drop the database. This didn't work because the optimization of the temporary databases took a long time--25-30 seconds for a term with 1K document results, according to the BaseX logs. It would work in theory only if the existing full-text index could be parceled out for subsequent terms, instead of being freshly rebuilt. What I DID find helpful: Changing the server We use Amazon Web Services, so I experimented with putting the project on different instance types: General, Memory-Optimized, and Compute-Optimized. The contenders: General t2.medium: 2 vCPU, 4 GB memory General t3.large: 2 vCPU, 8 GB memory Compute-optimized c6g.xlarge: 4 vCPU, 8 GB memory Memory-optimized r6g.large: 2 vCPU, 16 GB memory At the time of testing we were on t2.medium, which is the most affordable and the smallest I thought would be sufficient. For one-term queries, the difference in speed was not that much across the instance types. For longer queries, the number of virtual CPUs and memory made a big difference. Query: native american tribes in oregon t2.medium: 55 seconds t3.large: 30 seconds r6g.large: 22 seconds c6g.xlarge: 21 seconds Memory: - Increasing from 4 GB on the t2.medium to 8 GB on the t3.large and c6g.xlarge nearly doubled the speed of my queries, even for queries of 2 words like "women's march" (20 seconds on t2.medium, 8-10 seconds on the others). - Increasing from 8 GB to 16 GB on a memory-optimized instance didn't affect the speed. The java process used only 10% of the available memory, versus 50-60% on other instance types, but the speed wasn't any faster, even increasing the maximum heap size in the basexhttp startup script. This could be because heap size isn't the right property to adjust. CPU: - Increasing from 2 vCPU to 4 vCPU on a compute-optimized instance improved speeds only for extreme queries of 4 words or more. papers t3.large: 6 seconds c6g.xlarge: 7 seconds family papers t3.large: 18 seconds c6g.xlarge: 18 seconds adams family papers t3.large: 15 seconds c6g.xlarge: 14 seconds adams family papers utah t3.large: 25 seconds c6g.xlarge: 21 seconds For most queries our users are performing, which are short and restricted to one repository, it's a negligible difference that didn't justify the increase in cost for a compute-optimized instance ($40 per month vs. $60 per month). -Tamara -- Tamara Marnell Program Manager, Systems Orbis Cascade Alliance (orbiscascade.org <https://www.orbiscascade.org/>) Pronouns: she/her/hers

3 7

Keyboard issue on MacBook (Apple M1 Pro)
by Tim Thompson 05 Mar '22

05 Mar '22

Hello, I'm having a small but annoying issue with keyboard input in the BaseX GUI on a new MacBook (M1 Pro). I tend to use the U.S. International keyboard layout for ease of typing accented characters: e.g., using the apostrophe/quotation key as a dead key when typing é or ü. However, with this keyboard layout, the apos/quot key doesn't register at all in the BaseX GUI. It works as expected everywhere else. I've tried switching fonts, but that doesn't seem to help. Any ideas? Thanks in advance! Tim -- -- Tim A. Thompson Discovery Metadata Librarian Yale University Library 344 Winchester Street New Haven, Connecticut 06511 (203) 432-4189 (office) (201) 423-9972 (mobile) www.linkedin.com/in/timathompson timothy.thompson(a)yale.edu

1 0

have a query report a warning?
by Graydon Saunders 04 Mar '22

04 Mar '22

Hello all -- XPath has an error function, https://www.w3.org/TR/xpath-functions-31/#func-error which stops processing, which isn't wanted when it's just a warning. ("this thing has problems; on to the next thing" shouldn't stop processing.) XPath has a trace function, https://www.w3.org/TR/xpath-functions-31/#func-trace which emits text, but which I think is like xsl:message and will write to STDOUT rather than STDERR. This leaves me thinking I've missed something -- how should I have a query give a warning? I'm not finding something BaseX specific; I'm fairly sure neither error() nor trace() are correct. Any suggestions? Thanks! Graydon

2 2

validate:xsd-info agains more than one schema
by Arantza Etxebarria Pablo 04 Mar '22

04 Mar '22

Dear Community, We have been trying to validate a file using the function *validate:xsd-info*($input as item(), $schema as item()?) as xs:string* against several different schemas and, we don't know how to send the parameter “schema” with more than one schema for this function. We have tried to declare the variable *schema *like this : let $schema:= " http://inspire.ec.europa.eu/schemas/bu-base/4.0/BuildingsBase.xsd http://schemas.opengis.net/gml/3.2.1/gml.xsd" But it returns this error message: XML document 'example.gml': -1:-1: schema_reference.4: Failed to read schema document ' http://inspire.ec.europa.eu/schemas/bu-base/4.0/BuildingsBase.xsd http://schemas.opengis.net/gml/3.2.1/gml.xsd' , because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. I have tried this function when no schema is given and it takes the contain of schemaLocation attribute, and in this case, is able to validate more than one schema. But I need to pass the schemas through a variable Could any of you point us in the right direction? Thanks -- *Arantza Etxebarria *

3 2

Re: [basex-talk] feature request: opening database at arbitrary file path
by Eric Levy 03 Mar '22

03 Mar '22

On Tue, 2022-02-22 at 23:10 +0100, Christian Grün wrote: > > The other contributor's comments were deeply rooted in particular > > assumptions that stood in stark contrast to the scenario I had > > described. > > It always depends on the way you interpret others’ comments. But > we're getting circular again (there must be a reason for it ;). > > > To me, "embedded" and "standalone" carry the same > > implication in the context of a database > > I see. With standalone, we want to indicate that the application > stands “on its own” and needs no external accessors. In contrast, > something that's embedded is fully dependant on other applications. > > In other words, if we use BaseX embedded, we import it as Java > library. If we use it as standalone processor, we access it > externally, similar to other installed applications and along with > all their idiosyncrasies. > > Would Java be an option for you? I understand the distinction. It seems the issues I originally raised would be the same in both cases. The difference is whether the application would be built as a collection of scripts versus a full Java application. I had planned to begin with Bash scripts calling the command-line database application, and then migrate to a more integrated application model (e.g. Java application using a library) only if required by the evolving needs. Frankly, I would hope to avoid the latter for the foreseeable future, as both the overall application complexity and maintenance resources are rather limited. However, as I explained, the overriding concern is whether the databases may be maintained inside of projects' folders without any dependency on resources elsewhere on the file system.

3 11

How Best to Determine What BaseX Is Doing When It Pegs the Processor?
by Eliot Kimber 03 Mar '22

03 Mar '22

I have a RESTXQ page that makes a query call to construct a report and then displays it. When I run this page something is triggering BaseX to peg the processor and it basically never returns from whatever it is doing. Using proc:dump() I can see that the call to construct the report runs and returns the expected value—this takes about 3 seconds, and then the page never returns and top shows that the java process for the BaseX HTTP server is pegged at 100%. The behavior is consistent so I know it must be something I’m doing or the effect of some configuration setting I have but no idea what might be going on. I get the behavior both on my development machine and on my production server, so it must be something in my code or some reproducible issue with the databases I’m managing. I’ve tried connecting the BaseX HTTP server to the Eclipse debugger, which works, but I’m not sure where I should be focusing my attention in the code. Turning on the -d flag isn’t that helpful either as the log is flooded with exceptions from BaseX trying to load Java classes for my XQuery modules, which swamps any more detailed debugging log messages and what messages I see appear to be entirely about the HTTP interaction, not what’s happening in the core BaseX server. Is there a particular place in the code I can focus on in the interactive debugger that would be a likely source of the behavior or another debugging technique I haven’t considered? Thanks, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow>

2 4

Re: [basex-talk] Declaring a variable in bxs that carries over to called xquery scripts
by ETANCHAUD Fabrice 02 Mar '22

02 Mar '22

Hi Patrick, I don't think bxs scripts have something like variables (but I may have missed the point with all the work BaseX team achieves). Bindings are way to parametrize XQuery scripts, and you can indeed set external variables' value in bxs, or on command line. Best regards, Fabrice Here are a few examples : https://docs.basex.org/wiki/Options#BINDINGS Options - BaseX Documentation<https://docs.basex.org/wiki/Options#BINDINGS> This page is linked from the Getting Started Section.. The options listed on this page influence the way how database commands are executed and XQuery expressions are evaluated. Two kinds of options exist: Global Options are valid for all BaseX instances in the same JVM. This is particularly relevant if you are working with the client/server architecture. docs.basex.org https://docs.basex.org/wiki/Command-Line_Options Command-Line Options - BaseX Documentation<https://docs.basex.org/wiki/Command-Line_Options> Standalone []. The following options are available for the standalone Command-Line Client: $ basex -h BaseX [Standalone] Usage: basex [-bcdiIoqrRstuvVwxz] [input] [input] XQuery or command file, or query string -b<args> Bind external query variables -c<input> Execute commands from file or string -d Toggle debugging output -i<input> Bind file or database to context -I<input> Bind input string ... docs.basex.org ________________________________ De: BaseX-Talk de la part de Patrick Durusau Envoyé: Mercredi 02 mars 2022 01:38 À: basex-talk(a)mailman.uni-konstanz.de Objet: [basex-talk] Declaring a variable in bxs that carries over to called xquery scripts Greetings! What I thought would be a simple task has turned out to not be so simple. I wrote: SET CHOP false SET EXPORTER indent=no,omit-xml-declaration=no SET BINDINGS $ndb=Ruth CREATE DB $ndb ./sources/Ruth.xml In BaseX 9.6.4, and when testing it I got this result: CHOP: false EXPORTER: indent=no,omit-xml-declaration=no BINDINGS: $ndb=Ruth Database '$ndb' created in 544.5 ms. What? Why isn't the mapping of Ruth to the variable $ndb effective in the bxs file? Moreover, there are query files that follow in the bxs file that I want to have resolve $ndb to Ruth (the desired name of the database). 1) How should I declare a variable in a bxs file? 2) In such a way that it carries over to following xquery files? BTW, I've seen this posting by Christian: https://stackoverflow.com/questions/28018354/how-to-run-a-xquery-with-xml-f… but it doesn't seem to be working for me. What am I missing? Thanks! Patrick <https://twitter.com/servicenow>-- Patrick Durusau patrick(a)durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

1 0

CREATEFILTER Setting Not Being Applied
by Eliot Kimber 02 Mar '22

02 Mar '22

In my basex/.basex file I have this local option: # Local Options CREATEFILTER=*.xml,*.dita,*.ditamap I have three BaseX instances running. And in the DBA panel for an instance not running on the default port (i.e., on port 10894) I see this in the Local Options column: CREATEFILTER *.xml,*.dita,*.ditamap SKIPCORRUPT ✓ However, if I do this from the Query console of that same server: db:create(‘mydatabase’, ‘/path/to/docs’) The resulting database only reflects .xml files, not .dita or .ditamap files. I’m wondering if this is a bug in how CREATEFILTER is being applied or my misunderstanding of the implications for CREATEFILTER? This is running 9.6.4 on Centos. If I specify createfilter directly on the db:create() call then of course it works as expected. Cheers, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow>

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk