Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ksql.query.pull.range.scan.enabled for primary key is not working #10434

Open
Taymindis opened this issue Sep 14, 2024 · 0 comments
Open

ksql.query.pull.range.scan.enabled for primary key is not working #10434

Taymindis opened this issue Sep 14, 2024 · 0 comments

Comments

@Taymindis
Copy link

> 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.
@Taymindis 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant