Menu
▾
▴
exist-open — Open discussion
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(31) |
Nov
(25) |
Dec
(33) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(48) |
Feb
(62) |
Mar
(22) |
Apr
(29) |
May
(9) |
Jun
(45) |
Jul
(28) |
Aug
(41) |
Sep
(60) |
Oct
(96) |
Nov
(99) |
Dec
(70) |
| 2003 |
Jan
(98) |
Feb
(159) |
Mar
(164) |
Apr
(150) |
May
(143) |
Jun
(97) |
Jul
(184) |
Aug
(143) |
Sep
(207) |
Oct
(126) |
Nov
(159) |
Dec
(165) |
| 2004 |
Jan
(131) |
Feb
(229) |
Mar
(220) |
Apr
(212) |
May
(320) |
Jun
(223) |
Jul
(191) |
Aug
(390) |
Sep
(261) |
Oct
(229) |
Nov
(215) |
Dec
(184) |
| 2005 |
Jan
(221) |
Feb
(312) |
Mar
(336) |
Apr
(273) |
May
(359) |
Jun
(277) |
Jul
(303) |
Aug
(321) |
Sep
(256) |
Oct
(415) |
Nov
(428) |
Dec
(508) |
| 2006 |
Jan
(585) |
Feb
(419) |
Mar
(496) |
Apr
(296) |
May
(403) |
Jun
(404) |
Jul
(553) |
Aug
(296) |
Sep
(252) |
Oct
(416) |
Nov
(414) |
Dec
(245) |
| 2007 |
Jan
(354) |
Feb
(422) |
Mar
(389) |
Apr
(298) |
May
(397) |
Jun
(318) |
Jul
(315) |
Aug
(339) |
Sep
(253) |
Oct
(317) |
Nov
(350) |
Dec
(264) |
| 2008 |
Jan
(353) |
Feb
(313) |
Mar
(433) |
Apr
(383) |
May
(343) |
Jun
(355) |
Jul
(321) |
Aug
(338) |
Sep
(242) |
Oct
(206) |
Nov
(199) |
Dec
(279) |
| 2009 |
Jan
(327) |
Feb
(221) |
Mar
(280) |
Apr
(278) |
May
(237) |
Jun
(345) |
Jul
(322) |
Aug
(324) |
Sep
(676) |
Oct
(586) |
Nov
(735) |
Dec
(329) |
| 2010 |
Jan
(619) |
Feb
(424) |
Mar
(529) |
Apr
(241) |
May
(312) |
Jun
(554) |
Jul
(698) |
Aug
(576) |
Sep
(408) |
Oct
(268) |
Nov
(391) |
Dec
(426) |
| 2011 |
Jan
(629) |
Feb
(512) |
Mar
(465) |
Apr
(467) |
May
(475) |
Jun
(403) |
Jul
(426) |
Aug
(542) |
Sep
(418) |
Oct
(620) |
Nov
(614) |
Dec
(358) |
| 2012 |
Jan
(357) |
Feb
(466) |
Mar
(344) |
Apr
(215) |
May
(408) |
Jun
(375) |
Jul
(241) |
Aug
(260) |
Sep
(401) |
Oct
(461) |
Nov
(498) |
Dec
(294) |
| 2013 |
Jan
(453) |
Feb
(447) |
Mar
(434) |
Apr
(326) |
May
(295) |
Jun
(471) |
Jul
(463) |
Aug
(278) |
Sep
(525) |
Oct
(343) |
Nov
(389) |
Dec
(405) |
| 2014 |
Jan
(564) |
Feb
(324) |
Mar
(319) |
Apr
(319) |
May
(384) |
Jun
(259) |
Jul
(210) |
Aug
(219) |
Sep
(315) |
Oct
(478) |
Nov
(207) |
Dec
(316) |
| 2015 |
Jan
(222) |
Feb
(234) |
Mar
(201) |
Apr
(145) |
May
(367) |
Jun
(318) |
Jul
(195) |
Aug
(210) |
Sep
(234) |
Oct
(248) |
Nov
(217) |
Dec
(189) |
| 2016 |
Jan
(219) |
Feb
(177) |
Mar
(110) |
Apr
(91) |
May
(159) |
Jun
(124) |
Jul
(192) |
Aug
(119) |
Sep
(125) |
Oct
(64) |
Nov
(80) |
Dec
(68) |
| 2017 |
Jan
(156) |
Feb
(312) |
Mar
(386) |
Apr
(217) |
May
(89) |
Jun
(115) |
Jul
(79) |
Aug
(122) |
Sep
(100) |
Oct
(99) |
Nov
(129) |
Dec
(77) |
| 2018 |
Jan
(106) |
Feb
(78) |
Mar
(160) |
Apr
(73) |
May
(110) |
Jun
(160) |
Jul
(93) |
Aug
(92) |
Sep
(75) |
Oct
(147) |
Nov
(114) |
Dec
(97) |
| 2019 |
Jan
(141) |
Feb
(78) |
Mar
(158) |
Apr
(60) |
May
(123) |
Jun
(54) |
Jul
(44) |
Aug
(147) |
Sep
(117) |
Oct
(54) |
Nov
(74) |
Dec
(96) |
| 2020 |
Jan
(113) |
Feb
(125) |
Mar
(142) |
Apr
(57) |
May
(71) |
Jun
(99) |
Jul
(58) |
Aug
(81) |
Sep
(49) |
Oct
(50) |
Nov
(63) |
Dec
(37) |
| 2021 |
Jan
(37) |
Feb
(45) |
Mar
(39) |
Apr
(18) |
May
(14) |
Jun
(9) |
Jul
(44) |
Aug
(23) |
Sep
(13) |
Oct
(31) |
Nov
(13) |
Dec
(33) |
| 2022 |
Jan
(17) |
Feb
(8) |
Mar
(32) |
Apr
(7) |
May
(17) |
Jun
(7) |
Jul
(36) |
Aug
(29) |
Sep
(9) |
Oct
(20) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(30) |
Feb
(37) |
Mar
(23) |
Apr
(1) |
May
(14) |
Jun
(5) |
Jul
(3) |
Aug
(6) |
Sep
(5) |
Oct
(48) |
Nov
(4) |
Dec
(29) |
| 2024 |
Jan
(1) |
Feb
|
Mar
(21) |
Apr
(6) |
May
(16) |
Jun
(41) |
Jul
(11) |
Aug
(17) |
Sep
(16) |
Oct
(11) |
Nov
(3) |
Dec
(9) |
| 2025 |
Jan
(7) |
Feb
(7) |
Mar
(6) |
Apr
(6) |
May
(30) |
Jun
(8) |
Jul
(10) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pieter L. <pie...@be...> - 2025-04-22 05:15:25
|
Hi Sascha,
I think the problem is that you can serialize a snippet using
fn:serialize but the whole response is serialized according to exist
serialization settings. Apart from the declare options route in the
prolog of your xquery, you can also set these inline via the following,
e.g. util:declare-option("exist:serialize", "method=json")
I think this will get you going.
Best,
Pieter
On 17/04/2025 15:25, Sascha Grabsch via Exist-open wrote:
> Dear list members,
>
> I'm trying to output different formats (XML and HTML5) from a single
> xquery script, but can't get it to work. Here is my test case:
>
> xquery version "3.1";
> let $p_format := request:get-parameter("format", ())
>
> let $test :=
> <html>
> <head>
> <title>Test Title</title>
> </head>
> <body>
> <h1>Hello, World!</h1>
> </body>
> </html>
>
> return
> if ($p_format = "tei-xml") then (serialize($test, map { "method":
> "xml" })) else (serialize($test, map { "method": "html" }))
>
>
> However in both cases this does not work as expected:
>
> method:xml - The serialization option method:xml does not return valid
> XML, since the returned document is wrongly escaped
> (<html><head><title>Test
> Title</title></head><body><h1>Hello,
> World!</h1></body></html>). The content-type in the
> response header however is correct ("application/xml").
>
> method:html - While the serialization option method:html correctly
> adds a doctype for HTML5 (i. e. <!DOCTYPE html>), the actual response
> in a browser is wrongly escaped (as in <!DOCTYPE html>
> <html><head><title>Test
> Title</title></head><body><h1>Hello,
> World!</h1></body></html>). Additionally the
> content-type in the response header is "application/xml" instead of
> "text/html".
>
>
> According to
> <https://exist-db.org/exist/apps/doc/xquery.xml#fn-serialize> I would
> have expected to be able to return different serializations via
> fn:serialize, but it seems it is only possible to have one
> serialization per XQuery script via "declare option exist:serialize ..."?
>
> I would be glad about any information or hints what I might be missing.
>
> Thanks a lot!
>
> Sascha
--
Pieter Lamers
John Benjamins Publishing Company
Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
Visiting Address: Klaprozenweg 75D, 1033 NN AMSTERDAM, The Netherlands
Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
tel: +31 20 630 4747
web: www.benjamins.com
|
|
From: Sascha G. <gr...@bb...> - 2025-04-17 13:48:05
|
Dear list members,
I'm trying to output different formats (XML and HTML5) from a single
xquery script, but can't get it to work. Here is my test case:
xquery version "3.1";
let $p_format := request:get-parameter("format", ())
let $test :=
<html>
<head>
<title>Test Title</title>
</head>
<body>
<h1>Hello, World!</h1>
</body>
</html>
return
if ($p_format = "tei-xml") then (serialize($test, map { "method":
"xml" })) else (serialize($test, map { "method": "html" }))
However in both cases this does not work as expected:
method:xml - The serialization option method:xml does not return valid
XML, since the returned document is wrongly escaped
(<html><head><title>Test
Title</title></head><body><h1>Hello,
World!</h1></body></html>). The content-type in the
response header however is correct ("application/xml").
method:html - While the serialization option method:html correctly adds
a doctype for HTML5 (i. e. <!DOCTYPE html>), the actual response in a
browser is wrongly escaped (as in <!DOCTYPE html>
<html><head><title>Test
Title</title></head><body><h1>Hello,
World!</h1></body></html>). Additionally the
content-type in the response header is "application/xml" instead of
"text/html".
According to
<https://exist-db.org/exist/apps/doc/xquery.xml#fn-serialize> I would
have expected to be able to return different serializations via
fn:serialize, but it seems it is only possible to have one serialization
per XQuery script via "declare option exist:serialize ..."?
I would be glad about any information or hints what I might be missing.
Thanks a lot!
Sascha
--
Berlin-Brandenburgische Akademie der Wissenschaften
TELOTA (The Electronic Life Of The Academy)
Jägerstr. 22/23 | 10117 Berlin
gr...@bb... | +49 30 20370 536
|
|
From: Eduard D. <ed...@fr...> - 2025-04-15 12:42:54
|
Solved this by using BackupSystemTask for just one collection, needed to dive into the code to find out the correct parameters. Eduard Drenth, Software Architekt ed...@fr... Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/ https://frysker.nl/ https://frisian.eu/ [cid:b8fb4d34-8acc-44b1-afa4-85f1d4419a8e] gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index ________________________________ From: Eduard Drenth <ed...@fr...> Sent: Friday, April 4, 2025 10:58 AM To: Exist-open <Exi...@li...> Subject: [Exist-open] backup fails Dear all, The full backups of exist-db (6.2) fail since ± a week. Looks like I can still download the data and I have a week old backup. Don't fully trust the backup though because the backup file is accompanied with a report (see below) that shows an error. exist logging shows: 31 Mar 2025 20:00:00,037 [db.exist.scheduler.quartz-worker-2] INFO (ConsistencyCheckTask.java [execute]:152) - Starting consistency check... 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:165) - Errors found: 1 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:170) - Fatal errors were found: pausing the consistency check task. 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO (ConsistencyCheckTask.java [execute]:175) - Finished consistency check 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO (ConsistencyCheckTask.java [execute]:179) - Starting backup... 31 Mar 2025 20:00:10,305 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Skipping damaged document collection.xconf 31 Mar 2025 20:00:30,270 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Found an orphaned document: collection.xconf Backup logging shows: DOCUMENT: 70237 of 70237 ---------------------------------------------- RESOURCE_ACCESS_FAILED: Failed to access document data Document ID: 2075 Regards, Eduard Eduard Drenth, Software Architekt ed...@fr... Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/ https://frysker.nl/ https://frisian.eu/ [cid:a4941762-f448-4133-a3bf-ef679ade1fa0] gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index |
|
From: Eduard D. <ed...@fr...> - 2025-04-04 09:33:21
|
Dear all, The full backups of exist-db (6.2) fail since ± a week. Looks like I can still download the data and I have a week old backup. Don't fully trust the backup though because the backup file is accompanied with a report (see below) that shows an error. exist logging shows: 31 Mar 2025 20:00:00,037 [db.exist.scheduler.quartz-worker-2] INFO (ConsistencyCheckTask.java [execute]:152) - Starting consistency check... 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:165) - Errors found: 1 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [execute]:170) - Fatal errors were found: pausing the consistency check task. 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO (ConsistencyCheckTask.java [execute]:175) - Finished consistency check 31 Mar 2025 20:00:01,616 [db.exist.scheduler.quartz-worker-2] INFO (ConsistencyCheckTask.java [execute]:179) - Starting backup... 31 Mar 2025 20:00:10,305 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Skipping damaged document collection.xconf 31 Mar 2025 20:00:30,270 [db.exist.scheduler.quartz-worker-2] ERROR (ConsistencyCheckTask.java [error]:250) - EXPORT: Found an orphaned document: collection.xconf Backup logging shows: DOCUMENT: 70237 of 70237 ---------------------------------------------- RESOURCE_ACCESS_FAILED: Failed to access document data Document ID: 2075 Regards, Eduard Eduard Drenth, Software Architekt ed...@fr... Doelestrjitte 8 8911 DX Ljouwert (058) 213 14 14 +31 62 094 34 28 https://www.fryske-akademy.nl/ https://frysker.nl/ https://frisian.eu/ [cid:a4941762-f448-4133-a3bf-ef679ade1fa0] gpg: https://keyserver.ubuntu.com/pks/lookup?search=eduard+drenth&fingerprint=on&op=index |
|
From: Alberto S. <am...@zb...> - 2025-03-21 09:44:00
|
Hello Thank you all. I have a collection with a large number of files that might be causing these shortages. Bumped the output size limit. Let's see how it handles it. Thanks Alberto Simões On Thursday, March 20th, 2025 at 08:55, Guillaume Mella <gui...@un...> wrote: > Hello, > > Le 19/03/2025 à 16:21, Alberto Simões a écrit : > >> Hello >> >> I am getting this message: Query exceeded predefined output-size-limit (1,000,000) for document fragments (see below complete log for error). >> >> What is the cause, and how can I fix it? >> Thanks > > You are reaching the limit defined in the self documented existdb/etc/conf.xml > > <!-- > > This is the global configuration for the query watchdog. The > > watchdog monitors all query processes, and can terminate any > > long-running queries if they exceed one of the predefined limits. > > These limits are as follows: > > - output-size-limit: > > this attribute limits the size of XML fragments constructed > > using XQuery, and thus sets the maximum amount of main memory a > > query is allowed to use. This limit is expressed as the maximum > > number of nodes allowed for an in-memory DOM tree. The purpose > > of this option is to avoid memory shortages on the server in > > cases where users are allowed to run queries that produce very > > large output fragments. > > - query-timeout: > > this attribute sets the maximum amount of time (expressed in > > milliseconds) that the query can take before it is killed.. > > --> > > <watchdog > > output-size-limit > > = > > "1000000" > > query-timeout > > = > > "-1" > > /> > > I often increase this value to one order of magnitude. even in the docker instances... > > Cheers, > -- > Guillaume |
|
From: Guillaume M. <gui...@un...> - 2025-03-20 09:12:27
|
Hello,
Le 19/03/2025 à 16:21, Alberto Simões a écrit :
> Hello
>
> I am getting this message: Query exceeded predefined output-size-limit
> (1,000,000) for document fragments (see below complete log for error).
>
> What is the cause, and how can I fix it?
> Thanks
You are reaching the limit defined in the self documented
existdb/etc/conf.xml
<!--
This is the global configuration for the query watchdog. The
watchdog monitors all query processes, and can terminate any
long-running queries if they exceed one of the predefined limits.
These limits are as follows:
- output-size-limit:
this attribute limits the size of XML fragments constructed
using XQuery, and thus sets the maximum amount of main memory a
query is allowed to use. This limit is expressed as the maximum
number of nodes allowed for an in-memory DOM tree. The purpose
of this option is to avoid memory shortages on the server in
cases where users are allowed to run queries that produce very
large output fragments.
- query-timeout:
this attribute sets the maximum amount of time (expressed in
milliseconds) that the query can take before it is killed..
-->
<watchdog output-size-limit="1000000"query-timeout="-1"/>
I often increase this value to one order of magnitude. even in the
docker instances...
Cheers,
--
Guillaume
|
|
From: Pieter L. <pie...@be...> - 2025-03-19 20:46:21
|
Hi Alberto,
on a main module you can set a different size limit. It is reached when
your output has too many nodes.
to get a max of 10M nodes use the following:
declare option exist:output-size-limit "10000000";
when I need to set a large output-size-limit in a function I use the
following function (which could be simplified):
declare function my:set-output-size-limit( $new-limit as xs:integer ) as
empty-sequence()
{
let $output-size-limit-option as xs:string := 'exist:output-size-limit'
let $set-output-size-limit :=
util:declare-option($output-size-limit-option, $new-limit cast as xs:string)
return ()
};
Best,
Pieter
On 19/03/2025 16:21, Alberto Simões wrote:
> Hello
>
> I am getting this message: Query exceeded predefined output-size-limit
> (1,000,000) for document fragments (see below complete log for error).
>
> What is the cause, and how can I fix it?
> Thanks
>
> lexmart_exist.1.vi427hqb2os7@academia | 19 Mar 2025 15:12:32,497
> [qtp478864778-47] WARN (XQueryWatchDog.java [proceed]:174) - Query
> exceeded predefined output-size-limit (1,000,000) for document
> fragments: {
> lexmart_exist.1.vi427hqb2os7@academia | for <130>
> lexmart_exist.1.vi427hqb2os7@academia | $resource in $subset
> lexmart_exist.1.vi427hqb2os7@academia | <131>
> lexmart_exist.1.vi427hqb2os7@academia | let <131>
> lexmart_exist.1.vi427hqb2os7@academia | $isCollection := $resource
> = "/",
> lexmart_exist.1.vi427hqb2os7@academia | let <132>
> lexmart_exist.1.vi427hqb2os7@academia | $path := if (
> lexmart_exist.1.vi427hqb2os7@academia | $isCollection
> lexmart_exist.1.vi427hqb2os7@academia | ) then
> lexmart_exist.1.vi427hqb2os7@academia |
> {http://www.w3.org/2005/xpath-functions}concat($collection
> <http://www.w3.org/2005/xpath-functions}concat($collection>, $resource)
> lexmart_exist.1.vi427hqb2os7@academia | else
> lexmart_exist.1.vi427hqb2os7@academia |
> {http://www.w3.org/2005/xpath-functions}concat($collection
> <http://www.w3.org/2005/xpath-functions}concat($collection>, "/",
> $resource)
> lexmart_exist.1.vi427hqb2os7@academia | return
> lexmart_exist.1.vi427hqb2os7@academia | where <137>
> lexmart_exist.1.vi427hqb2os7@academia |
> sm:has-access(untyped-value-check[xs:anyURI, $path cast as xs:anyURI],
> "r")
> lexmart_exist.1.vi427hqb2os7@academia |
> lexmart_exist.1.vi427hqb2os7@academia |
> lexmart_exist.1.vi427hqb2os7@academia | }
>
> --
> Alberto Simões
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
--
Pieter Lamers
John Benjamins Publishing Company
Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
Visiting Address: Klaprozenweg 75D, 1033 NN AMSTERDAM, The Netherlands
Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
tel: +31 20 630 4747
web:www.benjamins.com
|
|
From: Adam R. <ad...@ex...> - 2025-03-19 19:22:29
|
Take a look in conf.xml, you can increase the limit in there
On Wed, 19 Mar 2025, 19:07 Alberto Simões, <has...@gm...> wrote:
> Hello
>
> I am getting this message: Query exceeded predefined output-size-limit
> (1,000,000) for document fragments (see below complete log for error).
>
> What is the cause, and how can I fix it?
> Thanks
>
> lexmart_exist.1.vi427hqb2os7@academia | 19 Mar 2025 15:12:32,497
> [qtp478864778-47] WARN (XQueryWatchDog.java [proceed]:174) - Query
> exceeded predefined output-size-limit (1,000,000) for document fragments: {
> lexmart_exist.1.vi427hqb2os7@academia | for <130>
> lexmart_exist.1.vi427hqb2os7@academia | $resource in $subset
> lexmart_exist.1.vi427hqb2os7@academia | <131>
> lexmart_exist.1.vi427hqb2os7@academia | let <131>
> lexmart_exist.1.vi427hqb2os7@academia | $isCollection :=
> $resource = "/",
> lexmart_exist.1.vi427hqb2os7@academia | let <132>
> lexmart_exist.1.vi427hqb2os7@academia | $path := if (
> lexmart_exist.1.vi427hqb2os7@academia |
> $isCollection
> lexmart_exist.1.vi427hqb2os7@academia | ) then
> lexmart_exist.1.vi427hqb2os7@academia | {
> http://www.w3.org/2005/xpath-functions}concat($collection, $resource)
> lexmart_exist.1.vi427hqb2os7@academia | else
> lexmart_exist.1.vi427hqb2os7@academia | {
> http://www.w3.org/2005/xpath-functions}concat($collection, "/", $resource)
> lexmart_exist.1.vi427hqb2os7@academia | return
> lexmart_exist.1.vi427hqb2os7@academia | where <137>
> lexmart_exist.1.vi427hqb2os7@academia |
> sm:has-access(untyped-value-check[xs:anyURI, $path cast as xs:anyURI], "r")
> lexmart_exist.1.vi427hqb2os7@academia |
> lexmart_exist.1.vi427hqb2os7@academia |
> lexmart_exist.1.vi427hqb2os7@academia | }
>
> --
> Alberto Simões
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
|
|
From: Alberto S. <has...@gm...> - 2025-03-19 15:22:14
|
Hello
I am getting this message: Query exceeded predefined output-size-limit
(1,000,000) for document fragments (see below complete log for error).
What is the cause, and how can I fix it?
Thanks
lexmart_exist.1.vi427hqb2os7@academia | 19 Mar 2025 15:12:32,497
[qtp478864778-47] WARN (XQueryWatchDog.java [proceed]:174) - Query
exceeded predefined output-size-limit (1,000,000) for document fragments: {
lexmart_exist.1.vi427hqb2os7@academia | for <130>
lexmart_exist.1.vi427hqb2os7@academia | $resource in $subset
lexmart_exist.1.vi427hqb2os7@academia | <131>
lexmart_exist.1.vi427hqb2os7@academia | let <131>
lexmart_exist.1.vi427hqb2os7@academia | $isCollection :=
$resource = "/",
lexmart_exist.1.vi427hqb2os7@academia | let <132>
lexmart_exist.1.vi427hqb2os7@academia | $path := if (
lexmart_exist.1.vi427hqb2os7@academia | $isCollection
lexmart_exist.1.vi427hqb2os7@academia | ) then
lexmart_exist.1.vi427hqb2os7@academia | {
http://www.w3.org/2005/xpath-functions}concat($collection, $resource)
lexmart_exist.1.vi427hqb2os7@academia | else
lexmart_exist.1.vi427hqb2os7@academia | {
http://www.w3.org/2005/xpath-functions}concat($collection, "/", $resource)
lexmart_exist.1.vi427hqb2os7@academia | return
lexmart_exist.1.vi427hqb2os7@academia | where <137>
lexmart_exist.1.vi427hqb2os7@academia |
sm:has-access(untyped-value-check[xs:anyURI, $path cast as xs:anyURI], "r")
lexmart_exist.1.vi427hqb2os7@academia |
lexmart_exist.1.vi427hqb2os7@academia |
lexmart_exist.1.vi427hqb2os7@academia | }
--
Alberto Simões
|
|
From: Roth, M. <mat...@ya...> - 2025-03-13 16:54:04
|
Hi List, I am in the process of updating an exist-3.x instance to an exist-6.x instance. We would like to be able to directly clone, branch, and commit to a locally hosted git repository. In our eXist-3.x instance we do most of this via subversion and the old SVN module. But in the last decade we have migrated a lot of our local repositories to git and think this would be a good time to migrate away from this old dependency. The problem I am running into is I don't see any modules that currently replicate the same features of the old SVN module in git. I see two abandoned projects. 1. eXgit [0<https://github.com/shabanovd/eXgit/>] - This seemed to have the most community support 2. eXgit [1<https://github.com/dariok/eXgit/tree/master>] - Yeah, same name, different project. The xar would not work in 6.2.0, and the instructions for using the jar also seemed to not function, nor generate any log messages [2<https://github.com/eXist-db/documentation/issues/385>]. And two xquery modules that are designed to work with github. 1. Github-xq [3<https://github.com/eXist-db/github-xq>]- Winona's excellent module, but due to restrictions on our data github is not an option 2. Tuttle [4<https://github.com/eeditiones/tuttle>] - I suppose I could self-host gitlab, but not sure excited about a nodejs dep. So now I am left with a few questions 1. Is there a module for working with git I cannot locate? 2. If not, Why is there no longer a well maintained module for working with git or svn in eXist. * Is there no community desire for this? * Is this an anti-pattern, or might there be a more preferred way to handle this? 3. If I were to try to do something myself, I would want to create an EXPath Package or would I be wanting to create an extension such the Example in extensions/modules/example [5<https://github.com/eXist-db/exist/tree/develop/extensions/modules/example>]? * Or am I misunderstanding and these are similar? From my understanding the latter requires it being built and bundled with exist. Best, Matt [0] https://github.com/shabanovd/eXgit/ [1] https://github.com/dariok/eXgit/tree/master [2] https://github.com/eXist-db/documentation/issues/385 [3] https://github.com/eXist-db/github-xq [4] https://github.com/eeditiones/tuttle [5] https://github.com/eXist-db/exist/tree/develop/extensions/modules/example |
|
From: Hayim L. <hl...@um...> - 2025-02-18 17:37:11
|
Once again, thank you for this suggestion! Just to close this circle,
unfortunately, editing the conf.xml file did not solve the problem.
On Sun, Feb 16, 2025 at 4:14 AM Florian Schmitt <
ml-...@fl...> wrote:
> Hayim,
>
> it seems that in certain cases, the default apps aren't deployed
> correctly. If I remember correctly, I ran into a similar issue with a
> headless setup.
>
> Please try the following (assuming eXist is installed in /opt/existdb -
> adapt the paths according to your setup):
>
> First, check if there's a directory /opt/existdb/autodeploy containing the
> .xar files for eXide and so on.
>
> If the autodeploy directory seems fine, stop exist-db, and open
> /opt/existdb/etc/conf.xml in a text editor.
>
> Search for the following lines:
>
> <trigger class="org.exist.repo.AutoDeploymentTrigger">
> <!-- parameter name="ignore-autodeploy-system-property" value="true"/ -->
> <!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ -->
> </trigger>
>
> Uncomment the second "parameter" element, and change the "value"
> attribute, setting the full path to the autodeploy directory. With exist
> installed in /opt/existdb, the third line should now be
>
> <parameter name="dir" value="/opt/existdb/autodeploy" />
>
> Now, restart exist-db and check the logs for messages regarding
> autodeployment. If the AutoDeploymentTrigger doesn't fire, you may have to
> uncomment the first parameter element, too.
>
> HTH
> Florian
>
> Am 14.02.25 um 16:42 schrieb Hayim Lapin:
>
> Hello,
> I just installed eXist 6.3 on an aws linux machine running on port *8081*.
> The database loads and I can log in as admin.
> All the default apps that appear on the launcher yield errors like:
> HTTP ERROR 404 Document /db/apps/eXide not found
>
> I have been able to use the package manager to load and run an app
> (TEI-Publisher), but other apps created by me and working in a docker
> instance generate the following again caused by being unable to access /db:
>
>> err:XPST0017 error found while loading .... for module:
>> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line
>> 84, column 13]
>
>
> There is another version of exist (4.7.1) running on port *8080*. Could
> this be the cause of the problem?
>
> Any suggestions about how to fix this?
> Best, HL
>
>
> _______________________________________________
> Exist-open mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
|
|
From: Hayim L. <hl...@um...> - 2025-02-17 15:59:41
|
Thanks! I will definitely try this.
On Sun, Feb 16, 2025 at 4:14 AM Florian Schmitt <
ml-...@fl...> wrote:
> Hayim,
>
> it seems that in certain cases, the default apps aren't deployed
> correctly. If I remember correctly, I ran into a similar issue with a
> headless setup.
>
> Please try the following (assuming eXist is installed in /opt/existdb -
> adapt the paths according to your setup):
>
> First, check if there's a directory /opt/existdb/autodeploy containing the
> .xar files for eXide and so on.
>
> If the autodeploy directory seems fine, stop exist-db, and open
> /opt/existdb/etc/conf.xml in a text editor.
>
> Search for the following lines:
>
> <trigger class="org.exist.repo.AutoDeploymentTrigger">
> <!-- parameter name="ignore-autodeploy-system-property" value="true"/ -->
> <!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ -->
> </trigger>
>
> Uncomment the second "parameter" element, and change the "value"
> attribute, setting the full path to the autodeploy directory. With exist
> installed in /opt/existdb, the third line should now be
>
> <parameter name="dir" value="/opt/existdb/autodeploy" />
>
> Now, restart exist-db and check the logs for messages regarding
> autodeployment. If the AutoDeploymentTrigger doesn't fire, you may have to
> uncomment the first parameter element, too.
>
> HTH
> Florian
>
> Am 14.02.25 um 16:42 schrieb Hayim Lapin:
>
> Hello,
> I just installed eXist 6.3 on an aws linux machine running on port *8081*.
> The database loads and I can log in as admin.
> All the default apps that appear on the launcher yield errors like:
> HTTP ERROR 404 Document /db/apps/eXide not found
>
> I have been able to use the package manager to load and run an app
> (TEI-Publisher), but other apps created by me and working in a docker
> instance generate the following again caused by being unable to access /db:
>
>> err:XPST0017 error found while loading .... for module:
>> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line
>> 84, column 13]
>
>
> There is another version of exist (4.7.1) running on port *8080*. Could
> this be the cause of the problem?
>
> Any suggestions about how to fix this?
> Best, HL
>
>
> _______________________________________________
> Exist-open mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
|
|
From: Florian S. <ml-...@fl...> - 2025-02-15 19:43:39
|
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hayim,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">it seems that in certain cases, the
default apps aren't deployed correctly. If I remember correctly, I
ran into a similar issue with a headless setup.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Please try the following (assuming
eXist is installed in /opt/existdb - adapt the paths according to
your setup):<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">First, check if there's a directory
/opt/existdb/autodeploy containing the .xar files for eXide and so
on.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"></div>
<div class="moz-cite-prefix">If the autodeploy directory seems fine,
stop exist-db, and open /opt/existdb/etc/conf.xml in a text
editor.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Search for the following lines:</div>
<pre class="moz-cite-prefix"><trigger class="org.exist.repo.AutoDeploymentTrigger">
<!-- parameter name="ignore-autodeploy-system-property" value="true"/ -->
<!-- parameter name="dir" value="${project.build.outputDirectory}/autodeploy"/ -->
</trigger>
</pre>
<div class="moz-cite-prefix">Uncomment the second "parameter"
element, and change the "value" attribute, setting the full path
to the autodeploy directory. With exist installed in /opt/existdb,
the third line should now be <br>
</div>
<pre class="moz-cite-prefix"><parameter name="dir" value="/opt/existdb/autodeploy" /></pre>
<div class="moz-cite-prefix">Now, restart exist-db and check the
logs for messages regarding autodeployment. If the
AutoDeploymentTrigger doesn't fire, you may have to uncomment the
first parameter element, too.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">HTH</div>
<div class="moz-cite-prefix">Florian<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 14.02.25 um 16:42 schrieb Hayim
Lapin:<br>
</div>
<blockquote type="cite"
cite="mid:CAE=1_O_Y4moZDk=FA4...@ma...">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>Hello,</div>
<div>I just installed eXist 6.3 on an aws linux machine
running on port <b>8081</b>.</div>
<div>The database loads and I can log in as admin. </div>
<div>All the default apps that appear on the launcher
yield errors like:</div>
<div>HTTP ERROR 404 Document /db/apps/eXide not found</div>
<div><br>
</div>
<div>I have been able to use the package manager to load and
run an app (TEI-Publisher), but other apps created by me and
working in a docker instance generate the following again
caused by being unable to access /db:</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">err:XPST0017
error found while loading .... for module:
/db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql
[at line 84, column 13]</blockquote>
<div><br>
</div>
<div>There is another version of exist (4.7.1) running on port
<b>8080</b>. Could this be the cause of the problem?</div>
<div><br>
</div>
<div>Any suggestions about how to fix this?</div>
<div>Best, HL </div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
Exist-open mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Exi...@li...">Exi...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/exist-open">https://lists.sourceforge.net/lists/listinfo/exist-open</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>
|
|
From: Hayim L. <hl...@um...> - 2025-02-14 16:10:19
|
Sorry -- figured it out. Needed to restart *again* On Fri, Feb 14, 2025 at 10:42 AM Hayim Lapin <hl...@um...> wrote: > Hello, > I just installed eXist 6.3 on an aws linux machine running on port *8081*. > The database loads and I can log in as admin. > All the default apps that appear on the launcher yield errors like: > HTTP ERROR 404 Document /db/apps/eXide not found > > I have been able to use the package manager to load and run an app > (TEI-Publisher), but other apps created by me and working in a docker > instance generate the following again caused by being unable to access /db: > >> err:XPST0017 error found while loading .... for module: >> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line >> 84, column 13] > > > There is another version of exist (4.7.1) running on port *8080*. Could > this be the cause of the problem? > > Any suggestions about how to fix this? > Best, HL > |
|
From: Hayim L. <hl...@um...> - 2025-02-14 16:07:13
|
Sorry to sound like a complete idiot, but in fact the errors still exist (I in error tested the local docker instance ...) On Fri, Feb 14, 2025 at 10:42 AM Hayim Lapin <hl...@um...> wrote: > Hello, > I just installed eXist 6.3 on an aws linux machine running on port *8081*. > The database loads and I can log in as admin. > All the default apps that appear on the launcher yield errors like: > HTTP ERROR 404 Document /db/apps/eXide not found > > I have been able to use the package manager to load and run an app > (TEI-Publisher), but other apps created by me and working in a docker > instance generate the following again caused by being unable to access /db: > >> err:XPST0017 error found while loading .... for module: >> /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line >> 84, column 13] > > > There is another version of exist (4.7.1) running on port *8080*. Could > this be the cause of the problem? > > Any suggestions about how to fix this? > Best, HL > |
|
From: Hayim L. <hl...@um...> - 2025-02-14 15:42:44
|
Hello, I just installed eXist 6.3 on an aws linux machine running on port *8081*. The database loads and I can log in as admin. All the default apps that appear on the launcher yield errors like: HTTP ERROR 404 Document /db/apps/eXide not found I have been able to use the package manager to load and run an app (TEI-Publisher), but other apps created by me and working in a docker instance generate the following again caused by being unable to access /db: > err:XPST0017 error found while loading .... for module: > /db/system/repo/tei-publisher-lib-4.0.1/content/tei-functions.xql [at line > 84, column 13] There is another version of exist (4.7.1) running on port *8080*. Could this be the cause of the problem? Any suggestions about how to fix this? Best, HL |
|
From: Craig B. <cra...@ma...> - 2025-02-01 12:51:45
|
> On Jan 31, 2025, at 3:04 PM, Craig Berry via Exist-open <exi...@li...> wrote:
>
>
> -----
> Cannot compile xquery: exerr:ERROR error found while loading module console: Cannot find module class from EXPath repository: org.exist.console.xquery.ConsoleModule
> -----
Still don't know why it was necessary, but I solved this by uninstalling and reinstalling Monex.
________________________________________
Craig A. Berry
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
|
|
From: Craig B. <cra...@ma...> - 2025-01-31 21:05:15
|
I tried eXist 6.3.0 but cannot use it be because things I depend on use modules with location hints and I get the XQST0059 error as described here: https://github.com/eXist-db/exist/issues/5530 So, I thought, since 6.2.0 and 6.3.0 are binary compatible, I'd just downgrade to 6.2.0 and keep the same data directory and be back where I was. I did that but now it can't find the console module using an import statement that's worked for years. This XQuery: ----- xquery version "3.1"; import module namespace console="http://exist-db.org/xquery/console" at "java:org.exist.console.xquery.ConsoleModule"; let $x := console:log('got here') return $x ----- throws this error: ----- Cannot compile xquery: err:XPST0081 Invalid qname console:log. No namespace defined for prefix console. QName is invalid: INVALID_PREFIX [at line 3, column 11] ----- If I remove the location hint I then get: ----- Cannot compile xquery: exerr:ERROR error found while loading module console: Cannot find module class from EXPath repository: org.exist.console.xquery.ConsoleModule ----- The most relevant bits of the stack dump in the log seem to be: Caused by: java.lang.ClassNotFoundException: org.exist.console.xquery.ConsoleModule at java.net.URLClassLoader.findClass(URLClassLoader.java:445) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:592) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?] at java.lang.Class.forName0(Native Method) ~[?:?] at java.lang.Class.forName(Class.java:467) ~[?:?] at org.exist.repo.ExistRepository.getModule(ExistRepository.java:169) ~[exist-core-6.2.0.jar:6.2.0] at org.exist.repo.ExistRepository.resolveJavaModule(ExistRepository.java:155) ~[exist-core-6.2.0.jar:6.2.0] at org.exist.xquery.XQueryContext.resolveInEXPathRepository(XQueryContext.java:579) ~[exist-core-6.2.0.jar:6.2.0] Is there a way to (re)acquire the console module in eXist 6.2.0? This is on Java 17, Mac OS X 15.3 x86_64. ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
|
From: Murray, G. <gre...@pt...> - 2025-01-09 04:48:04
|
Hello, I’m attempting to create my first RESTXQ web application. I’m unable to figure out how to make use of static files such as images, CSS, and JavaScript files in a RESTXQ context in eXist. Where should such files reside on the filesystem, and how are they referenced in relative URLs? For example, let’s say I’ve got my XQuery modules in /db/apps/my-app/ in which controller.xqm acts as the MVC controller and contains RESTXQ resource functions. Meanwhile the directory /db/apps/my-app/css/ contains CSS files. Other XQuery modules contain MVC views that return HTML to the browser. When including a CSS file in the HTML <head>, what path should be used to refer to a CSS file? I was assuming that something like <link type="text/css" rel="stylesheet" href="css/my.css"/> would suffice, since it is relative to the location of controller.xqm, but that seems to be incorrect. Thanks, Greg |
|
From: Craig B. <cra...@ma...> - 2025-01-08 17:10:49
|
> On Jan 8, 2025, at 9:03 AM, Joe Wicentowski <jo...@GM...> wrote: > > Hi Craig, > > Occasionally the exist-db.org server experiences heavy load and becomes unavailable for a short time. We have a monitoring service that reports such outages and their resolutions. (I believe the one you experienced has now been resolved.) Outages are sent to the eXist-db.org Slack's #integrations channel. > > The monitoring service provides a public status page that you can check if you're ever wondering the current status: > > https://exist-db.betteruptime.com/ That's good to know, thanks. According to that all exist.org services were down for 5 hours yesterday, which squares with what I observed. ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
|
From: Joe W. <jo...@gm...> - 2025-01-08 16:31:46
|
Hi Demian, Yes, your URL is the landing page for the public-repo app. The link Craig referenced is one of the app's API endpoints. Joe On Wed, Jan 8, 2025 at 11:01 AM Demian Hauptle <dem...@gm...> wrote: > shouldn't it be https://exist-db.org/exist/apps/public-repo/? > > *Demian Hauptle* > *Mobile & Whatsapp: +27 71 462 6937* > dem...@gm... > LinkedIn <http://za.linkedin.com/in/demianhauptle/> > > > > > On Wed, 8 Jan 2025 at 16:53, Craig Berry via Exist-open < > exi...@li...> wrote: > >> I'm currently get 503, service unavailable from < >> https://exist-db.org/exist/apps/public-repo/find>. Is this a known >> problem? >> >> ________________________________________ >> Craig A. Berry >> >> "... getting out of a sonnet is much more >> difficult than getting in." >> Brad Leithauser >> >> >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Demian H. <dem...@gm...> - 2025-01-08 15:18:37
|
shouldn't it be https://exist-db.org/exist/apps/public-repo/? *Demian Hauptle* *Mobile & Whatsapp: +27 71 462 6937* dem...@gm... LinkedIn <http://za.linkedin.com/in/demianhauptle/> On Wed, 8 Jan 2025 at 16:53, Craig Berry via Exist-open < exi...@li...> wrote: > I'm currently get 503, service unavailable from < > https://exist-db.org/exist/apps/public-repo/find>. Is this a known > problem? > > ________________________________________ > Craig A. Berry > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Joe W. <jo...@gm...> - 2025-01-08 15:04:06
|
Hi Craig, Occasionally the exist-db.org server experiences heavy load and becomes unavailable for a short time. We have a monitoring service that reports such outages and their resolutions. (I believe the one you experienced has now been resolved.) Outages are sent to the eXist-db.org Slack's #integrations channel. The monitoring service provides a public status page that you can check if you're ever wondering the current status: https://exist-db.betteruptime.com/ Joe On Wed, Jan 8, 2025 at 9:53 AM Craig Berry via Exist-open < exi...@li...> wrote: > I'm currently get 503, service unavailable from < > https://exist-db.org/exist/apps/public-repo/find>. Is this a known > problem? > > ________________________________________ > Craig A. Berry > > "... getting out of a sonnet is much more > difficult than getting in." > Brad Leithauser > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
|
From: Craig B. <cra...@ma...> - 2025-01-07 15:21:09
|
I'm currently get 503, service unavailable from <https://exist-db.org/exist/apps/public-repo/find>. Is this a known problem? ________________________________________ Craig A. Berry "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser |
|
From: Irene V. <ire...@pa...> - 2024-12-12 11:24:22
|
Thank you very much, it was this! In the meantime I was also suggested to look at this https://github.com/eXist-db/documentation/issues/385, so I copy it here in case it may be helpful to others too. Thanks again, Irene > On 11.12.2024 11:17 CET Dannes Wessels <di...@ex...> wrote: > > > > Hi, > > I think you need to register the jar in EXIST_HOME/etc/launcher.xml > > Cheers > > Dannes > > > > > On 4 Dec 2024, at 12:55, Irene Vagionakis <ire...@pa...bh> wrote: > > > > > > > Hi there! > > > > I am trying to add a custom Lucene analyzer that behaves like the WhitespaceAnalyzer concerning tokenization and (lack of) stemming, but that is also case-insensitive (basically the same of https://sourceforge.net/p/exist/mailman/message/35188378/). > > > > I followed what suggested in the post thread above, that is writing the custom analyzer, compiling its class as JAR and saving it in $EXIST_HOME/lib/user, but it is not working. I tried also putting it in the same folder of the other Lucene JAR files, but the same. > > > > Since both my Java/Lucene and eXist-db knowledge are quite poor, I am struggling to figure out whether the problem concerns my code or has to do with eXist-db itself. > > > > This is my custom analyzer code: > > > > package org.custom; > > import org.apache.lucene.analysis.Analyzer; > > import org.apache.lucene.analysis.TokenStream; > > import org.apache.lucene.analysis.core.LowerCaseFilter; > > import org.apache.lucene.analysis.core.WhitespaceTokenizer; > > public class CaseInsensitiveWhitespaceAnalyzer extends Analyzer { > > @Override > > protected TokenStreamComponents createComponents(String fieldName) { > > final WhitespaceTokenizer source = new WhitespaceTokenizer(); > > final TokenStream filter = new LowerCaseFilter(source); > > return new TokenStreamComponents(source, filter); > > } > > } > > > > And this is how I reference to it in collection.xconf: > > <analyzer id="custom" class="org.custom.CaseInsensitiveWhitespaceAnalyzer"/> > > > > I also tested the analyzer outside eXist-db with the following and it returned the expected tokens: > > > > import org.apache.lucene.analysis.Analyzer; > > import org.apache.lucene.analysis.TokenStream; > > import org.apache.lucene.analysis.tokenattributes.CharTermAttribute; > > import org.custom.CaseInsensitiveWhitespaceAnalyzer; > > import java.io.IOException; > > import java.io.StringReader; > > public class TestAnalyzer { > > public static void main(String[] args) throws IOException { > > String text = "Lucene is a Simple1 123 5% _test - Yet Powerful - Java Based Search Library. I love IT!"; > > Analyzer analyzer = new CaseInsensitiveWhitespaceAnalyzer(); > > try (TokenStream tokenStream = analyzer.tokenStream("field", new StringReader(text))) { > > CharTermAttribute charTermAttribute = tokenStream.addAttribute(CharTermAttribute.class); > > tokenStream.reset(); > > while (tokenStream.incrementToken()) { > > System.out.println(charTermAttribute.toString()); > > } > > tokenStream.end(); > > } > > } > > } > > > > What am I doing wrong? Any suggestions/hints will be highly appreciated :) > > > > Thanks, > > Irene > > _______________________________________________ > > Exist-open mailing list > > Exi...@li... > > https://lists.sourceforge.net/lists/listinfo/exist-open > > > |
602 messages has been excluded from this view by a project administrator.
