Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solr documents of custom content properties are removed from index when node is reindexed #422

Open
alexanderjakab opened this issue Apr 28, 2023 · 1 comment

Comments

@alexanderjakab
Copy link

alexanderjakab commented Apr 28, 2023

Since ASS 2.0.1.5 the indexation of custom content properties was reintroduced by setting the property solr.enableIndexingCustomContent to true.

On a node update in the alfresco repository the solr-documents for that node is reindexd. Those for the custom content properties are removed for one reindex cycle. This leads to a different behaviour than the reindexation of all other node properties ...

the search results for the custom content properties simply disappear for one reindex cycle. from an enduser perspective this leads to inconsistent searchresults and the impression of a defect in the default search behaviour

can be reproduced by using the following sdk sample project.
alfresco-sdk-sample-reindex-content-properties.zip

  1. build sample project with maven and start acs with run.sh start
  2. call sample webscript from your browser : http://localhost:8080/alfresco/s/sample/helloworld
    now a test node was created here "/app:company_home/cm:test/cm:test.txt". it has 1 custom content-property acme:metadataIndex. you can verify in your node-browser
  3. use the nodebrowser so search for the node: aftsQuery: "acme:metadataIndex:Alexander" and you will find the node as expected
  4. call the sample webscript again
    on an already existing node - the cm:name property will be changed to cm:xtest.txt leading to a reindex
  5. use the nodebrowser so search for the node: aftsQuery: "acme:metadataIndex:Alexander" . after solr tracks the update the result will disappear.
  6. keep searching ... after 8 sec. it will appear again
@isandhu
Copy link

isandhu commented Jul 12, 2023

This is fixed in:
MNT-23669: Custom d:content indexes becomes temporarily unsearchable when any property on the node is updated
It was released as a hotfix in Search Services 2.0.5.2 and will also be part of the upcoming 2.0.8 SP release.

Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants