org.hibernate.search.backend.elasticsearch.impl.IndexNamesRegistry Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of hibernate-search-backend-elasticsearch Show documentation
Show all versions of hibernate-search-backend-elasticsearch Show documentation
Hibernate Search Backend relying on remote Elasticsearch clusters
The newest version!
/*
* SPDX-License-Identifier: Apache-2.0
* Copyright Red Hat Inc. and Hibernate Authors
*/
package org.hibernate.search.backend.elasticsearch.impl;
import java.util.LinkedHashSet;
import java.util.Map;
import java.util.Set;
import java.util.concurrent.ConcurrentHashMap;
import org.hibernate.search.backend.elasticsearch.index.layout.impl.IndexNames;
import org.hibernate.search.backend.elasticsearch.logging.impl.MappingLog;
final class IndexNamesRegistry {
private final Map indexNamesByName = new ConcurrentHashMap<>();
void register(IndexNames newIndexNames) {
// Put everything in a set to avoid failures if, for example, the Hibernate Search name is identical to the read name
// (that's not a problem per se, and should be checked elsewhere).
Set names = new LinkedHashSet<>();
names.add( newIndexNames.write().original );
names.add( newIndexNames.read().original );
// Also prevent other indexes from using the Hibernate Search index name as their name/alias.
// This is just to avoid confusing setups.
names.add( IndexNames.normalizeName( newIndexNames.hibernateSearchIndex() ) );
for ( String name : names ) {
IndexNames existingIndexNames = indexNamesByName.putIfAbsent( name, newIndexNames );
if ( existingIndexNames != null ) {
throw MappingLog.INSTANCE.conflictingIndexNames(
existingIndexNames.hibernateSearchIndex(),
newIndexNames.hibernateSearchIndex(),
name
);
}
}
}
}
© 2015 - 2024 Weber Informatics LLC | Privacy Policy