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

[GPU Logic Bug] SELECT /*+ keep_table_function_result */ <column> FROM <table> LIMIT <number> OFFSET <number> Brings Errors #832

Open
qwebug opened this issue Jun 5, 2024 · 1 comment

Comments

@qwebug
Copy link

qwebug commented Jun 5, 2024

Describe:

SELECT /*+ keep_table_function_result */ <column> FROM <table> LIMIT <number> OFFSET <number> brings different results, when using CPU-only configurations and GPU-used configurations.

SQL with CPU-only Config:

CREATE TABLE t0(c0 bigint);
INSERT INTO t0(c0) VALUES(1);
ALTER SESSION SET EXECUTOR_DEVICE='CPU';
SELECT /*+ keep_table_function_result */ * FROM t0 LIMIT 1 OFFSET 1;

Result:

No rows returned.

SQL with GPU-used Config:

ALTER SESSION SET EXECUTOR_DEVICE='GPU';
SELECT /*+ keep_table_function_result */ * FROM t0 LIMIT 1 OFFSET 1;

Result:

c0
1

Environment:

Docker Deployment

https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/latest/images/sha256-5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f?context=explore

Docker DIGEST: sha256:5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f

HeavyDB Version: 7.1.0-20230821-eae9ec17da

HeavyDB license: Free Edition

@Carmelo006
Copy link

HeavyDB v8.1.1 has fixed this issue, after I comfirmed.
Thanks for your report @qwebug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants