search

heavyai / heavydb

HeavyDB (formerly OmniSciDB)
https://heavy.ai
Apache License 2.0
2.96k stars 448 forks source link

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

Open qwebug opened 5 months ago

qwebug commented 5 months ago

Describe:

SELECT /+ keep_table_function_result / \ FROM \

LIMIT \ OFFSET \ 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

qwebug commented 5 months ago

This problem came up at HeavyDB Version: 7.1.0-20230821-eae9ec17da (Docker: https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/v7.1.0/images/sha256-5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f?context=explore ) . And it has been fixed at HeavyDB Version: 8.0.2 (Docker: https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/v8.0.2/images/sha256-e343a97e342db3ba4e0ca069d567b76826dc7f6f95d07ee2af611f218194d28b?context=explore), after my verification. Thanks to the developers for their contributions.

Carmelo006 commented 2 weeks ago

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

  • © Githubissues.
  • Githubissues is a development platform for aggregating issues.