cancel
Showing results for 
Search instead for 
Did you mean: 

Solr search results are not corrected

castgroupteam
Champ in-the-making
Champ in-the-making
Hi all,
I'm struggling with this issue I have opened on JIRA:
https://issues.alfresco.com/jira/browse/ALF-20475

A user closed the issue saying to watch the issue MNT-626.
Problem is that I can't see that issue.
Someone can help to investigate the problem and possible find a workaround keeping use of solr engine?

Thanks in advance

Daniele
6 REPLIES 6

afaust
Legendary Innovator
Legendary Innovator
Hello,

the fix is in Alfresco 4.2d/e - you need to upgrade to get it or try to backport it from that codebase.

Regards
Axel

castgroupteam
Champ in-the-making
Champ in-the-making
Thank you Axel,
I know the 4.2 version include the patch but in in this case I can not upgrade the environement. An upgrade task must be studied tested and takes a lot of time.
I found a workaround applying a small set of permissions for transaction at a time, but it's just a workaround.
In order to backport the codebase I need to know where to watch in the code but the Alfresco's team keep all those informations private.
I still don't know where exactly the limit is , I thought was of 1024 rows of acl for transaction but I really don't think this is the real limit.
This is a very bad issue that can cause problems very hard to investigate and I think the nature of the issue must not keeped private. I just mean the explanation of the problem, not the patch! The patch is right that can only be available for Enterprise users.
Thank you again.

Regards
Daniele



afaust
Legendary Innovator
Legendary Innovator
Alfresco usually works in a transparent way. The problem with the MNT JIRA is that information provided by an Enterprise customer that may be necessary to reproduce / understand an issue is transferred to the JIRA as well and Alfresco needs to somehow protect the data of the customer from public access. This is why tickets triggered by Enterprise customers are usually marked private. I think if it were up to the Alfresco engineers they would certainly like to keep the process as transparent to the community as possible.

castgroupteam
Champ in-the-making
Champ in-the-making
I've tried to retrieve some informations from engeneers in order to better understand the problem, but no way.
My issue was closed without any explanation; just that it has been solved on the newest versions. I still don't know where is the problem, I just know from my tests that big acl transaction (acl_change_set) fail indexing without any kind of error or warning so my workaround was to make many smaller transaction.
Thank you anyway.

Daniele

mrogers
Star Contributor
Star Contributor
Problem is with these two files that were limiting the number of ACLs to 1024
MODIFY /alfresco/PATCHES/V4.1.2/root/projects/repository/source/java/org/alfresco/repo/domain/solr/ibatis/SOLRDAOImpl.java
MODIFY /alfresco/PATCHES/V4.1.2/root/projects/solr/source/java/org/alfresco/solr/client/SOLRAPIClient.java

Thank you very much mrogers!

This is a good starting point. I will compare source codes as soon as possible an then i will post my conclusions on this topic!

Daniele