Hi Anastasiou (and thanks Bridger),
BaseX fails with a message along the lines “This is too big for one database”.
Are there any logs, beyond the DB logs? If yes, where can I find
them?
I'm not sure how to enable more verbose logging with the GUI -- hopefully one of the devs or power users can weigh in on this.
You can enable the debugging mode, e.g. by entering "set debug true" in the GUI command input panel on top. If the returned feedback does not help, it would be interested in the exact error message you get (because there may be several reasons why the input is too large for a single database).
The parser options include reading XML files from archives, which
is very convenient, but once the file has been parsed, does BaseX require the “originals” for queries / returning results?
AFAIK, no it does not. BaseX will query and return results from the internal database(s).
Exactly!
Is it possible to do federation with BaseX? In other words, let’s
say I split a database in two large parts (as per #1), is it possible to launch two baseX servers and then have them talk to each other so that ultimately I just query one of them and get back unified results?
AFAIK, the preferred method is to split your files across many databases, then query multiple databases from a single expression[1]. Others will be able to speak to this better, but I don't think there's a straightforward way to run multiple BaseX servers in a single JVM.
Exactly!