Alfresco Custom Model searches doesn't return all documents

[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!

[amitabhandari1]

Hi Lieu2,

I can suggest few things :
1. Did you make your code compatible to Alfresco V.3.3
2. Please try to do Full Indexing , indexes might get corrupt

In content Model alfresco does not support backward compatibility but if your model has any error then that will come at time of server start up. Alfresco 3.3 has impose some more restrictions for defining model.

Thanks,

[loftux]

ACP export/import is only supported between same version repositories. There are a lot of patches run to upgrade your data that you have now missed out. And standard acp doesn't bring along versions.
May I ask why you did an export/import, and not upgrade your repository with the content intact?

[lieu2]

Question by Loftux:

ACP export/import is only supported between same version repositories. There are a lot of patches run to upgrade your data that you have now missed out. And standard acp doesn't bring along versions.
May I ask why you did an export/import, and not upgrade your repository with the content intact?

My response:
Our previous developers customized Alfresco 2.1 to do many things that Alfresco was not designed for. We are trying to rip out all of the customizations made by the previous developers to Alfresco 2.1 so that we can just go back to a vanilla Alfresco version so taht we can use Alfresco the way it was intended (managing the documents, and as of right now we are using Alfresco for managing documents but we are using it for a bunch of other unintended purposes). We thought we could just use an ACP export of the document data so that we can just upgrade from Alfresco 2.1 to 3.2 after making changes to our custom model file.

Response to AmitaBhandari:
Currently we have ripped out all of the customizations made to Alfresco v2.1 in hopes that we can just migrate the documents over to 3.3. I have tried doing a full indexing and the indexes from what I see are okay but during searches in the node browser, incorrect document results come back in certain cases since we have constrained values on our custom aspect properties to only a certain allowed number of values which we specify in our model file.
I don't see any error messages upon starrtup related to our custom model file.

Thank you all for your responses! I greatly appreciate it! Hope to hear from you guys as well as other users soon!

[lieu2]

Correction we are currently using Alfresco 2.2 and not 2.1.

[loftux]

This is what I would do in your situation.
Keep the content model, but only the model, not any of the other customizations. That means all your content will be intact, indexing will work, and you can upgrade according to recommended procedures. The result is for the end user that you want see any custom properties, by removing customizations like webclient-custom-config.xml you are essentially hiding for end user. Whats important is that data integrity is intact.
-Take a clean 2.2 alfresco.war, and replace any customized alfresco.war.
-Remove all customization stuff out of tomcat/share/classes/alfresco/extension
-In extension, keep the data model.
-Now restart 2.2, make sure everything works

-Start the upgrade procedure as outlined in the wiki article I linked to.
-> End result should be that you have an upgraded environment, default install, with some deprecated properties, constraints.

When would this method not work? I can think if instead of creating your own model, your external developers modified alfresco default model. That would definitely complicate/break things.
There may be other stuff in your model that makes my approach harder, but then I need to see it.

[lieu2]

I got the 2.1 to 3.3 search issue resolved. In actuality there was an ACL with lucene index in which I had to up the time out configuration parameter in repository.properties and hence all the documents in Alfresco were not being indexed by the lucene indexer.

Thank you everyone for your replies! I greatly appreciate it!