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

Endless loop for bad SQL like: SELECT * FROM table WHERE id IN () #827

Closed
liuqianzhong opened this issue May 14, 2018 · 2 comments · Fixed by #825
Closed

Endless loop for bad SQL like: SELECT * FROM table WHERE id IN () #827

liuqianzhong opened this issue May 14, 2018 · 2 comments · Fixed by #825
Assignees

Comments

@liuqianzhong
Copy link

Please answer these questions before submitting your issue. Thanks!
开源不易,我们希望将精力放在完成新功能和解决有价值的问题上,为了让大家的配合更具有效率,请填写以下列出的全部问题
sj死循环,导致内存溢出

Which version of Sharding-Sphere do you using?(您使用的Sharding-Sphere版本为?)

2.1版本

Expected behavior (您预期的结果是)

虽然sql不对,但是sj不能死循环,导致内存溢出,影响其他业务,sql报错就行

Actual behavior (实际运行的结果是)

死循环

Steps to reproduce the behavior (可重现问题的操作步骤)

select * from table where id in ();

Please provide the reproduce example codes (such as github link),otherwise we will label the issue as Invalid and close it.(为了节省复现问题的时间,请务必提供可重现的代码,否则我们会将issue直接标记为invalid并关闭)

image
Code should based on https://github.com/sharding-sphere/sharding-sphere-example
(代码请基于 https://github.com/sharding-sphere/sharding-sphere-example)

@terrymanu
Copy link
Member

fixed at #825

terrymanu added a commit that referenced this issue May 14, 2018
@terrymanu terrymanu changed the title 分片建in查询,死循环 Endless loop for bad SQL like SELECT * FROM table WHERE id IN () Aug 8, 2018
@terrymanu terrymanu changed the title Endless loop for bad SQL like SELECT * FROM table WHERE id IN () Endless loop for bad SQL like: SELECT * FROM table WHERE id IN () Aug 8, 2018
@terrymanu
Copy link
Member

fixed at 3.0.0.M1

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

Successfully merging a pull request may close this issue.

3 participants