> Hello Willem, > > This indeed seems quite wrong! Do you have an example for me > of the delete webdav call and the add? > > And, perhaps, can you do a little test for me, to be able to > pinpoint the problem: > > First of all, look in the indexer.xml at the <cron> > configuration, and look at the index frequency (if you see > something like 0/5 * * * * ?) it means every 5 seconds. > > If you now could do a time out of at least 5 sec (or if it > says 0/10 at least 10 seconds) before putting the new > document. Can you confirm that it is working correct now? I > didn't look at the repository code yet, but I think it has > todo with the 'delete queue' and the 'add queue', where, the > put of the document removes the item from the index delete queue. > > Anyway, if you could do the test for me, would be great, > > Regards Ard > > > > > Hi, > > While querying our Hippo repository with a simple DASL query I > > discovered that the query is returning multiple references > to the same > > file in the repository. > > We have a process that updates files in the repository with new > > content in two steps: > > 1. DELETE the old file from the repository 2. PUT a new file with > > exactly the same file name in the repository. > > After such an update, the file appears in the DASL query > results one > > extra time for every update, so after two updates the file appears > > three times in the search results. > > This of course is undesirable because we feed the search result XML > > into an XSLT transformation to render a portlet. > > > > Example DASL: > > > > <?xml version="1.0" encoding="utf-8" ?> <d:searchrequest > > xmlns:s="http://jakarta.apache.org/slide/"; > > xmlns:h="http://hippo.nl/cms/1.0"; xmlns:d="DAV:"> > > <d:basicsearch> > > <d:select> > > <d:prop> > > <d:displayname/> > > </d:prop> > > </d:select> > > <d:from> > > <d:scope> > > <d:href>appdata/webwinkel/categorien</d:href> > > <d:depth>1</d:depth> > > </d:scope> > > </d:from> > > <d:where> > > <d:eq> > > <d:prop><h:caption/></d:prop> > > <d:literal>Kleding</d:literal> > > </d:eq> > > </d:where> > > </d:basicsearch> > > </d:searchrequest> > > > > Example result: > > > > <?xml version="1.0" encoding="UTF-8"?><D:multistatus xmlns:D="DAV:"> > > <D:response> > > > > <D:href>/default/files/default.www/appdata/webwinkel/categorie > > n/Kleding.xml</D:href> > > <D:propstat> > > <D:prop> > > <D:displayname>Kleding.xml</D:displayname> > > </D:prop> > > <D:status>HTTP/1.1 200 OK</D:status> > > </D:propstat> > > </D:response> > > <D:response> > > > > <D:href>/default/files/default.www/appdata/webwinkel/categorie > > n/Kleding.xml</D:href> > > <D:propstat> > > <D:prop> > > <D:displayname>Kleding.xml</D:displayname> > > </D:prop> > > <D:status>HTTP/1.1 200 OK</D:status> > > </D:propstat> > > </D:response> > > <D:response> > > > > <D:href>/default/files/default.www/appdata/webwinkel/categorie > > n/Kleding.xml</D:href> > > <D:propstat> > > <D:prop> > > <D:displayname>Kleding.xml</D:displayname> > > </D:prop> > > <D:status>HTTP/1.1 200 OK</D:status> > > </D:propstat> > > </D:response> > > </D:multistatus> > > > > What could be the cause of the behaviour? I don't think DASL/WEBDAV > > protocol allows you to do a SELECT DISTINCT. > > Thanks, > > Willem > > -- > > View this message in context: > > http://www.nabble.com/multiple-dasl-search-results-on-the-same > > -repository-entry-tp19607175p19607175.html > > Sent from the Hippo Repository development public > mailinglist mailing > > list archive at Nabble.com. > > > > _______________________________________________ > > HippoRepos-dev mailing list > > [EMAIL PROTECTED] > > http://lists.hippo.nl/mailman/listinfo/hipporepos-dev > > > _______________________________________________ > HippoRepos-dev mailing list > [EMAIL PROTECTED] > http://lists.hippo.nl/mailman/listinfo/hipporepos-dev > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
