After debugging the source code, I think the dynamic shard registry has been removed from Alfresco Community Edition. At query time, alfresco apparently instantiates always the ExplicitSolrStoreMappingWrapper instead of the DynamicSolrStoreMappingWrapper. At least with DB_ID_RANGE sharding. That happens even if you have explicitly enabled the dynamic registry (solr.useDynamicShardRegistration=true).
That because shardRegistry object is null when alfresco tries to extract and build the Solr mapping by SolrClientUtil:
// org.alfresco.repo.search.impl.solr.SolrClientUtil
//
public static SolrStoreMappingWrapper extractMapping(StoreRef store,
HashMap<StoreRef, SolrStoreMappingWrapper> mappingLookup, ShardRegistry shardRegistry,
boolean useDynamicShardRegistration,BeanFactory beanFactory)
{
// shardRegistry is null here !!!
if((shardRegistry != null) && useDynamicShardRegistration)
{
SearchParameters sp = new SearchParameters();
...
return DynamicSolrStoreMappingWrapperFactory.wrap(slice, beanFactory);
}
else
{
// ok there's another wrapper for you,
// this is the concrete ExplicitSolrStoreMappingWrapper here
SolrStoreMappingWrapper mappings = mappingLookup.get(store);
....
return mappings;
}
}I think devs have intentionally removed part of shard registry implementation on community edition. I can see a specific search-enterprise-context.xml for the enterprise edition that is missing on community ed.
<bean id="search.solrQueryHTTPCLient" class="org.alfresco.repo.search.impl.solr.SolrQueryHTTPClient" init-method="init">
...
<property name="shardRegistry">
<ref bean="search.SolrShardRegistry"/>
</property>And this is the implementation in common-search-enterprise-context.xml
<bean id="search.solrShardRegistry" class="org.alfresco.repo.index.shard.ShardRegistryImpl" init-method="init">
<property name="purgeOnInit">
<value>${search.solrShardRegistry.purgeOnInit}</value>
</property>I think the official documentation should be updated about that
