AnsweredAssumed Answered

Alfresco Custom Model searches doesn't return all documents

Question asked by lieu2 on Mar 16, 2011
Latest reply on Apr 22, 2011 by lieu2
Hello,
I upgraded from Alfresco 2.1 to 3.3 then imported my old Alfresco 2.1 repository data using the ACP bulk export then bulk import into Alfresco 3.3. I am unable to obtain the same number of documents from the search results in the Node Browser when I issue a Lucene query using a few the custom model properties which are defined under my custom aspects in my custom model file. Is there any differences in the version of 2.1 to 3.3 would cause the import and indexing of these documents to have issues? I don't see any issues when I start up Tomcat, but I'm not sure is there some difference in how custom models are defined in Alfresco 3.3? I would assume that Alfresco would retain backward compatibility. I made the necessary configurations for my custom model in web-client-config-custom.xml as well.

Under log4j, I turned up: log4j.logger.org.alfresco.repo.search.Indexer=debug and log4j.logger.org.alfresco.repo.search.impl.lucene.index=debug but I don't see any error messages.

Any help would be greatly appreciated. Thank you for your help in advance!

Outcomes