You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(22) |
Nov
(85) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(47) |
Feb
(127) |
Mar
(268) |
Apr
(78) |
May
(47) |
Jun
(38) |
Jul
(131) |
Aug
(221) |
Sep
(187) |
Oct
(54) |
Nov
(111) |
Dec
(84) |
2011 |
Jan
(152) |
Feb
(106) |
Mar
(94) |
Apr
(90) |
May
(53) |
Jun
(20) |
Jul
(24) |
Aug
(37) |
Sep
(32) |
Oct
(70) |
Nov
(22) |
Dec
(15) |
2012 |
Jan
(33) |
Feb
(110) |
Mar
(24) |
Apr
(1) |
May
(11) |
Jun
(8) |
Jul
(12) |
Aug
(37) |
Sep
(39) |
Oct
(81) |
Nov
(38) |
Dec
(50) |
2013 |
Jan
(23) |
Feb
(53) |
Mar
(23) |
Apr
(5) |
May
(19) |
Jun
(16) |
Jul
(16) |
Aug
(9) |
Sep
(21) |
Oct
(1) |
Nov
(2) |
Dec
(8) |
2014 |
Jan
(16) |
Feb
(6) |
Mar
(27) |
Apr
(1) |
May
(10) |
Jun
(1) |
Jul
(4) |
Aug
(10) |
Sep
(19) |
Oct
(22) |
Nov
(4) |
Dec
(6) |
2015 |
Jan
(3) |
Feb
(6) |
Mar
(9) |
Apr
|
May
(11) |
Jun
(23) |
Jul
(14) |
Aug
(10) |
Sep
(10) |
Oct
(9) |
Nov
(18) |
Dec
(4) |
2016 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(15) |
Jun
(2) |
Jul
(8) |
Aug
(2) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
(12) |
Mar
(22) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(2) |
Nov
|
Dec
|
2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(19) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Frederike N. <fre...@bb...> - 2022-06-17 15:19:08
|
Hello again, in the meantime a colleague pointed me to https://github.com/eXist-db/eXide/issues/323 - It would be helpful if the documentation could be adapted as the last comment says. Best wishes, Frederike Am 2022-06-17 16:08, schrieb Frederike Neuber: > Hello everyone, > > I am using exist 5.3.1 and have noticed that you can no longer create > apps in exide via "Application/New Application" as before. The option > seems simply missing. Is there a reason for this or how can I create > new apps now? In the documentation, the procedure is still described > with choosing "New Application" via exide. > > Many thanks and best wishes, > Frederike > > -- > -- > > Dr. Frederike Neuber > > Berlin-Brandenburgische Akademie der Wissenschaften > TELOTA - Koordination Digital Humanities (http://www.bbaw.de/telota) > Jean Paul-Briefedition (https://www.jeanpaul-edition.de) > > Kontakt: > Jägerstraße 22/23, 10117 Berlin, Raum 458 > Telefon: +49 (0)30 20370 395 [derzeit nur per e-mail erreichbar!] > Email: fre...@bb... > > - - - - > > Institut für Dokumentologie und Editorik (https://www.i-d-e.de/) > RIDE - A review journal for digital editions and resources (Managing > Editor, https://ride.i-d-e.de/) -- -- Dr. Frederike Neuber Berlin-Brandenburgische Akademie der Wissenschaften TELOTA - Koordination Digital Humanities (http://www.bbaw.de/telota) Jean Paul-Briefedition (https://www.jeanpaul-edition.de) Kontakt: Jägerstraße 22/23, 10117 Berlin, Raum 458 Telefon: +49 (0)30 20370 395 [derzeit nur per e-mail erreichbar!] Email: fre...@bb... - - - - Institut für Dokumentologie und Editorik (https://www.i-d-e.de/) RIDE - A review journal for digital editions and resources (Managing Editor, https://ride.i-d-e.de/) |
From: Frederike N. <fre...@bb...> - 2022-06-17 14:08:49
|
Hello everyone, I am using exist 5.3.1 and have noticed that you can no longer create apps in exide via "Application/New Application" as before. The option seems simply missing. Is there a reason for this or how can I create new apps now? In the documentation, the procedure is still described with choosing "New Application" via exide. Many thanks and best wishes, Frederike -- -- Dr. Frederike Neuber Berlin-Brandenburgische Akademie der Wissenschaften TELOTA - Koordination Digital Humanities (http://www.bbaw.de/telota) Jean Paul-Briefedition (https://www.jeanpaul-edition.de) Kontakt: Jägerstraße 22/23, 10117 Berlin, Raum 458 Telefon: +49 (0)30 20370 395 [derzeit nur per e-mail erreichbar!] Email: fre...@bb... - - - - Institut für Dokumentologie und Editorik (https://www.i-d-e.de/) RIDE - A review journal for digital editions and resources (Managing Editor, https://ride.i-d-e.de/) |
From: <ml-...@fl...> - 2022-06-09 18:53:02
|
Hi all, i'd like to propose a fix for Issue #16 "cross links to documentation apps are broken" of the eXist-db Function Documentation Browser App (fundocs). I've prepared a small Pull Request [2] and it would be great if someone could take some time to review it. It appears that the issue was caused by the xar packaging process. It included the source version of the page.html template from /src/main/xar-resources/templates instead of the compiled version from /target/classes/templates. I hope it's a small but useful contribution. Florian [1] https://github.com/eXist-db/function-documentation/issues/16 [2] https://github.com/eXist-db/function-documentation/pull/59 |
From: Marcin N. <nie...@gm...> - 2021-10-08 16:13:47
|
Hi, I would like to contribute to eXist by creating fuzzing tests and integrating those with OSS-Fuzzing. My main focus would be on malicious and invalid xml inputs that could break application. Here is instruction how to integrate with OSS-Fuzzing: https://google.github.io/oss-fuzz/ What do you think about this idea ? Best, Marcin |
From: Adam R. <ad...@ex...> - 2018-10-18 09:44:35
|
I am posting this as aside from being interesting, it probably adds support to the argument that we should stick with Java language level 8 for the time being - https://snyk.io/blog/jvm-ecosystem-report-2018 -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Adam R. <ad...@ex...> - 2018-10-16 15:17:19
|
Hi Christian, I think this issue that Erik opened may be relevant - https://github.com/eXist-db/exist/issues/1711#issuecomment-424732059 If so, could you add your comments to that one. On Tue, 16 Oct 2018 at 17:54, Christian Wittern <cwi...@gm...> wrote: > Hi there, > > I just used the newest stable version to install eXist on Ubuntu 16.04. > I used the file eXist-db-setup-4.4.0.jar available from the eXist > homepage. During installation, I entered a password for admin and a data > directory different from the one suggested by the installer. > > When I started eXist (using the desktop icon provided by the installer) > and inspected the values for the data directory, I found that it had in > fact not been set. Setting it through the tray icon did work. I also > found that the admin password had not been set. This caused me a bit of > a headache and several installer attempts, until I realized that it has > not been set and was still empty. > > I hope this feedback helps to improve the installing experience for > future users. > > All the best, > > Christian > > > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Stanislav <st...@gm...> - 2018-10-14 19:34:17
|
Oh come on, Adam. :) May be you should bother to look into the test case added? Question now is 'Is it achieved in a way that is acceptable?' On Sun, Oct 14, 2018, 8:20 PM Adam Retter <ad...@ex...> wrote: > What follows now (I mean PR-wise) ? >> > > Is the PR still just structural changes, or did you manage to complete > what you set out to do? > > -- > Adam Retter > > eXist Core Developer > { United Kingdom / United States } > ad...@ex... > |
From: Adam R. <ad...@ex...> - 2018-10-14 17:21:05
|
> > What follows now (I mean PR-wise) ? > Is the PR still just structural changes, or did you manage to complete what you set out to do? -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Stanislav <st...@gm...> - 2018-10-14 13:04:03
|
Yes. So it was a glitch in AppVeyor in the end. What follows now (I mean PR-wise) ? On Oct 14, 2018 7:09 AM, "Adam Retter" <ad...@ex...> wrote: Stanislav, Your tests appear to be passing on AppVeyor On Fri, 12 Oct 2018 at 16:49, Stanislav <st...@gm...> wrote: > Attached you will find a zip file containing the results (as printed on > stdin and stderr) of running the tests (by `./build.sh test` ) > with OpenJDK10 (or to be more precise OpenJDK 64-Bit Server VM 18.3 (build > 10.0.2+13, mixed mode)) > (Ok, you won't find it attached, as the exist-open mail list does not > allow posting mails containing zip attachments) > In the test log, there are a lot of warnings of the type: > [junit] WARNING: An illegal reflective access operation has occurred > > Specifically, the test that seemed to fail in AppVeyor reports: > [junit] Running org.exist.fluent.QueryServiceTest > [junit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time > elapsed: 6.905 sec > > In particular, this means I can't reproduce what's bothering AppVeyor in > its OpenJDK10 build tests. > Can somebody else reproduce that problem? > I will push a dummy commit to start another IC test cycle. > > Kindly, > /Stanislav > > On Wed, Oct 10, 2018 at 9:47 AM Stanislav <st...@gm...> wrote: > >> I need to install OpenJdk10. >> Later today, perhaps >> >> On Wed, Oct 10, 2018, 6:38 AM Adam Retter <ad...@ex...> wrote: >> >>> It looks to me from the AppVeyor log that the test [junit] Running >>> org.exist.fluent.QueryServiceTest >>> >>> Is failing with an error. Can you test with OpenJdk10 locally on Linux? >>> >>> >>> On Wed, 10 Oct 2018, 08:30 Stanislav, <st...@gm...> wrote: >>> >>>> Mystery of all mysteries: >>>> >>>> All the integration tests pass now with the single exception of the >>>> Java10 OpenJDK amd64 build which failed. >>>> The message is not too informative, it only states: >>>> BUILD FAILED >>>> 3610 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3610>/home/appveyor/projects/exist/build/scripts/junit.xml:329: >>>> The following error occurred while executing this line: >>>> 3611 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3611>/home/appveyor/projects/exist/build/scripts/extensions-build.xml:68: >>>> The following error occurred while executing this line: >>>> 3612 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3612>/home/appveyor/projects/exist/build/scripts/extensions-common.xml:339: >>>> Test org.exist.fluent.QueryServiceTest failed >>>> 3613 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3613> >>>> 3614 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3614>Total >>>> time: 22 minutes 40 seconds >>>> 3615 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3615>Command >>>> exited with code 1 >>>> 3616 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3616>Build >>>> failed >>>> >>>> >>>> On Tue, Oct 9, 2018 at 10:25 PM Stanislav <st...@gm...> wrote: >>>> >>>>> Hi Adam, >>>>> >>>>> Thanks for your reply, but I have figured out what you have said >>>>> myself. >>>>> And nevertheless, the test was failing. >>>>> So, after much ado about nothing (read this 'debugging my and also >>>>> older tests') >>>>> I've figured out (by the grace of God or some other deity that is >>>>> inclined to compassionately aid developers lost in legacy code) >>>>> that the problematic line: >>>>> >>>>> checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); >>>>> >>>>> miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" >>>>> >>>>> 2.5 hours lost. Case closed. Working TC submitted. >>>>> >>>>> :) >>>>> >>>>> >>>>> On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: >>>>> >>>>>> Hi Stanislav, >>>>>> >>>>>> I didn't implement the Lucene index in eXist-db, that would have been >>>>>> Wolfgang Meier. >>>>>> >>>>>> However to try and help you, I just studied that code. It looks to me >>>>>> that the LuceneIndexTest#checkIndex function scans over the entire index, >>>>>> capturing each occurence of one or more provided QNames in the `qn` >>>>>> parameter and then returns the total number of occurrences. >>>>>> >>>>>> Hope that is helpful? >>>>>> >>>>>> On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: >>>>>> >>>>>>> Ok, >>>>>>> may be this is asking for too much. >>>>>>> How about something simpler then -- could someone please add >>>>>>> meaningful documentation to the >>>>>>> >>>>>>> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >>>>>>> >>>>>>> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >>>>>>> >>>>>>> /St. >>>>>>> >>>>>>> >>>>>>> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >>>>>>> >>>>>>>> Ok, >>>>>>>> >>>>>>>> I've crafted a basic test case and it does not work (not sure if it >>>>>>>> is the test that is wrong or the code tested that is wrong) >>>>>>>> Could someone knowledgeable in LuceneIndexTest(s) take a look at >>>>>>>> the test that I just added and tell me why it fails: >>>>>>>> >>>>>>>> >>>>>>>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>>>>>>> >>>>>>>> /St. >>>>>>>> >>>>>>>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>>>>>>> >>>>>>>>> Exactly - as Dom has explained it. >>>>>>>>> (Excuse me for not making myself clearer) >>>>>>>>> >>>>>>>>> /Stanislav >>>>>>>>> >>>>>>>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham < >>>>>>>>> dom...@gm...> wrote: >>>>>>>>> >>>>>>>>>> Dear Adam, >>>>>>>>>> >>>>>>>>>> Thanks for your help. >>>>>>>>>> >>>>>>>>>> The comments in the TEI express the tests >>>>>>>>>> e.g. >>>>>>>>>> <!-- this should get indexed --> >>>>>>>>>> <!-- this should not get indexed -- attribute name ns does not >>>>>>>>>> match --> >>>>>>>>>> >>>>>>>>>> I think the question is how to express that as a test in exist >>>>>>>>>> i.e. that a particular text node has been indexed. >>>>>>>>>> Does that make sense? >>>>>>>>>> >>>>>>>>>> With best wishes, >>>>>>>>>> >>>>>>>>>> Dominic >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Erm... you don't say what you are trying to test exactly? >>>>>>>>>>> >>>>>>>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi guys, >>>>>>>>>>>> >>>>>>>>>>>> A test case is required for the code that implements: >>>>>>>>>>>> "Allow more elaborate XPath expressions in the Lucene index >>>>>>>>>>>> spec in collection.xconf" (#2169) >>>>>>>>>>>> >>>>>>>>>>>> and I have trouble understanding how existing indexing tests do >>>>>>>>>>>> work (and I am a bit tired of reverse-engineering) >>>>>>>>>>>> It would be great if someone familiar with the matter could >>>>>>>>>>>> give me a hand here: >>>>>>>>>>>> >>>>>>>>>>>> *The collection.xconf should be like this:* >>>>>>>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>>>>>>> <!-- Lucene indexes --> >>>>>>>>>>>> <lucene diacritics="no"> >>>>>>>>>>>> <analyzer >>>>>>>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>>>>>>> <text field="title" >>>>>>>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>>>>>>> </lucene> >>>>>>>>>>>> </index> >>>>>>>>>>>> </collection> >>>>>>>>>>>> >>>>>>>>>>>> *While the document being indexed should be like this:* >>>>>>>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>>>>>>> <teiHeader> >>>>>>>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> >>>>>>>>>>>> <!-- this should get indexed --> >>>>>>>>>>>> <title type="longTitle" >>>>>>>>>>>> lang="Sa-Ltn">Cadillac</title> <!-- this should not get indexed -- >>>>>>>>>>>> attribute name ns does not match --> >>>>>>>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> >>>>>>>>>>>> <!-- this should not get indexed -- attribute value does not match --> >>>>>>>>>>>> <title type="longTitle"> >>>>>>>>>>>> Dodge </title> <!-- this should not get indexed -- attribute is entirely >>>>>>>>>>>> missing --> >>>>>>>>>>>> </teiHeader> >>>>>>>>>>>> </TEI> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Kind regards, >>>>>>>>>>>> /St. >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Exist-development mailing list >>>>>>>>>>>> Exi...@li... >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Adam Retter >>>>>>>>>>> >>>>>>>>>>> eXist Core Developer >>>>>>>>>>> { United Kingdom / United States } >>>>>>>>>>> ad...@ex... >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>>> Exist-open mailing list >>>>>>>>>>> Exi...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>> Exist-development mailing list >>>>>>> Exi...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Adam Retter >>>>>> >>>>>> eXist Core Developer >>>>>> { United Kingdom / United States } >>>>>> ad...@ex... >>>>>> >>>>> _______________________________________________ >>>> Exist-development mailing list >>>> Exi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>> >>> -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Adam R. <ad...@ex...> - 2018-10-14 04:09:54
|
Stanislav, Your tests appear to be passing on AppVeyor On Fri, 12 Oct 2018 at 16:49, Stanislav <st...@gm...> wrote: > Attached you will find a zip file containing the results (as printed on > stdin and stderr) of running the tests (by `./build.sh test` ) > with OpenJDK10 (or to be more precise OpenJDK 64-Bit Server VM 18.3 (build > 10.0.2+13, mixed mode)) > (Ok, you won't find it attached, as the exist-open mail list does not > allow posting mails containing zip attachments) > In the test log, there are a lot of warnings of the type: > [junit] WARNING: An illegal reflective access operation has occurred > > Specifically, the test that seemed to fail in AppVeyor reports: > [junit] Running org.exist.fluent.QueryServiceTest > [junit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time > elapsed: 6.905 sec > > In particular, this means I can't reproduce what's bothering AppVeyor in > its OpenJDK10 build tests. > Can somebody else reproduce that problem? > I will push a dummy commit to start another IC test cycle. > > Kindly, > /Stanislav > > On Wed, Oct 10, 2018 at 9:47 AM Stanislav <st...@gm...> wrote: > >> I need to install OpenJdk10. >> Later today, perhaps >> >> On Wed, Oct 10, 2018, 6:38 AM Adam Retter <ad...@ex...> wrote: >> >>> It looks to me from the AppVeyor log that the test [junit] Running >>> org.exist.fluent.QueryServiceTest >>> >>> Is failing with an error. Can you test with OpenJdk10 locally on Linux? >>> >>> >>> On Wed, 10 Oct 2018, 08:30 Stanislav, <st...@gm...> wrote: >>> >>>> Mystery of all mysteries: >>>> >>>> All the integration tests pass now with the single exception of the >>>> Java10 OpenJDK amd64 build which failed. >>>> The message is not too informative, it only states: >>>> BUILD FAILED >>>> 3610 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3610>/home/appveyor/projects/exist/build/scripts/junit.xml:329: >>>> The following error occurred while executing this line: >>>> 3611 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3611>/home/appveyor/projects/exist/build/scripts/extensions-build.xml:68: >>>> The following error occurred while executing this line: >>>> 3612 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3612>/home/appveyor/projects/exist/build/scripts/extensions-common.xml:339: >>>> Test org.exist.fluent.QueryServiceTest failed >>>> 3613 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3613> >>>> 3614 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3614>Total >>>> time: 22 minutes 40 seconds >>>> 3615 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3615>Command >>>> exited with code 1 >>>> 3616 >>>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3616>Build >>>> failed >>>> >>>> >>>> On Tue, Oct 9, 2018 at 10:25 PM Stanislav <st...@gm...> wrote: >>>> >>>>> Hi Adam, >>>>> >>>>> Thanks for your reply, but I have figured out what you have said >>>>> myself. >>>>> And nevertheless, the test was failing. >>>>> So, after much ado about nothing (read this 'debugging my and also >>>>> older tests') >>>>> I've figured out (by the grace of God or some other deity that is >>>>> inclined to compassionately aid developers lost in legacy code) >>>>> that the problematic line: >>>>> >>>>> checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); >>>>> >>>>> miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" >>>>> >>>>> 2.5 hours lost. Case closed. Working TC submitted. >>>>> >>>>> :) >>>>> >>>>> >>>>> On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: >>>>> >>>>>> Hi Stanislav, >>>>>> >>>>>> I didn't implement the Lucene index in eXist-db, that would have been >>>>>> Wolfgang Meier. >>>>>> >>>>>> However to try and help you, I just studied that code. It looks to me >>>>>> that the LuceneIndexTest#checkIndex function scans over the entire index, >>>>>> capturing each occurence of one or more provided QNames in the `qn` >>>>>> parameter and then returns the total number of occurrences. >>>>>> >>>>>> Hope that is helpful? >>>>>> >>>>>> On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: >>>>>> >>>>>>> Ok, >>>>>>> may be this is asking for too much. >>>>>>> How about something simpler then -- could someone please add >>>>>>> meaningful documentation to the >>>>>>> >>>>>>> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >>>>>>> >>>>>>> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >>>>>>> >>>>>>> /St. >>>>>>> >>>>>>> >>>>>>> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >>>>>>> >>>>>>>> Ok, >>>>>>>> >>>>>>>> I've crafted a basic test case and it does not work (not sure if it >>>>>>>> is the test that is wrong or the code tested that is wrong) >>>>>>>> Could someone knowledgeable in LuceneIndexTest(s) take a look at >>>>>>>> the test that I just added and tell me why it fails: >>>>>>>> >>>>>>>> >>>>>>>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>>>>>>> >>>>>>>> /St. >>>>>>>> >>>>>>>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>>>>>>> >>>>>>>>> Exactly - as Dom has explained it. >>>>>>>>> (Excuse me for not making myself clearer) >>>>>>>>> >>>>>>>>> /Stanislav >>>>>>>>> >>>>>>>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham < >>>>>>>>> dom...@gm...> wrote: >>>>>>>>> >>>>>>>>>> Dear Adam, >>>>>>>>>> >>>>>>>>>> Thanks for your help. >>>>>>>>>> >>>>>>>>>> The comments in the TEI express the tests >>>>>>>>>> e.g. >>>>>>>>>> <!-- this should get indexed --> >>>>>>>>>> <!-- this should not get indexed -- attribute name ns does not >>>>>>>>>> match --> >>>>>>>>>> >>>>>>>>>> I think the question is how to express that as a test in exist >>>>>>>>>> i.e. that a particular text node has been indexed. >>>>>>>>>> Does that make sense? >>>>>>>>>> >>>>>>>>>> With best wishes, >>>>>>>>>> >>>>>>>>>> Dominic >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Erm... you don't say what you are trying to test exactly? >>>>>>>>>>> >>>>>>>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi guys, >>>>>>>>>>>> >>>>>>>>>>>> A test case is required for the code that implements: >>>>>>>>>>>> "Allow more elaborate XPath expressions in the Lucene index >>>>>>>>>>>> spec in collection.xconf" (#2169) >>>>>>>>>>>> >>>>>>>>>>>> and I have trouble understanding how existing indexing tests do >>>>>>>>>>>> work (and I am a bit tired of reverse-engineering) >>>>>>>>>>>> It would be great if someone familiar with the matter could >>>>>>>>>>>> give me a hand here: >>>>>>>>>>>> >>>>>>>>>>>> *The collection.xconf should be like this:* >>>>>>>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>>>>>>> <!-- Lucene indexes --> >>>>>>>>>>>> <lucene diacritics="no"> >>>>>>>>>>>> <analyzer >>>>>>>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>>>>>>> <text field="title" >>>>>>>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>>>>>>> </lucene> >>>>>>>>>>>> </index> >>>>>>>>>>>> </collection> >>>>>>>>>>>> >>>>>>>>>>>> *While the document being indexed should be like this:* >>>>>>>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>>>>>>> <teiHeader> >>>>>>>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> >>>>>>>>>>>> <!-- this should get indexed --> >>>>>>>>>>>> <title type="longTitle" >>>>>>>>>>>> lang="Sa-Ltn">Cadillac</title> <!-- this should not get indexed -- >>>>>>>>>>>> attribute name ns does not match --> >>>>>>>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> >>>>>>>>>>>> <!-- this should not get indexed -- attribute value does not match --> >>>>>>>>>>>> <title type="longTitle"> >>>>>>>>>>>> Dodge </title> <!-- this should not get indexed -- attribute is entirely >>>>>>>>>>>> missing --> >>>>>>>>>>>> </teiHeader> >>>>>>>>>>>> </TEI> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Kind regards, >>>>>>>>>>>> /St. >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Exist-development mailing list >>>>>>>>>>>> Exi...@li... >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Adam Retter >>>>>>>>>>> >>>>>>>>>>> eXist Core Developer >>>>>>>>>>> { United Kingdom / United States } >>>>>>>>>>> ad...@ex... >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>>> Exist-open mailing list >>>>>>>>>>> Exi...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>> Exist-development mailing list >>>>>>> Exi...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Adam Retter >>>>>> >>>>>> eXist Core Developer >>>>>> { United Kingdom / United States } >>>>>> ad...@ex... >>>>>> >>>>> _______________________________________________ >>>> Exist-development mailing list >>>> Exi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>> >>> -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Stanislav <st...@gm...> - 2018-10-12 11:49:57
|
Attached you will find a zip file containing the results (as printed on stdin and stderr) of running the tests (by `./build.sh test` ) with OpenJDK10 (or to be more precise OpenJDK 64-Bit Server VM 18.3 (build 10.0.2+13, mixed mode)) (Ok, you won't find it attached, as the exist-open mail list does not allow posting mails containing zip attachments) In the test log, there are a lot of warnings of the type: [junit] WARNING: An illegal reflective access operation has occurred Specifically, the test that seemed to fail in AppVeyor reports: [junit] Running org.exist.fluent.QueryServiceTest [junit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.905 sec In particular, this means I can't reproduce what's bothering AppVeyor in its OpenJDK10 build tests. Can somebody else reproduce that problem? I will push a dummy commit to start another IC test cycle. Kindly, /Stanislav On Wed, Oct 10, 2018 at 9:47 AM Stanislav <st...@gm...> wrote: > I need to install OpenJdk10. > Later today, perhaps > > On Wed, Oct 10, 2018, 6:38 AM Adam Retter <ad...@ex...> wrote: > >> It looks to me from the AppVeyor log that the test [junit] Running >> org.exist.fluent.QueryServiceTest >> >> Is failing with an error. Can you test with OpenJdk10 locally on Linux? >> >> >> On Wed, 10 Oct 2018, 08:30 Stanislav, <st...@gm...> wrote: >> >>> Mystery of all mysteries: >>> >>> All the integration tests pass now with the single exception of the >>> Java10 OpenJDK amd64 build which failed. >>> The message is not too informative, it only states: >>> BUILD FAILED >>> 3610 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3610>/home/appveyor/projects/exist/build/scripts/junit.xml:329: >>> The following error occurred while executing this line: >>> 3611 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3611>/home/appveyor/projects/exist/build/scripts/extensions-build.xml:68: >>> The following error occurred while executing this line: >>> 3612 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3612>/home/appveyor/projects/exist/build/scripts/extensions-common.xml:339: >>> Test org.exist.fluent.QueryServiceTest failed >>> 3613 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3613> >>> 3614 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3614>Total >>> time: 22 minutes 40 seconds >>> 3615 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3615>Command >>> exited with code 1 >>> 3616 >>> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3616>Build >>> failed >>> >>> >>> On Tue, Oct 9, 2018 at 10:25 PM Stanislav <st...@gm...> wrote: >>> >>>> Hi Adam, >>>> >>>> Thanks for your reply, but I have figured out what you have said myself. >>>> And nevertheless, the test was failing. >>>> So, after much ado about nothing (read this 'debugging my and also >>>> older tests') >>>> I've figured out (by the grace of God or some other deity that is >>>> inclined to compassionately aid developers lost in legacy code) >>>> that the problematic line: >>>> >>>> checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); >>>> >>>> miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" >>>> >>>> 2.5 hours lost. Case closed. Working TC submitted. >>>> >>>> :) >>>> >>>> >>>> On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: >>>> >>>>> Hi Stanislav, >>>>> >>>>> I didn't implement the Lucene index in eXist-db, that would have been >>>>> Wolfgang Meier. >>>>> >>>>> However to try and help you, I just studied that code. It looks to me >>>>> that the LuceneIndexTest#checkIndex function scans over the entire index, >>>>> capturing each occurence of one or more provided QNames in the `qn` >>>>> parameter and then returns the total number of occurrences. >>>>> >>>>> Hope that is helpful? >>>>> >>>>> On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: >>>>> >>>>>> Ok, >>>>>> may be this is asking for too much. >>>>>> How about something simpler then -- could someone please add >>>>>> meaningful documentation to the >>>>>> >>>>>> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >>>>>> >>>>>> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >>>>>> >>>>>> /St. >>>>>> >>>>>> >>>>>> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >>>>>> >>>>>>> Ok, >>>>>>> >>>>>>> I've crafted a basic test case and it does not work (not sure if it >>>>>>> is the test that is wrong or the code tested that is wrong) >>>>>>> Could someone knowledgeable in LuceneIndexTest(s) take a look at the >>>>>>> test that I just added and tell me why it fails: >>>>>>> >>>>>>> >>>>>>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>>>>>> >>>>>>> /St. >>>>>>> >>>>>>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>>>>>> >>>>>>>> Exactly - as Dom has explained it. >>>>>>>> (Excuse me for not making myself clearer) >>>>>>>> >>>>>>>> /Stanislav >>>>>>>> >>>>>>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham < >>>>>>>> dom...@gm...> wrote: >>>>>>>> >>>>>>>>> Dear Adam, >>>>>>>>> >>>>>>>>> Thanks for your help. >>>>>>>>> >>>>>>>>> The comments in the TEI express the tests >>>>>>>>> e.g. >>>>>>>>> <!-- this should get indexed --> >>>>>>>>> <!-- this should not get indexed -- attribute name ns does not >>>>>>>>> match --> >>>>>>>>> >>>>>>>>> I think the question is how to express that as a test in exist >>>>>>>>> i.e. that a particular text node has been indexed. >>>>>>>>> Does that make sense? >>>>>>>>> >>>>>>>>> With best wishes, >>>>>>>>> >>>>>>>>> Dominic >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Erm... you don't say what you are trying to test exactly? >>>>>>>>>> >>>>>>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>>>>>>>> >>>>>>>>>>> Hi guys, >>>>>>>>>>> >>>>>>>>>>> A test case is required for the code that implements: >>>>>>>>>>> "Allow more elaborate XPath expressions in the Lucene index spec >>>>>>>>>>> in collection.xconf" (#2169) >>>>>>>>>>> >>>>>>>>>>> and I have trouble understanding how existing indexing tests do >>>>>>>>>>> work (and I am a bit tired of reverse-engineering) >>>>>>>>>>> It would be great if someone familiar with the matter could give >>>>>>>>>>> me a hand here: >>>>>>>>>>> >>>>>>>>>>> *The collection.xconf should be like this:* >>>>>>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>>>>>> <!-- Lucene indexes --> >>>>>>>>>>> <lucene diacritics="no"> >>>>>>>>>>> <analyzer >>>>>>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>>>>>> <text field="title" >>>>>>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>>>>>> </lucene> >>>>>>>>>>> </index> >>>>>>>>>>> </collection> >>>>>>>>>>> >>>>>>>>>>> *While the document being indexed should be like this:* >>>>>>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>>>>>> <teiHeader> >>>>>>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> >>>>>>>>>>> <!-- this should get indexed --> >>>>>>>>>>> <title type="longTitle" >>>>>>>>>>> lang="Sa-Ltn">Cadillac</title> <!-- this should not get indexed -- >>>>>>>>>>> attribute name ns does not match --> >>>>>>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> >>>>>>>>>>> <!-- this should not get indexed -- attribute value does not match --> >>>>>>>>>>> <title type="longTitle"> >>>>>>>>>>> Dodge </title> <!-- this should not get indexed -- attribute is entirely >>>>>>>>>>> missing --> >>>>>>>>>>> </teiHeader> >>>>>>>>>>> </TEI> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Kind regards, >>>>>>>>>>> /St. >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Exist-development mailing list >>>>>>>>>>> Exi...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Adam Retter >>>>>>>>>> >>>>>>>>>> eXist Core Developer >>>>>>>>>> { United Kingdom / United States } >>>>>>>>>> ad...@ex... >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>>> Exist-open mailing list >>>>>>>>>> Exi...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>> Exist-development mailing list >>>>>> Exi...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>> >>>>> >>>>> >>>>> -- >>>>> Adam Retter >>>>> >>>>> eXist Core Developer >>>>> { United Kingdom / United States } >>>>> ad...@ex... >>>>> >>>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >>> >> |
From: Stanislav <st...@gm...> - 2018-10-10 06:47:34
|
I need to install OpenJdk10. Later today, perhaps On Wed, Oct 10, 2018, 6:38 AM Adam Retter <ad...@ex...> wrote: > It looks to me from the AppVeyor log that the test [junit] Running > org.exist.fluent.QueryServiceTest > > Is failing with an error. Can you test with OpenJdk10 locally on Linux? > > > On Wed, 10 Oct 2018, 08:30 Stanislav, <st...@gm...> wrote: > >> Mystery of all mysteries: >> >> All the integration tests pass now with the single exception of the >> Java10 OpenJDK amd64 build which failed. >> The message is not too informative, it only states: >> BUILD FAILED >> 3610 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3610>/home/appveyor/projects/exist/build/scripts/junit.xml:329: >> The following error occurred while executing this line: >> 3611 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3611>/home/appveyor/projects/exist/build/scripts/extensions-build.xml:68: >> The following error occurred while executing this line: >> 3612 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3612>/home/appveyor/projects/exist/build/scripts/extensions-common.xml:339: >> Test org.exist.fluent.QueryServiceTest failed >> 3613 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3613> >> 3614 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3614>Total >> time: 22 minutes 40 seconds >> 3615 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3615>Command >> exited with code 1 >> 3616 >> <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3616>Build >> failed >> >> >> On Tue, Oct 9, 2018 at 10:25 PM Stanislav <st...@gm...> wrote: >> >>> Hi Adam, >>> >>> Thanks for your reply, but I have figured out what you have said myself. >>> And nevertheless, the test was failing. >>> So, after much ado about nothing (read this 'debugging my and also older >>> tests') >>> I've figured out (by the grace of God or some other deity that is >>> inclined to compassionately aid developers lost in legacy code) >>> that the problematic line: >>> >>> checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); >>> >>> miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" >>> >>> 2.5 hours lost. Case closed. Working TC submitted. >>> >>> :) >>> >>> >>> On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: >>> >>>> Hi Stanislav, >>>> >>>> I didn't implement the Lucene index in eXist-db, that would have been >>>> Wolfgang Meier. >>>> >>>> However to try and help you, I just studied that code. It looks to me >>>> that the LuceneIndexTest#checkIndex function scans over the entire index, >>>> capturing each occurence of one or more provided QNames in the `qn` >>>> parameter and then returns the total number of occurrences. >>>> >>>> Hope that is helpful? >>>> >>>> On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: >>>> >>>>> Ok, >>>>> may be this is asking for too much. >>>>> How about something simpler then -- could someone please add >>>>> meaningful documentation to the >>>>> >>>>> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >>>>> >>>>> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >>>>> >>>>> /St. >>>>> >>>>> >>>>> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >>>>> >>>>>> Ok, >>>>>> >>>>>> I've crafted a basic test case and it does not work (not sure if it >>>>>> is the test that is wrong or the code tested that is wrong) >>>>>> Could someone knowledgeable in LuceneIndexTest(s) take a look at the >>>>>> test that I just added and tell me why it fails: >>>>>> >>>>>> >>>>>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>>>>> >>>>>> /St. >>>>>> >>>>>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>>>>> >>>>>>> Exactly - as Dom has explained it. >>>>>>> (Excuse me for not making myself clearer) >>>>>>> >>>>>>> /Stanislav >>>>>>> >>>>>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> >>>>>>> wrote: >>>>>>> >>>>>>>> Dear Adam, >>>>>>>> >>>>>>>> Thanks for your help. >>>>>>>> >>>>>>>> The comments in the TEI express the tests >>>>>>>> e.g. >>>>>>>> <!-- this should get indexed --> >>>>>>>> <!-- this should not get indexed -- attribute name ns does not >>>>>>>> match --> >>>>>>>> >>>>>>>> I think the question is how to express that as a test in exist i.e. >>>>>>>> that a particular text node has been indexed. >>>>>>>> Does that make sense? >>>>>>>> >>>>>>>> With best wishes, >>>>>>>> >>>>>>>> Dominic >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> Erm... you don't say what you are trying to test exactly? >>>>>>>>> >>>>>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>>>>>>> >>>>>>>>>> Hi guys, >>>>>>>>>> >>>>>>>>>> A test case is required for the code that implements: >>>>>>>>>> "Allow more elaborate XPath expressions in the Lucene index spec >>>>>>>>>> in collection.xconf" (#2169) >>>>>>>>>> >>>>>>>>>> and I have trouble understanding how existing indexing tests do >>>>>>>>>> work (and I am a bit tired of reverse-engineering) >>>>>>>>>> It would be great if someone familiar with the matter could give >>>>>>>>>> me a hand here: >>>>>>>>>> >>>>>>>>>> *The collection.xconf should be like this:* >>>>>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>>>>> <!-- Lucene indexes --> >>>>>>>>>> <lucene diacritics="no"> >>>>>>>>>> <analyzer >>>>>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>>>>> <text field="title" >>>>>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>>>>> </lucene> >>>>>>>>>> </index> >>>>>>>>>> </collection> >>>>>>>>>> >>>>>>>>>> *While the document being indexed should be like this:* >>>>>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>>>>> <teiHeader> >>>>>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> >>>>>>>>>> <!-- this should get indexed --> >>>>>>>>>> <title type="longTitle" >>>>>>>>>> lang="Sa-Ltn">Cadillac</title> <!-- this should not get indexed -- >>>>>>>>>> attribute name ns does not match --> >>>>>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> >>>>>>>>>> <!-- this should not get indexed -- attribute value does not match --> >>>>>>>>>> <title type="longTitle"> >>>>>>>>>> Dodge </title> <!-- this should not get indexed -- attribute is entirely >>>>>>>>>> missing --> >>>>>>>>>> </teiHeader> >>>>>>>>>> </TEI> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Kind regards, >>>>>>>>>> /St. >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Exist-development mailing list >>>>>>>>>> Exi...@li... >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Adam Retter >>>>>>>>> >>>>>>>>> eXist Core Developer >>>>>>>>> { United Kingdom / United States } >>>>>>>>> ad...@ex... >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>>> Exist-open mailing list >>>>>>>>> Exi...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>>>>> >>>>>>>> _______________________________________________ >>>>> Exist-development mailing list >>>>> Exi...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>> >>>> >>>> >>>> -- >>>> Adam Retter >>>> >>>> eXist Core Developer >>>> { United Kingdom / United States } >>>> ad...@ex... >>>> >>> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> > |
From: Adam R. <ad...@ex...> - 2018-10-10 03:38:43
|
It looks to me from the AppVeyor log that the test [junit] Running org.exist.fluent.QueryServiceTest Is failing with an error. Can you test with OpenJdk10 locally on Linux? On Wed, 10 Oct 2018, 08:30 Stanislav, <st...@gm...> wrote: > Mystery of all mysteries: > > All the integration tests pass now with the single exception of the Java10 > OpenJDK amd64 build which failed. > The message is not too informative, it only states: > BUILD FAILED > 3610 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3610>/home/appveyor/projects/exist/build/scripts/junit.xml:329: > The following error occurred while executing this line: > 3611 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3611>/home/appveyor/projects/exist/build/scripts/extensions-build.xml:68: > The following error occurred while executing this line: > 3612 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3612>/home/appveyor/projects/exist/build/scripts/extensions-common.xml:339: > Test org.exist.fluent.QueryServiceTest failed > 3613 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3613> > 3614 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3614>Total > time: 22 minutes 40 seconds > 3615 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3615>Command > exited with code 1 > 3616 > <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3616>Build > failed > > > On Tue, Oct 9, 2018 at 10:25 PM Stanislav <st...@gm...> wrote: > >> Hi Adam, >> >> Thanks for your reply, but I have figured out what you have said myself. >> And nevertheless, the test was failing. >> So, after much ado about nothing (read this 'debugging my and also older >> tests') >> I've figured out (by the grace of God or some other deity that is >> inclined to compassionately aid developers lost in legacy code) >> that the problematic line: >> >> checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); >> >> miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" >> >> 2.5 hours lost. Case closed. Working TC submitted. >> >> :) >> >> >> On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: >> >>> Hi Stanislav, >>> >>> I didn't implement the Lucene index in eXist-db, that would have been >>> Wolfgang Meier. >>> >>> However to try and help you, I just studied that code. It looks to me >>> that the LuceneIndexTest#checkIndex function scans over the entire index, >>> capturing each occurence of one or more provided QNames in the `qn` >>> parameter and then returns the total number of occurrences. >>> >>> Hope that is helpful? >>> >>> On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: >>> >>>> Ok, >>>> may be this is asking for too much. >>>> How about something simpler then -- could someone please add meaningful >>>> documentation to the >>>> >>>> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >>>> >>>> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >>>> >>>> /St. >>>> >>>> >>>> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >>>> >>>>> Ok, >>>>> >>>>> I've crafted a basic test case and it does not work (not sure if it is >>>>> the test that is wrong or the code tested that is wrong) >>>>> Could someone knowledgeable in LuceneIndexTest(s) take a look at the >>>>> test that I just added and tell me why it fails: >>>>> >>>>> >>>>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>>>> >>>>> /St. >>>>> >>>>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>>>> >>>>>> Exactly - as Dom has explained it. >>>>>> (Excuse me for not making myself clearer) >>>>>> >>>>>> /Stanislav >>>>>> >>>>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> >>>>>> wrote: >>>>>> >>>>>>> Dear Adam, >>>>>>> >>>>>>> Thanks for your help. >>>>>>> >>>>>>> The comments in the TEI express the tests >>>>>>> e.g. >>>>>>> <!-- this should get indexed --> >>>>>>> <!-- this should not get indexed -- attribute name ns does not match >>>>>>> --> >>>>>>> >>>>>>> I think the question is how to express that as a test in exist i.e. >>>>>>> that a particular text node has been indexed. >>>>>>> Does that make sense? >>>>>>> >>>>>>> With best wishes, >>>>>>> >>>>>>> Dominic >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >>>>>>> >>>>>>>> >>>>>>>> Erm... you don't say what you are trying to test exactly? >>>>>>>> >>>>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>>>>>> >>>>>>>>> Hi guys, >>>>>>>>> >>>>>>>>> A test case is required for the code that implements: >>>>>>>>> "Allow more elaborate XPath expressions in the Lucene index spec >>>>>>>>> in collection.xconf" (#2169) >>>>>>>>> >>>>>>>>> and I have trouble understanding how existing indexing tests do >>>>>>>>> work (and I am a bit tired of reverse-engineering) >>>>>>>>> It would be great if someone familiar with the matter could give >>>>>>>>> me a hand here: >>>>>>>>> >>>>>>>>> *The collection.xconf should be like this:* >>>>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>>>> <!-- Lucene indexes --> >>>>>>>>> <lucene diacritics="no"> >>>>>>>>> <analyzer >>>>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>>>> <text field="title" >>>>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>>>> </lucene> >>>>>>>>> </index> >>>>>>>>> </collection> >>>>>>>>> >>>>>>>>> *While the document being indexed should be like this:* >>>>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>>>> <teiHeader> >>>>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- >>>>>>>>> this should get indexed --> >>>>>>>>> <title type="longTitle" >>>>>>>>> lang="Sa-Ltn">Cadillac</title> <!-- this should not get indexed -- >>>>>>>>> attribute name ns does not match --> >>>>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> >>>>>>>>> <!-- this should not get indexed -- attribute value does not match --> >>>>>>>>> <title type="longTitle"> Dodge >>>>>>>>> </title> <!-- this should not get indexed -- attribute is entirely missing >>>>>>>>> --> >>>>>>>>> </teiHeader> >>>>>>>>> </TEI> >>>>>>>>> >>>>>>>>> >>>>>>>>> Kind regards, >>>>>>>>> /St. >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Exist-development mailing list >>>>>>>>> Exi...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Adam Retter >>>>>>>> >>>>>>>> eXist Core Developer >>>>>>>> { United Kingdom / United States } >>>>>>>> ad...@ex... >>>>>>>> >>>>>>> _______________________________________________ >>>>>>>> Exist-open mailing list >>>>>>>> Exi...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>>>> >>>>>>> _______________________________________________ >>>> Exist-development mailing list >>>> Exi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>> >>> >>> >>> -- >>> Adam Retter >>> >>> eXist Core Developer >>> { United Kingdom / United States } >>> ad...@ex... >>> >> _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > |
From: Stanislav <st...@gm...> - 2018-10-10 03:30:01
|
Mystery of all mysteries: All the integration tests pass now with the single exception of the Java10 OpenJDK amd64 build which failed. The message is not too informative, it only states: BUILD FAILED 3610 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3610>/home/appveyor/projects/exist/build/scripts/junit.xml:329: The following error occurred while executing this line: 3611 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3611>/home/appveyor/projects/exist/build/scripts/extensions-build.xml:68: The following error occurred while executing this line: 3612 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3612>/home/appveyor/projects/exist/build/scripts/extensions-common.xml:339: Test org.exist.fluent.QueryServiceTest failed 3613 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3613> 3614 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3614>Total time: 22 minutes 40 seconds 3615 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3615>Command exited with code 1 3616 <https://ci.appveyor.com/project/AdamRetter/exist/builds/19381496/job/gtukpcxvq0wfftrs#L3616>Build failed On Tue, Oct 9, 2018 at 10:25 PM Stanislav <st...@gm...> wrote: > Hi Adam, > > Thanks for your reply, but I have figured out what you have said myself. > And nevertheless, the test was failing. > So, after much ado about nothing (read this 'debugging my and also older > tests') > I've figured out (by the grace of God or some other deity that is inclined > to compassionately aid developers lost in legacy code) > that the problematic line: > > checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); > > miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" > > 2.5 hours lost. Case closed. Working TC submitted. > > :) > > > On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: > >> Hi Stanislav, >> >> I didn't implement the Lucene index in eXist-db, that would have been >> Wolfgang Meier. >> >> However to try and help you, I just studied that code. It looks to me >> that the LuceneIndexTest#checkIndex function scans over the entire index, >> capturing each occurence of one or more provided QNames in the `qn` >> parameter and then returns the total number of occurrences. >> >> Hope that is helpful? >> >> On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: >> >>> Ok, >>> may be this is asking for too much. >>> How about something simpler then -- could someone please add meaningful >>> documentation to the >>> >>> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >>> >>> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >>> >>> /St. >>> >>> >>> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >>> >>>> Ok, >>>> >>>> I've crafted a basic test case and it does not work (not sure if it is >>>> the test that is wrong or the code tested that is wrong) >>>> Could someone knowledgeable in LuceneIndexTest(s) take a look at the >>>> test that I just added and tell me why it fails: >>>> >>>> >>>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>>> >>>> /St. >>>> >>>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>>> >>>>> Exactly - as Dom has explained it. >>>>> (Excuse me for not making myself clearer) >>>>> >>>>> /Stanislav >>>>> >>>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> >>>>> wrote: >>>>> >>>>>> Dear Adam, >>>>>> >>>>>> Thanks for your help. >>>>>> >>>>>> The comments in the TEI express the tests >>>>>> e.g. >>>>>> <!-- this should get indexed --> >>>>>> <!-- this should not get indexed -- attribute name ns does not match >>>>>> --> >>>>>> >>>>>> I think the question is how to express that as a test in exist i.e. >>>>>> that a particular text node has been indexed. >>>>>> Does that make sense? >>>>>> >>>>>> With best wishes, >>>>>> >>>>>> Dominic >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >>>>>> >>>>>>> >>>>>>> Erm... you don't say what you are trying to test exactly? >>>>>>> >>>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>>>>> >>>>>>>> Hi guys, >>>>>>>> >>>>>>>> A test case is required for the code that implements: >>>>>>>> "Allow more elaborate XPath expressions in the Lucene index spec in >>>>>>>> collection.xconf" (#2169) >>>>>>>> >>>>>>>> and I have trouble understanding how existing indexing tests do >>>>>>>> work (and I am a bit tired of reverse-engineering) >>>>>>>> It would be great if someone familiar with the matter could give me >>>>>>>> a hand here: >>>>>>>> >>>>>>>> *The collection.xconf should be like this:* >>>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>>> <!-- Lucene indexes --> >>>>>>>> <lucene diacritics="no"> >>>>>>>> <analyzer >>>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>>> <text field="title" >>>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>>> </lucene> >>>>>>>> </index> >>>>>>>> </collection> >>>>>>>> >>>>>>>> *While the document being indexed should be like this:* >>>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>>> <teiHeader> >>>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- >>>>>>>> this should get indexed --> >>>>>>>> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> >>>>>>>> <!-- this should not get indexed -- attribute name ns does not match --> >>>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> >>>>>>>> <!-- this should not get indexed -- attribute value does not match --> >>>>>>>> <title type="longTitle"> Dodge >>>>>>>> </title> <!-- this should not get indexed -- attribute is entirely missing >>>>>>>> --> >>>>>>>> </teiHeader> >>>>>>>> </TEI> >>>>>>>> >>>>>>>> >>>>>>>> Kind regards, >>>>>>>> /St. >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Exist-development mailing list >>>>>>>> Exi...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Adam Retter >>>>>>> >>>>>>> eXist Core Developer >>>>>>> { United Kingdom / United States } >>>>>>> ad...@ex... >>>>>>> >>>>>> _______________________________________________ >>>>>>> Exist-open mailing list >>>>>>> Exi...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>>> >>>>>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >>> >> >> >> -- >> Adam Retter >> >> eXist Core Developer >> { United Kingdom / United States } >> ad...@ex... >> > |
From: Stanislav <st...@gm...> - 2018-10-09 19:25:29
|
Hi Adam, Thanks for your reply, but I have figured out what you have said myself. And nevertheless, the test was failing. So, after much ado about nothing (read this 'debugging my and also older tests') I've figured out (by the grace of God or some other deity that is inclined to compassionately aid developers lost in legacy code) that the problematic line: checkIndex(docs, broker, new QName[]{new QName("title")}, "Buick", 1); miraculously becomes un-problematic if only I convert "Buick" to all small letters - "buick" 2.5 hours lost. Case closed. Working TC submitted. :) On Mon, Oct 8, 2018 at 10:45 PM Adam Retter <ad...@ex...> wrote: > Hi Stanislav, > > I didn't implement the Lucene index in eXist-db, that would have been > Wolfgang Meier. > > However to try and help you, I just studied that code. It looks to me that > the LuceneIndexTest#checkIndex function scans over the entire index, > capturing each occurence of one or more provided QNames in the `qn` > parameter and then returns the total number of occurrences. > > Hope that is helpful? > > On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: > >> Ok, >> may be this is asking for too much. >> How about something simpler then -- could someone please add meaningful >> documentation to the >> >> private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) >> >> method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? >> >> /St. >> >> >> On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: >> >>> Ok, >>> >>> I've crafted a basic test case and it does not work (not sure if it is >>> the test that is wrong or the code tested that is wrong) >>> Could someone knowledgeable in LuceneIndexTest(s) take a look at the >>> test that I just added and tell me why it fails: >>> >>> >>> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >>> >>> /St. >>> >>> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >>> >>>> Exactly - as Dom has explained it. >>>> (Excuse me for not making myself clearer) >>>> >>>> /Stanislav >>>> >>>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> >>>> wrote: >>>> >>>>> Dear Adam, >>>>> >>>>> Thanks for your help. >>>>> >>>>> The comments in the TEI express the tests >>>>> e.g. >>>>> <!-- this should get indexed --> >>>>> <!-- this should not get indexed -- attribute name ns does not match >>>>> --> >>>>> >>>>> I think the question is how to express that as a test in exist i.e. >>>>> that a particular text node has been indexed. >>>>> Does that make sense? >>>>> >>>>> With best wishes, >>>>> >>>>> Dominic >>>>> >>>>> >>>>> >>>>> >>>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >>>>> >>>>>> >>>>>> Erm... you don't say what you are trying to test exactly? >>>>>> >>>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>>>> >>>>>>> Hi guys, >>>>>>> >>>>>>> A test case is required for the code that implements: >>>>>>> "Allow more elaborate XPath expressions in the Lucene index spec in >>>>>>> collection.xconf" (#2169) >>>>>>> >>>>>>> and I have trouble understanding how existing indexing tests do work >>>>>>> (and I am a bit tired of reverse-engineering) >>>>>>> It would be great if someone familiar with the matter could give me >>>>>>> a hand here: >>>>>>> >>>>>>> *The collection.xconf should be like this:* >>>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>>> <!-- Lucene indexes --> >>>>>>> <lucene diacritics="no"> >>>>>>> <analyzer >>>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>>> <text field="title" >>>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>>> </lucene> >>>>>>> </index> >>>>>>> </collection> >>>>>>> >>>>>>> *While the document being indexed should be like this:* >>>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>>> <teiHeader> >>>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- >>>>>>> this should get indexed --> >>>>>>> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> >>>>>>> <!-- this should not get indexed -- attribute name ns does not match --> >>>>>>> <title type="longTitle" xml:lang="En"> Ford</title> <!-- >>>>>>> this should not get indexed -- attribute value does not match --> >>>>>>> <title type="longTitle"> Dodge >>>>>>> </title> <!-- this should not get indexed -- attribute is entirely missing >>>>>>> --> >>>>>>> </teiHeader> >>>>>>> </TEI> >>>>>>> >>>>>>> >>>>>>> Kind regards, >>>>>>> /St. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Exist-development mailing list >>>>>>> Exi...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Adam Retter >>>>>> >>>>>> eXist Core Developer >>>>>> { United Kingdom / United States } >>>>>> ad...@ex... >>>>>> >>>>> _______________________________________________ >>>>>> Exist-open mailing list >>>>>> Exi...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>>> >>>>> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> > > > -- > Adam Retter > > eXist Core Developer > { United Kingdom / United States } > ad...@ex... > |
From: Adam R. <ad...@ex...> - 2018-10-08 19:45:21
|
Hi Stanislav, I didn't implement the Lucene index in eXist-db, that would have been Wolfgang Meier. However to try and help you, I just studied that code. It looks to me that the LuceneIndexTest#checkIndex function scans over the entire index, capturing each occurence of one or more provided QNames in the `qn` parameter and then returns the total number of occurrences. Hope that is helpful? On Mon, 8 Oct 2018 at 16:51, Stanislav <st...@gm...> wrote: > Ok, > may be this is asking for too much. > How about something simpler then -- could someone please add meaningful > documentation to the > > private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) > > method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? > > /St. > > > On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: > >> Ok, >> >> I've crafted a basic test case and it does not work (not sure if it is >> the test that is wrong or the code tested that is wrong) >> Could someone knowledgeable in LuceneIndexTest(s) take a look at the test >> that I just added and tell me why it fails: >> >> >> https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce >> >> /St. >> >> On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: >> >>> Exactly - as Dom has explained it. >>> (Excuse me for not making myself clearer) >>> >>> /Stanislav >>> >>> On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> >>> wrote: >>> >>>> Dear Adam, >>>> >>>> Thanks for your help. >>>> >>>> The comments in the TEI express the tests >>>> e.g. >>>> <!-- this should get indexed --> >>>> <!-- this should not get indexed -- attribute name ns does not match --> >>>> >>>> I think the question is how to express that as a test in exist i.e. >>>> that a particular text node has been indexed. >>>> Does that make sense? >>>> >>>> With best wishes, >>>> >>>> Dominic >>>> >>>> >>>> >>>> >>>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >>>> >>>>> >>>>> Erm... you don't say what you are trying to test exactly? >>>>> >>>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>>> >>>>>> Hi guys, >>>>>> >>>>>> A test case is required for the code that implements: >>>>>> "Allow more elaborate XPath expressions in the Lucene index spec in >>>>>> collection.xconf" (#2169) >>>>>> >>>>>> and I have trouble understanding how existing indexing tests do work >>>>>> (and I am a bit tired of reverse-engineering) >>>>>> It would be great if someone familiar with the matter could give me a >>>>>> hand here: >>>>>> >>>>>> *The collection.xconf should be like this:* >>>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>>> <!-- Lucene indexes --> >>>>>> <lucene diacritics="no"> >>>>>> <analyzer >>>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>>> <text field="title" >>>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>>> </lucene> >>>>>> </index> >>>>>> </collection> >>>>>> >>>>>> *While the document being indexed should be like this:* >>>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>>> http://relaxng.org/ns/structure/1.0"?> >>>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>>> <teiHeader> >>>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- >>>>>> this should get indexed --> >>>>>> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> >>>>>> <!-- this should not get indexed -- attribute name ns does not match --> >>>>>> <title type="longTitle" xml:lang="En"> Ford</title> <!-- >>>>>> this should not get indexed -- attribute value does not match --> >>>>>> <title type="longTitle"> Dodge >>>>>> </title> <!-- this should not get indexed -- attribute is entirely missing >>>>>> --> >>>>>> </teiHeader> >>>>>> </TEI> >>>>>> >>>>>> >>>>>> Kind regards, >>>>>> /St. >>>>>> >>>>>> _______________________________________________ >>>>>> Exist-development mailing list >>>>>> Exi...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>>> >>>>> >>>>> >>>>> -- >>>>> Adam Retter >>>>> >>>>> eXist Core Developer >>>>> { United Kingdom / United States } >>>>> ad...@ex... >>>>> >>>> _______________________________________________ >>>>> Exist-open mailing list >>>>> Exi...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>>> >>>> _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Stanislav <st...@gm...> - 2018-10-08 11:51:28
|
Ok, may be this is asking for too much. How about something simpler then -- could someone please add meaningful documentation to the private Occurrences[] checkIndex(final DocumentSet docs, final DBBroker broker, final QName[] qn, final String term, final int expected) method in extensions/indexes/lucene/test/src/org/exist/indexing/lucene/LuceneIndexTest.java ? /St. On Fri, Oct 5, 2018 at 5:22 PM Stanislav <st...@gm...> wrote: > Ok, > > I've crafted a basic test case and it does not work (not sure if it is the > test that is wrong or the code tested that is wrong) > Could someone knowledgeable in LuceneIndexTest(s) take a look at the test > that I just added and tell me why it fails: > > > https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce > > /St. > > On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: > >> Exactly - as Dom has explained it. >> (Excuse me for not making myself clearer) >> >> /Stanislav >> >> On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> >> wrote: >> >>> Dear Adam, >>> >>> Thanks for your help. >>> >>> The comments in the TEI express the tests >>> e.g. >>> <!-- this should get indexed --> >>> <!-- this should not get indexed -- attribute name ns does not match --> >>> >>> I think the question is how to express that as a test in exist i.e. that >>> a particular text node has been indexed. >>> Does that make sense? >>> >>> With best wishes, >>> >>> Dominic >>> >>> >>> >>> >>> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >>> >>>> >>>> Erm... you don't say what you are trying to test exactly? >>>> >>>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> A test case is required for the code that implements: >>>>> "Allow more elaborate XPath expressions in the Lucene index spec in >>>>> collection.xconf" (#2169) >>>>> >>>>> and I have trouble understanding how existing indexing tests do work >>>>> (and I am a bit tired of reverse-engineering) >>>>> It would be great if someone familiar with the matter could give me a >>>>> hand here: >>>>> >>>>> *The collection.xconf should be like this:* >>>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>>> <!-- Lucene indexes --> >>>>> <lucene diacritics="no"> >>>>> <analyzer >>>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>>> <text field="title" >>>>> match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> >>>>> </lucene> >>>>> </index> >>>>> </collection> >>>>> >>>>> *While the document being indexed should be like this:* >>>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>>> http://relaxng.org/ns/structure/1.0"?> >>>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>>> <teiHeader> >>>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- >>>>> this should get indexed --> >>>>> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> >>>>> <!-- this should not get indexed -- attribute name ns does not match --> >>>>> <title type="longTitle" xml:lang="En"> Ford</title> <!-- >>>>> this should not get indexed -- attribute value does not match --> >>>>> <title type="longTitle"> Dodge >>>>> </title> <!-- this should not get indexed -- attribute is entirely missing >>>>> --> >>>>> </teiHeader> >>>>> </TEI> >>>>> >>>>> >>>>> Kind regards, >>>>> /St. >>>>> >>>>> _______________________________________________ >>>>> Exist-development mailing list >>>>> Exi...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>>> >>>> >>>> >>>> -- >>>> Adam Retter >>>> >>>> eXist Core Developer >>>> { United Kingdom / United States } >>>> ad...@ex... >>>> >>> _______________________________________________ >>>> Exist-open mailing list >>>> Exi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/exist-open >>>> >>> |
From: Stanislav <st...@gm...> - 2018-10-05 14:23:17
|
Ok, I've crafted a basic test case and it does not work (not sure if it is the test that is wrong or the code tested that is wrong) Could someone knowledgeable in LuceneIndexTest(s) take a look at the test that I just added and tell me why it fails: https://github.com/eXist-db/exist/pull/2169/commits/39896b258b34571e4e264c46e4759b6ed14292ce /St. On Thu, Oct 4, 2018 at 6:43 PM Stanislav <st...@gm...> wrote: > Exactly - as Dom has explained it. > (Excuse me for not making myself clearer) > > /Stanislav > > On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> > wrote: > >> Dear Adam, >> >> Thanks for your help. >> >> The comments in the TEI express the tests >> e.g. >> <!-- this should get indexed --> >> <!-- this should not get indexed -- attribute name ns does not match --> >> >> I think the question is how to express that as a test in exist i.e. that >> a particular text node has been indexed. >> Does that make sense? >> >> With best wishes, >> >> Dominic >> >> >> >> >> On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: >> >>> >>> Erm... you don't say what you are trying to test exactly? >>> >>> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >>> >>>> Hi guys, >>>> >>>> A test case is required for the code that implements: >>>> "Allow more elaborate XPath expressions in the Lucene index spec in >>>> collection.xconf" (#2169) >>>> >>>> and I have trouble understanding how existing indexing tests do work >>>> (and I am a bit tired of reverse-engineering) >>>> It would be great if someone familiar with the matter could give me a >>>> hand here: >>>> >>>> *The collection.xconf should be like this:* >>>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>>> <!-- Lucene indexes --> >>>> <lucene diacritics="no"> >>>> <analyzer >>>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>>> <text field="title" match="//tei:title[@xml:lang='Sa-Ltn']" >>>> boost="2.0"/> >>>> </lucene> >>>> </index> >>>> </collection> >>>> >>>> *While the document being indexed should be like this:* >>>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>>> http://relaxng.org/ns/structure/1.0"?> >>>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>>> <teiHeader> >>>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- this >>>> should get indexed --> >>>> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> >>>> <!-- this should not get indexed -- attribute name ns does not match --> >>>> <title type="longTitle" xml:lang="En"> Ford</title> <!-- >>>> this should not get indexed -- attribute value does not match --> >>>> <title type="longTitle"> Dodge >>>> </title> <!-- this should not get indexed -- attribute is entirely missing >>>> --> >>>> </teiHeader> >>>> </TEI> >>>> >>>> >>>> Kind regards, >>>> /St. >>>> >>>> _______________________________________________ >>>> Exist-development mailing list >>>> Exi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/exist-development >>>> >>> >>> >>> -- >>> Adam Retter >>> >>> eXist Core Developer >>> { United Kingdom / United States } >>> ad...@ex... >>> >> _______________________________________________ >>> Exist-open mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-open >>> >> |
From: Stanislav <st...@gm...> - 2018-10-04 15:43:37
|
Exactly - as Dom has explained it. (Excuse me for not making myself clearer) /Stanislav On Thu, 4 Oct 2018 at 12:43, Dominic Latham <dom...@gm...> wrote: > Dear Adam, > > Thanks for your help. > > The comments in the TEI express the tests > e.g. > <!-- this should get indexed --> > <!-- this should not get indexed -- attribute name ns does not match --> > > I think the question is how to express that as a test in exist i.e. that a > particular text node has been indexed. > Does that make sense? > > With best wishes, > > Dominic > > > > > On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: > >> >> Erm... you don't say what you are trying to test exactly? >> >> On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: >> >>> Hi guys, >>> >>> A test case is required for the code that implements: >>> "Allow more elaborate XPath expressions in the Lucene index spec in >>> collection.xconf" (#2169) >>> >>> and I have trouble understanding how existing indexing tests do work >>> (and I am a bit tired of reverse-engineering) >>> It would be great if someone familiar with the matter could give me a >>> hand here: >>> >>> *The collection.xconf should be like this:* >>> <collection xmlns="http://exist-db.org/collection-config/1.0"> >>> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >>> <!-- Lucene indexes --> >>> <lucene diacritics="no"> >>> <analyzer >>> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >>> <text field="title" match="//tei:title[@xml:lang='Sa-Ltn']" >>> boost="2.0"/> >>> </lucene> >>> </index> >>> </collection> >>> >>> *While the document being indexed should be like this:* >>> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >>> http://relaxng.org/ns/structure/1.0"?> >>> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >>> <teiHeader> >>> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- this >>> should get indexed --> >>> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> <!-- >>> this should not get indexed -- attribute name ns does not match --> >>> <title type="longTitle" xml:lang="En"> Ford</title> <!-- >>> this should not get indexed -- attribute value does not match --> >>> <title type="longTitle"> Dodge >>> </title> <!-- this should not get indexed -- attribute is entirely missing >>> --> >>> </teiHeader> >>> </TEI> >>> >>> >>> Kind regards, >>> /St. >>> >>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >>> >> >> >> -- >> Adam Retter >> >> eXist Core Developer >> { United Kingdom / United States } >> ad...@ex... >> > _______________________________________________ >> Exist-open mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-open >> > |
From: Dominic L. <dom...@gm...> - 2018-10-04 09:43:57
|
Dear Adam, Thanks for your help. The comments in the TEI express the tests e.g. <!-- this should get indexed --> <!-- this should not get indexed -- attribute name ns does not match --> I think the question is how to express that as a test in exist i.e. that a particular text node has been indexed. Does that make sense? With best wishes, Dominic On Wed, 3 Oct 2018 at 09:43, Adam Retter <ad...@ex...> wrote: > > Erm... you don't say what you are trying to test exactly? > > On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: > >> Hi guys, >> >> A test case is required for the code that implements: >> "Allow more elaborate XPath expressions in the Lucene index spec in >> collection.xconf" (#2169) >> >> and I have trouble understanding how existing indexing tests do work (and >> I am a bit tired of reverse-engineering) >> It would be great if someone familiar with the matter could give me a >> hand here: >> >> *The collection.xconf should be like this:* >> <collection xmlns="http://exist-db.org/collection-config/1.0"> >> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> >> <!-- Lucene indexes --> >> <lucene diacritics="no"> >> <analyzer >> class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> >> <text field="title" match="//tei:title[@xml:lang='Sa-Ltn']" >> boost="2.0"/> >> </lucene> >> </index> >> </collection> >> >> *While the document being indexed should be like this:* >> <?xml-model href="../schema/1.0/tei.rng" schematypens=" >> http://relaxng.org/ns/structure/1.0"?> >> <TEI xmlns="http://www.tei-c.org/ns/1.0"> >> <teiHeader> >> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- this >> should get indexed --> >> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> <!-- >> this should not get indexed -- attribute name ns does not match --> >> <title type="longTitle" xml:lang="En"> Ford</title> <!-- this >> should not get indexed -- attribute value does not match --> >> <title type="longTitle"> Dodge >> </title> <!-- this should not get indexed -- attribute is entirely missing >> --> >> </teiHeader> >> </TEI> >> >> >> Kind regards, >> /St. >> >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> > > > -- > Adam Retter > > eXist Core Developer > { United Kingdom / United States } > ad...@ex... > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |
From: Adam R. <ad...@ex...> - 2018-10-03 07:43:24
|
Erm... you don't say what you are trying to test exactly? On Wed, 3 Oct 2018 at 12:59, Stanislav <st...@gm...> wrote: > Hi guys, > > A test case is required for the code that implements: > "Allow more elaborate XPath expressions in the Lucene index spec in > collection.xconf" (#2169) > > and I have trouble understanding how existing indexing tests do work (and > I am a bit tired of reverse-engineering) > It would be great if someone familiar with the matter could give me a hand > here: > > *The collection.xconf should be like this:* > <collection xmlns="http://exist-db.org/collection-config/1.0"> > <index xmlns:tei="http://www.tei-c.org/ns/1.0"> > <!-- Lucene indexes --> > <lucene diacritics="no"> > <analyzer > class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> > <text field="title" match="//tei:title[@xml:lang='Sa-Ltn']" > boost="2.0"/> > </lucene> > </index> > </collection> > > *While the document being indexed should be like this:* > <?xml-model href="../schema/1.0/tei.rng" schematypens=" > http://relaxng.org/ns/structure/1.0"?> > <TEI xmlns="http://www.tei-c.org/ns/1.0"> > <teiHeader> > <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- this > should get indexed --> > <title type="longTitle" lang="Sa-Ltn">Cadillac</title> <!-- > this should not get indexed -- attribute name ns does not match --> > <title type="longTitle" xml:lang="En"> Ford</title> <!-- this > should not get indexed -- attribute value does not match --> > <title type="longTitle"> Dodge > </title> <!-- this should not get indexed -- attribute is entirely missing > --> > </teiHeader> > </TEI> > > > Kind regards, > /St. > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Adam R. <ad...@ex...> - 2018-10-03 07:20:31
|
The name type is not used for all operations. It is only *sometimes* used when we need to know the type of the node. So you cannot rely on it always being set correctly. On Wed, 12 Sep 2018 at 01:49, Stanislav <st...@gm...> wrote: > Hi guys, > > Stanislav here (I am new to this list). > It started with this: > * [Exist-open] Are more elaborate xpath expressions allowed in Lucene's > index config <text match='...'/> > <https://sourceforge.net/p/exist/mailman/message/36392026/>* > > Then I went to clone, build and then debug/trace exist, > and it turned out NodePath and QName are not suited to handle 'more > elaborate xpath expressions' > > I started modifying them (locally). > I introduced (a minimalist) change - namely that QName should honor its > nameType which could be any of { UNKNOWN, ELEMENT, ATTRIBUTE } > and changed QName.compareTo() and .equals() methods to compare also this > field. > Alas, this prevented exist from normal startup as line 214 of > ConfigurationImpl.java consists of: > > Node attr = attrs.getNamedItem("key"); > > which in turn invokes NamedNodeMapImpl.getNamedItem(): > > @Override > public Node getNamedItem(final String name) { > try { > return getNamedItem(new QName(name)); > } catch (final QName.IllegalQNameException e) { > throw new DOMException(DOMException.INVALID_CHARACTER_ERR, "Invalid name"); > } > } > > And the problem is the newly created new QName(name) has its nameType set > (by default) to ELEMENT, > while the one stored in the map is of nameType ATTRIBUTE -- and the newly > modified QName.equals() method discerns between those two, as their > nameType(s) are different. > > I am not sure what would be the right question in this situation, so I > will try with: > How come? > > Kindly, > /Stanislav > > > > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |
From: Stanislav <st...@gm...> - 2018-10-03 06:58:59
|
Hi guys, A test case is required for the code that implements: "Allow more elaborate XPath expressions in the Lucene index spec in collection.xconf" (#2169) and I have trouble understanding how existing indexing tests do work (and I am a bit tired of reverse-engineering) It would be great if someone familiar with the matter could give me a hand here: *The collection.xconf should be like this:* <collection xmlns="http://exist-db.org/collection-config/1.0"> <index xmlns:tei="http://www.tei-c.org/ns/1.0"> <!-- Lucene indexes --> <lucene diacritics="no"> <analyzer class="org.apache.lucene.analysis.standard.StandardAnalyzer"/> <text field="title" match="//tei:title[@xml:lang='Sa-Ltn']" boost="2.0"/> </lucene> </index> </collection> *While the document being indexed should be like this:* <?xml-model href="../schema/1.0/tei.rng" schematypens="http://relaxng. org/ns/structure/1.0"?> <TEI xmlns="http://www.tei-c.org/ns/1.0"> <teiHeader> <title type="longTitle" xml:lang="Sa-Ltn">Buick</title> <!-- this should get indexed --> <title type="longTitle" lang="Sa-Ltn">Cadillac</title> <!-- this should not get indexed -- attribute name ns does not match --> <title type="longTitle" xml:lang="En"> Ford</title> <!-- this should not get indexed -- attribute value does not match --> <title type="longTitle"> Dodge </title> <!-- this should not get indexed -- attribute is entirely missing --> </teiHeader> </TEI> Kind regards, /St. |
From: Christian W. <cwi...@gm...> - 2018-09-27 06:24:48
|
Hi there, I just used the newest stable version to install eXist on Ubuntu 16.04. I used the file eXist-db-setup-4.4.0.jar available from the eXist homepage. During installation, I entered a password for admin and a data directory different from the one suggested by the installer. When I started eXist (using the desktop icon provided by the installer) and inspected the values for the data directory, I found that it had in fact not been set. Setting it through the tray icon did work. I also found that the admin password had not been set. This caused me a bit of a headache and several installer attempts, until I realized that it has not been set and was still empty. I hope this feedback helps to improve the installing experience for future users. All the best, Christian |
From: Adam R. <ad...@ex...> - 2018-09-26 15:45:28
|
I normally run just the tests I need in IntelliJ directly, or if I must do it from Ant, then I just add a new temporary and minimal target to build/scripts/junit.xml On Wed, 26 Sep 2018 at 21:43, Stanislav <st...@gm...> wrote: > Hi guys, > > I know that invoking > *./build.sh test* > > runs all test, > but is there a way to run only a specific group of tests ? > > (Asking this, because on my laptop it takes ~28 min. to run the complete > test suite) > > /Stanislav > > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |