[jira] [Updated] (GEODE-5096) AddCacheServerProfile should throw an error when conflicting Lucene indexes are concurrently created
[ https://issues.apache.org/jira/browse/GEODE-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-5096: --- Issue Type: Sub-task (was: New Feature) Parent: GEODE-3924 > AddCacheServerProfile should throw an error when conflicting Lucene indexes > are concurrently created > > > Key: GEODE-5096 > URL: https://issues.apache.org/jira/browse/GEODE-5096 > Project: Geode > Issue Type: Sub-task > Components: lucene >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > > When two servers concurrently define a LuceneIndex, the addCacheServerProfile > should throw an error to avoid conflicting indexes being defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5096) AddCacheServerProfile should throw an error when conflicting Lucene indexes are concurrently created
[ https://issues.apache.org/jira/browse/GEODE-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-5096: - Summary: AddCacheServerProfile should throw an error when conflicting Lucene indexes are concurrently created (was: AddCacheServerProfile should throw an error when conflicting Lucene are concurrently created) > AddCacheServerProfile should throw an error when conflicting Lucene indexes > are concurrently created > > > Key: GEODE-5096 > URL: https://issues.apache.org/jira/browse/GEODE-5096 > Project: Geode > Issue Type: New Feature > Components: lucene >Reporter: Udo Kohlmeyer >Assignee: Udo Kohlmeyer >Priority: Major > > When two servers concurrently define a LuceneIndex, the addCacheServerProfile > should throw an error to avoid conflicting indexes being defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)