Matt Howard ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3499 ( https://hibernate.atlassian.net/browse/HSEARCH-3499?atlOrigin=eyJpIjoiMWY... ) Re: Near-zero-downtime mass indexing ( https://hibernate.atlassian.net/browse/HSEARCH-3499?atlOrigin=eyJpIjoiMWY... ) Is there a way to access the (expected) mapping of a given index? I am attempting to manually implement a zero-downtime reindexing (ES backend) as outlined in the docs: https://docs.jboss.org/hibernate/search/6.0/reference/en-US/html_single/#... But when creating the new index (by calling the ES API directly) I don’t see how to post the index mappings along with the new index. Create a new index, myindex-000002. I’m attempting to do this when our mappings change so I can’t just get the existing JSON from the ES API and copy them. I believe I need to use the ES API directly rather than using the SchemaManager in hsearch, because schema management doesn’t like the read/write aliases pointing to different indexes: HSEARCH400593: Index aliases [test_indexed_entity-write, test_indexed_entity-read] are assigned to a single Hibernate Search index, but they are already defined in Elasticsearch and point to multiple distinct indexes: [test_indexed_entity-000002, test_indexed_entity-000001] Am I taking the wrong approach or just missing how to access the updated IndexMetadata ? ( https://hibernate.atlassian.net/browse/HSEARCH-3499#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3499#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100129- sha1:3ed9692 )