Hi Ard, Thanks for the quick response. > > I do not understand this. Do you mean that you in dasl-indexer.xml you > configure <cron>0/5 * * * * ? *</cron> or do you mean something else? I > you mean the cron job in the dasl-indexer.xml, it means that every 5 > seconds batch index runs when there are documents in the queue, ie when > documents are added/deleted/modified. If you mean something else with > the 5 seconds, I would really like to have some extra info because i am > in the dark
Sorry, perhaps I should have mentioned where I configured it, but yes, I was referring to the indexer declared in dasl-indexer.xml >> >> Now whenever we update any of these metadata files, the >> repository notices the files have changed and tries to re >> index them, so far so good. >> However, when we try to query the repo for any of these >> custom properties whilst the extractor is updating the index, >> we don't get back the result set we expected. > > Do you mean by this, that for example a webdav property changes from 1 > -> 2, and you query for the value '1' and you still get the document, > while the property already changed to '2'. This might be the case since > when you query the repository directly after the change, before the > indexing ran, the index is not yet updated, so you'll get an 'old' > result. I am not sure what kind of app you are developing (you might > explain a little) but basically it means that when you have an app > modifying data and at the same time searching the repository, you can > seem to get stale data. The document contains a lot of metadata, only part of it is relevant to hippo. The metadata that is being extracted by hippo, think properties like unique identifiers don't change value over time. The problem that we're seeing when executing a dasl query for one of these properties while the indexer is running is not that were getting stale data, we're getting no data. It's almost as if the indexer throws out the old entries completely, and then recreates them instead of just updating any values that changed. Daan Hoogenboezem ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
