Hey Nick, thanks for confirming! If possible, it would be great to share a few more details, like what was the misconfig and how you fixed it (while the symptoms are already described in the first message).
Saying this because our dev-list is also part of the project documentation, your example can help others in the future. Best regards, Alessandro On Fri, 4 Aug 2023 at 01:33, Nick Riasanovsky <n...@bodo.ai> wrote: > Thank you for your response. There was an issue with my configuration that > I was able to resolve. > > On Thu, Aug 3, 2023 at 4:33 PM Julian Hyde <jhyde.apa...@gmail.com> wrote: > > > The constraints on a RelSubset should be the union of the constraints of > > all of the RelNodes in that subset. (I haven’t tested it, or read the > code. > > But if it doesn’t do that, you’re probably seeing a bug, or you haven’r > > configured your metadata providers correctly.) > > > > > On Aug 3, 2023, at 9:33 AM, Nick Riasanovsky <n...@bodo.ai> wrote: > > > > > > Hello everyone, > > > > > > I am attempting to use AggregateProjectPullUpConstantsRule within an > > > optimizer that is using the VolcanoPlanner. When doing so I encounter > > > issues with what should be valid constants on the line > > > `mq.getPulledUpPredicates()` because aggregate.getInput() is a > RelSubset. > > > As a result, the predicates list is always empty. If I replace the uses > > of > > > aggregate.getInput() with input then everything works as expected. > > > > > > I am happy to submit a PR upstream with this fix, but I first want to > > > confirm that my interpretation is correct as I am relatively new to > using > > > the volcano planner and could have missed a configuration step. > > > > > > Thanks everyone, > > > Nick Riasanovsky > > > > >
