Search Services 2.0.2 Release

[angelborroy]

Obtaining this release

If you are using Docker, you can get the new Image by typing:

docker pull alfresco/alfresco-search-services:2.0.2

Source code for the release can be found in https://github.com/Alfresco/SearchServices/releases/tag/2.0.2

If you are Enterprise user, you can get distribution ZIP files:

• Search Services: https://process.alfresco.com/r/amazon/edl/?p=SearchServices/2.0.2&f=alfresco-search-services-2.0.2.z...
• Insight Engine: https://process.alfresco.com/r/amazon/edl/?p=InsightEngine/2.0.2&f=alfresco-insight-engine-distribut...
• Insight Zeppelin: https://process.alfresco.com/r/amazon/edl/?p=InsightZeppelin/2.0.2&f=alfresco-insight-zeppelin-2.0.2...

And also, only for Enterprise customers, the source code for this version is available in:

https://github.com/Alfresco/InsightEngine/tree/2.0.2

Insight Engine and Insight Zeppelin artifacts can be downloaded from Quay.io using Enterprise credentials.

Upgrading

Search 2.0.x will require a full re-index upon deployment when upgrading from Search 1.x.
This is necessary to accommodate the removal of the index store and improved storage of date fields.

If you were using Search 2.0.x, no changes are required on you SOLR indexes.

Improvements

• Updated default configuration to improve indexing performance, query performance and resource usage compared with versions 2.0.0 and 2.0.1 (SEARCH-2887)
• Improved query performance compared with versions 2.0.0 and 2.0.1 (SEARCH-2548)
• Updated documentation for considerations prior to a re-index or upgrade to Search Services 2.0 (SEARCH-2887)
• Updated documentation for exact term search (SEARCH-2904)
• Additional option for Search Services to authenticate with a shared secret header (SEARCH-2802)

Bugs Fixed

• SEARCH-2548: Query performance degradation
• SEARCH-2986: Search with mTLS enabled does not work with ACS 7.x
• SEARCH-2985: Starting Search Services without creating cores (alfresco, archive) is not working
• SEARCH-2995: Remove backup location in alfresco search service admin screen and SOLR REST API
  
  • Note that from Search Services 2.0.2 SOLR REST API for backup is not working anymore. It's required to configure the "solr.backup.dir" property in "solrcore.properties" file for SOLR Core. More details available in https://github.com/Alfresco/InsightEngine/pull/1188/files

Known Issues

• SEARCH-2461: Exact term queries behave differently against the DB and Solr
• SEARCH-2994: ISUNSET doesn’t return the correct results

Third Party Product Versions

• Solr 6.6.5 (patched)
• Jetty 9.3.29.v20201019
• Zeppelin 0.8.2

Compatibility

• Search Services 2.0.2 works with ACS 6.2
• Insight Engine 2.0.2 works with ACS 6.2 and AGS 3.2.0
• JVM 11 is required

[heiko_robert]

Hi@angelborroy,  thanks for sharing. Isn't there also a community zip download? Could you elaborate on "Updated default configuration", please?

[angelborroy]

We're working on the ZIP Distribution and repository tag for Community: https://alfresco.atlassian.net/browse/SEARCH-3006

I'll update this blog post once that's fixed.

Regarding to the "updated default configuration", you can get additional details in:

https://alfresco.atlassian.net/browse/SEARCH-2887

Mainly is disabling FINGERPRINT feature and removing SOLR Document Cache (as we are not using it).

[gabrielmarinb]

Thanks Angel for the detailed information. I have just upgraded from Search Services 2.0.0 and I am unable to search through custom metadata. Standard metadata search is working fine (cm:title, cm:description)

I noted that in my model i used a prefix that a shouldn't (dc) but i can't change it now that i have a couple of million documents.

Can you give me any hint?

[angelborroy]

You may try undeploying the conflicting model if you are not using it.

I guess you are referring to

<namespace uri="http://purl.org/dc/elements/1.1/" prefix="dc"/>

[JelleW]

@angelborroy 

What is the procedure for announcing a new patch release of search services? I found two new versions 2.0.3 and 2.0.4 in the product download page but there are no announcement for them like this one?

[fvargasj]

Hi Angel!

We are experiencing a problem when trying to reindex a huge repository (7TB of content store) and 12 million nodes approx in the repository. We took a snapshot of the contentstore and the database for the real data with an ACS v6.2.2.23, and ASS 1.4.3.3 instance running in production. Then, we put that snapshot into an ACS v7.2.3.1, and ASS 2.0.3 instance starting a full reindex.

The output for that action is the following.

ACS v6.2.2.23 / ASS 1.4.3.3

Size of the index:

• Main (Workspace)Store: 60GB
• Archive Store: 26GB

ACS v7.2.3.1 / ASS 2.0.3

Size of the index:

• Main (Workspace)Store: 150GB
• Archive Store: 49GB

As you can check, the size of the indexes is 2.5 times higher than previously. Apart from that, it took 60h to complete the full reindex work and, due to the https://host/alfresco/s/enterprise/admin/admin-searchservice page, the DB transactions were indexed after 19-20h approx. From that point, the index continued increasing drastically until it finishes the task.

Is that behaviour normal? Is that something you could check during your tests?

Thanks,

Fernando.

[heiko_robert]

Hi Fernando,

the Release note page may not the best place to ask for support. Please use the Alfresco Content Services or Alfresco's Community Discord Channel instead.

You may have stumbled onto CascadeTracker creates veeery big indexes when using secondary assocs on folders #415  

This means, if there are any secondary child associations on folders in your repo you may multiply your index size (depending on the hierarchy level the secondary is defined).
The only way to avoid this would be to disable PATH indexing or to remove secondary assocs, but this may not be an option ...

Regards

Heiko