[FOLIO-2176] Address index warnings from perf test Created: 18/Jul/19  Updated: 03/Jun/20  Resolved: 26/Jul/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Hongwei Ji Assignee: Hongwei Ji
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File mod-circulation-storage.log     Text File mod-inventory-storage.log     Text File mod-users.log    
Issue links:
Relates
relates to RMB-436 Log both CQL and SQL within the missi... Closed
relates to CIRCSTORE-139 Address index warnings from perf test Closed
relates to MODUSERS-135 Address index warnings from perf test Closed
relates to RMB-440 Skip logging GIN index missing if b-t... Closed
relates to FOLIO-2143 verify performance of RMB26 versions ... Closed
relates to FOLIO-2197 Research "get inventory items by stat... Closed
Sprint: CP: sprint 68
Story Points: 3
Development Team: Core: Platform

 Description   

With the new RMB 26 release, a warning will be logged if the query does not have the expected index in database. Please try to resolve those warnings originated from platform-perf test run.

Missing index messages in the log

See attached files for the details including corresponding CQL and SQL queries

mod-inventory-storage:

WARNING: Doing LIKE search without GIN index for instance_holding_item_view.it_jsonb->>'barcode'
WARNING: Doing LIKE search without GIN index for instance_holding_view.ho_jsonb->>'permanentLocationId'
WARNING: Doing LIKE search without GIN index for service_point_user.jsonb->>'userId'

mod-users

WARNING: Doing FT search without FT index proxyfor.jsonb->>'proxyUserId'
WARNING: Doing FT search without FT index users_groups_view.jsonb->>'barcode'
WARNING: Doing FT search without FT index users_groups_view.jsonb->>'externalSystemId'
WARNING: Doing FT search without FT index users_groups_view.jsonb->'personal'->>'email'
WARNING: Doing FT search without FT index users_groups_view.jsonb->'personal'->>'firstName'
WARNING: Doing FT search without FT index users_groups_view.jsonb->'personal'->>'lastName'
WARNING: Doing FT search without FT index users_groups_view.jsonb->>'username'
WARNING: Doing FT search without FT index users.jsonb->>'active'
WARNING: Doing FT search without FT index users.jsonb->>'barcode'
WARNING: Doing FT search without FT index users.jsonb->>'externalSystemId'
WARNING: Doing FT search without FT index users.jsonb->'personal'->>'email'
WARNING: Doing FT search without FT index users.jsonb->'personal'->>'firstName'
WARNING: Doing FT search without FT index users.jsonb->'personal'->>'lastName'
WARNING: Doing FT search without FT index users.jsonb->>'username'
WARNING: Doing LIKE search without GIN index for proxyfor.jsonb->>'userId'
WARNING: Doing LIKE search without GIN index for users.jsonb->>'active'

mod-circulation-storage

WARNING: Doing FT search without FT index loan.jsonb->>'userId'
WARNING: Doing LIKE search without GIN index for loan.jsonb->'status'->>'name'
WARNING: Doing LIKE search without GIN index for request.jsonb->>'itemId'
WARNING: Doing LIKE search without GIN index for request.jsonb->>'requestType'
WARNING: Doing LIKE search without GIN index for request.jsonb->>'status'



 Comments   
Comment by Jakub Skoczen [ 22/Jul/19 ]

Hongwei Ji Can you attach the warning and CQL/SQL for each to this ticket? Should we create issues for specific warnings in individual Jira projects?

Comment by Hongwei Ji [ 22/Jul/19 ]

Note from standup: also need to create a Spike ticket to see how "==" will be handled (sql or gin).

Comment by Hongwei Ji [ 26/Jul/19 ]

Attached the logs with warning, cql and sql in one line ( RMB-436 Closed ). Created RMB-440 Closed to skip false alerts. Created CIRCSTORE-139 Closed and MOSUSERS-135 to address warnings. mod-inventory-storage is fine after RMB-440 Closed . Those warnings originated from VIEW will not be addressed since we are refactoring to use multi-table subqueries.

Generated at Thu Feb 08 23:18:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.