Cmis query result not up-to-date
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2013 08:53 AM
Hello,
I have a query giving me all documents from a specific folder structure (including subfolders) and having
a specific number as aspect (which alocates it to a group).
The query works correctly.
There is also a possibilty to delete a document (it will simply be moved to a "trash" folder).
When I'm returning to the view showing me all documents, this "deleted" document is still shown nevertheless
it isn't anymore in the folder the query searchs in (with "IN_TREE"). Nevertheless after some time the document
isn't shown anymore by the query.
I guess there is a cache, saving the results and the query isn't executed anymore but the results are simply
taken from this cache therefore I added the command
session.getDefaultContext().setCacheEnabled(false);
before executing the query but this didn't solved the problem.
Does any one known why the moved document is still shown? Can anyone help me?
I have a query giving me all documents from a specific folder structure (including subfolders) and having
a specific number as aspect (which alocates it to a group).
The query works correctly.
There is also a possibilty to delete a document (it will simply be moved to a "trash" folder).
When I'm returning to the view showing me all documents, this "deleted" document is still shown nevertheless
it isn't anymore in the folder the query searchs in (with "IN_TREE"). Nevertheless after some time the document
isn't shown anymore by the query.
I guess there is a cache, saving the results and the query isn't executed anymore but the results are simply
taken from this cache therefore I added the command
session.getDefaultContext().setCacheEnabled(false);
before executing the query but this didn't solved the problem.
Does any one known why the moved document is still shown? Can anyone help me?
Labels:
- Labels:
-
Archive
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2013 10:36 AM
Do you happen to be using Solr for your search engine? If so, it is eventually consistent, which means that deletes (and creates) won't show up immediately. There is some lag.
Jeff
Jeff
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2013 02:36 AM
Yes, I am.
So, there is nothing, I can do about it?
So, there is nothing, I can do about it?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2013 09:54 AM
You can reduce the latency by changing the alfresco.cron property in file solrcore.properties which is under your solr core(under workspace-SpacesStore\conf\)
, so Solr would check for repository updates more freqently, It's default value is 15 seconds
, so Solr would check for repository updates more freqently, It's default value is 15 seconds
alfresco.cron=0/15 * * * * ? *
