Such a situation, when a document doesn't exists in nuxeo shell, but is still listed by the web application may happen if lucene indexes (created by the search service) are desynchronized with JCR repository. This is because the web application is using a search to display the content of a folder while nuxeo shell is using repository API (getChildren() method) to get the children. So, after a crash, it may happen to have a document that is indexed but that doesn't exists in the repository.
If nuxeo shell doesn't see the document it means it doesn't exists in the repository. The only solution is to rebuild lucene indexes by doing an reindexing of the repository. Bogdan Alex Viggio wrote: > We experienced a Nuxeo error when uploading a PDF. Now there is an > item listed in the folder corresponding to that upload in the Nuxeo EP > user interface, but when you select the check box for it, and attempt > to delete it you see another error. > > I had installed the Nuxeo Shell and thought I might delete it that > way, but when I navigate to the folder containing that bad document -- > it is not even listed. So the Shell is showing different contents than > Nuxeo EP. Why is that? I tried reindexing using the 'index' command in > the Shell, but that didn't fix anything. > > How can I best permanently remove this corrupted upload/document so > that I can attempt another upload? Do I need to modify the raw SQL > data? > > Thanks! > - Alex > _______________________________________________ > ECM mailing list > [email protected] > http://lists.nuxeo.com/mailman/listinfo/ecm > _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
