All work

Select view

Select search mode

 
45 of 45

Eliminate the use of CREATE INDEX statement due to RMB's optimized index re-creation mechanism

Won't Do

Description

RMB has optimized index re-creation since the Fameflower release, therefore the DROP INDEX snippet no longer works as intended and should be removed.

Please do not add "CREATE INDEX" for indexes that are maintained by RMB. If there really is a need to recreate an index remove it from RMB's rmb_internal_index table so that RMB recreates it: https://github.com/folio-org/raml-module-builder/blob/v35.0.3/domain-models-runtime/src/main/resources/templates/db_scripts/rmb_internal_index.ftl

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Vega

Release

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created June 13, 2023 at 9:01 AM
Updated September 8, 2023 at 2:10 PM
Resolved September 8, 2023 at 2:10 PM

Activity

Show:

Roman BarannykSeptember 8, 2023 at 1:32 PM

This ticket probably should be closed as won't do

Roman BarannykSeptember 6, 2023 at 11:32 AM
Edited

Investigated, mod-circulation-storage does not use "DROP INDEX", the single script that uses "CREATE INDEX" is not used for the indexes maintained by RMB. The script's purpose is to make the name of agedToLostDelayedBilling.dateLostItemShouldBeBilled index shorter and to allow creation of it

TestRail: Cases
TestRail: Runs

Flag notifications