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

[Crash Bug] SELECT * FROM <table> JOIN <table> ON NULL WHERE FALSE Brings Errors #812

Open
qwebug opened this issue Oct 18, 2023 · 2 comments

Comments

@qwebug
Copy link

qwebug commented Oct 18, 2023

Describe:

HeavyDB will crash when using SELECT * FROM <table> JOIN <table> ON NULL WHERE FALSE, after SET EXECUTOR_DEVICE='GPU'.

SQL:

ALTER SESSION SET EXECUTOR_DEVICE='GPU';
CREATE TABLE t0(c0 INT);
CREATE TABLE t1(c0 INT);
SELECT * FROM t1 JOIN t0 ON NULL WHERE FALSE;

Result:

2023-10-18T03:08:34.218366 F 3966 10 8 RelAlgDag.h:288 Check failed: ptr
Stack trace:
RelLeftDeepInnerJoin::RelLeftDeepInnerJoin
create_left_deep_join
RelAlgDagBuilder::optimizeDag
RelAlgDagBuilder::build
RelAlgDagBuilder::buildDag
DBHandler::execute_rel_alg
QueryDispatchQueue::worker
clone
/opt/heavyai/scripts/innerstartheavy: line 180:  3966 Aborted                 (core dumped) ./bin/heavydb $MAPD_DATA $RO --port $MAPD_TCP_PORT --http-port $MAPD_HTTP_PORT --calcite-port $MAPD_CALCITE_PORT $CONFIG $VERBOSE $*
Failed to write to log, write storage/log/heavy_web_server.7ff8a2f8be28.root.log.ALL.20231018-030751.3967: file already closed
startheavy 3955 exited

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

@cdessanti
Copy link
Contributor

cdessanti commented Oct 18, 2023

We can consider a duplicated of #810

@qwebug
Copy link
Author

qwebug commented Jan 21, 2024

This issue is different from #810 in that they both cause crashes due to different forms of SQL.

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