Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Prevent mass indexer from dropping the schema on start when requested but multitenancy is configured

Description

When configured, a mass indexer started from a session will drop the schema for all tenants but re-index the data only for the tenant for which the current session is created. Instead the mass indexer should throw an exception.

Activity

Show:

Yoann Rodière June 4, 2024 at 8:55 AM

I’d suggest qualifying as bug, since the current behavior really is a bug, and that would justify the breaking change.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Priority

Created June 4, 2024 at 7:03 AM
Updated June 10, 2024 at 1:14 PM
Resolved June 6, 2024 at 2:10 PM