Stackoverflow typically means one of two things: infinite planning or very
deep trees being created that go beyond stack height. It's important to
remember that this is a relatively arbitrary magic threshold so small
non-functional changes can potentially influence whether you hit this
condition or
Hi Jeremy,
if you manage to repro as a unit test in Calcite (as Stamatis suggested)
you can "git bisect" on that specific test to find the right commit.
Best regards,
Alessandro
On Wed, 5 Jan 2022 at 17:12, Jeremy Dyer wrote:
> I just tried removing the "S7" CASE WHEN portion and now it works.
I just tried removing the "S7" CASE WHEN portion and now it works. Why is
that however? Also just for version understanding my previous version was
Calcite 1.26.0 and this begins to occur at 1.27.0 so I would assume that
something in [1] diff would be the reason I just don't know where to look?
[1
Hi Jeremy,
Please log a JIRA case and attach the stacktrace. Apart from the query it
would help if you can provide the reproducer as a unit test in Calcite
(e.g., in RelOptRulesTest [1]).
Certain combinations of rules can lead to infinite rule matching.
Best,
Stamatis
[1]
https://github.com/apac
Hello,
I am experiencing a java.lang.StackOverFlowError in the HepPlanner [1]. The
error is occurring in a unit test that had been working for some time until
I recently upgraded to Calcite 1.29.0. It is very possible I am doing
something wrong in my planner configuration but I find it odd that it
