[IGNITE-13280] Improper index usage, fields enumeration not used with pk index creation.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.9
• Component/s: sql
• Assignee: Evgeny Stanilovsky
• Reporter: Evgeny Stanilovsky
• Created: 21/Jul/20 11:25
• Updated: 06/Aug/21 15:24
• Resolved: 25/Aug/20 09:05

Description

For example:

CREATE TABLE PUBLIC.TEST_TABLE (FIRST_NAME VARCHAR, LAST_NAME VARCHAR, ADDRESS VARCHAR, LANG VARCHAR,  CONSTRAINT PK_PERSON PRIMARY KEY (FIRST_NAME, LAST_NAME));

CREATE INDEX "idx2" ON PUBLIC.TEST_TABLE (LANG, ADDRESS);

and further explain:

SELECT
    "__Z0"."FIRST_NAME" AS "__C0_0",
    "__Z0"."LAST_NAME" AS "__C0_1",
    "__Z0"."ADDRESS" AS "__C0_2",
    "__Z0"."LANG" AS "__C0_3"
FROM "PUBLIC"."TEST_TABLE" "__Z0"
    /* PUBLIC.IDX2: ADDRESS > 0 */
WHERE "__Z0"."ADDRESS" > 0

this is erroneous to use "idx2" here, because first index field LANG not equals to predicate ADDRESS.
Looks like this bug brings this ticket [1]

[1] https://issues.apache.org/jira/browse/IGNITE-10217

Issue Links

• links to: GitHub Pull Request #8067