QLDB doing a full table scan when using an OR across two indexed fields


We have a table T with two indexed fields A and B. When we query the table using the following query, QLDB does a full table scan (by evidence of the IO stats and latency):

select * from T where A = 'x' or B = 'y'

Why? And is that expected?

asked a year ago261 views
1 Answer

Well, a team member just pointed out that it is not supported according to this https://qldbguide.com/guide/data-design/#transaction-timeout

 --Multiple indexed fields (VIN, LicensePlateNumber) lookup using the OR operator
 --Disjunctions not currently supported 
 SELECT * FROM VehicleRegistration
 WHERE VIN = '1N4AL11D75C109151' OR LicensePlateNumber = 'LEWISR261LL'

This seems like a bizarre omission.

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions