Open qwebug opened 4 months ago
SELECT /+ keep_result / \ FROM \ LIMIT \ OFFSET \ brings different results, when using CPU-only configurations and GPU-used configurations. SQL with CPU-only Config: CREATE TABLE t2(c0 FLOAT); INSERT INTO t2(c0) VALUES(0.1); ALTER SESSION SET EXECUTOR_DEVICE='CPU'; SELECT /*+ keep_result */ * FROM t2 LIMIT 1 OFFSET 1; Result: No rows returned. SQL with GPU-used Config: ALTER SESSION SET EXECUTOR_DEVICE='GPU'; SELECT /*+ keep_result */ * FROM t2 LIMIT 1 OFFSET 1; Result: c0 0.10000000149011612 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 3 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.
CREATE TABLE t2(c0 FLOAT); INSERT INTO t2(c0) VALUES(0.1); ALTER SESSION SET EXECUTOR_DEVICE='CPU'; SELECT /*+ keep_result */ * FROM t2 LIMIT 1 OFFSET 1;
No rows returned.
ALTER SESSION SET EXECUTOR_DEVICE='GPU'; SELECT /*+ keep_result */ * FROM t2 LIMIT 1 OFFSET 1;
c0 0.10000000149011612
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
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.
Describe:
SELECT /+ keep_result / \ FROM \ LIMIT \ OFFSET \ brings different results, when using CPU-only configurations and GPU-used configurations.
qwebug
commented
3 months ago
- © Githubissues.
- Githubissues is a development platform for aggregating issues.
SQL with CPU-only Config:
Result:
SQL with GPU-used Config:
Result:
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
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.