You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> set 'ksql.query.pull.range.scan.enabled'='true'
> select * from customer where id > 1 and id < 5;
> Multi-column sources must specify every key in the WHERE clause. Specified: [`CUSTID`] Expected: [`CUSTID` INTEGER KEY, `TARGET_DB` STRING KEY, `OFFSET` BIGINT KEY, `PARTITION` INTEGER KEY]. See https://cnfl.io/queries for more info.
> Add EMIT CHANGES if you intended to issue a push query.
> Pull queries require a WHERE clause that:
> - includes a key equality expression, e.g. `SELECT * FROM X WHERE <key-column> = Y;`.
> - in the case of a multi-column key, is a conjunction of equality expressions that cover all key columns.
> - to support range expressions, e.g., SELECT * FROM X WHERE <key-column> < Y;`, range scans need to be enabled by setting ksql.query.pull.range.scan.enabled=true
> If more flexible queries are needed, , table scans can be enabled by setting ksql.query.pull.table.scan.enabled=true.
The text was updated successfully, but these errors were encountered:
Taymindis
changed the title
ksql.query.pull.range.scan.enabled on PK is not working
ksql.query.pull.range.scan.enabled for primary key is not working
Sep 14, 2024
The text was updated successfully, but these errors were encountered: