[FOLIO-1229] Document CQL / SQL Performance Guidance Created: 26/Apr/18  Updated: 18/Jan/19

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

Type: Task Priority: P3
Reporter: Marc Johnson Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: core, sprint37
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to CQLPG-80 == relation creates a LIKE statement Closed
relates to UICHKIN-21 Use == for looking up records with an... Closed
relates to UICHKIN-18 Checkin takes > 1 min with ~2.5 milli... Closed
Sprint:
Development Team: Core: Platform

 Description   

Significant investigation into the performance of the inventory storage module has generated quite a lot of information about the kinds of SQL queries that are generated from CQL queries and the impact on performance.

It would be good to document this to clarify guidance around what kinds of queries to use in different circumstances and how best to support them in the backend implementations.

Examples of topics:

  • == vs. = relation semantics and performance implications
  • How index definitions need to match the case sensitivity and accent treatment of the CQL conversion

And possibly to expand upon it to improve the implementation. For example, it appears that a == relation creates a LIKE statement, and I wonder if there could be cases where an exact match could be done with a SQL equals?



 Comments   
Comment by Julian Ladisch [ 30/Apr/18 ]

This readme https://github.com/folio-org/cql2pgjson-java answers most of your questions.

Comment by Julian Ladisch [ 18/Jan/19 ]

"== relation creates a LIKE statement": Issue created: https://folio-org.atlassian.net/browse/CQLPG-80

Comment by Julian Ladisch [ 18/Jan/19 ]

https://dev.folio.org/faqs/explain-database-schema/

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