Hi Aspen, if the issue has been fixed on Calcite's side, it is waiting for an overdue upgrade of the Calcite version Beam uses (tracked by [1]). Currently Beam depends on Calcite 1.20, and it looks like that issue was fixed in Calcite 1.21 [2].
[1] https://issues.apache.org/jira/browse/BEAM-9379 [2] https://issues.apache.org/jira/browse/CALCITE-3237 On Tue, Dec 15, 2020 at 6:12 PM Ahmet Altay <al...@google.com> wrote: > +Andrew Pilloud <apill...@google.com> +Robin Qiu <robi...@google.com> > > > On Tue, Dec 15, 2020 at 12:42 PM Aspen Barnes <wbar...@etsy.com> wrote: > >> Hello, I have recently encountered an issue with BeamSql queries against >> complex data structures. See >> https://issues.apache.org/jira/browse/BEAM-11140 for info. Essentially, >> the query code generation is failing past a certain depth, which is not >> hard to achieve with subqueries and nested data structures. Is there any >> chance this issue could be fixed? It seems as though it has been solved on >> Calcite's side. >> >> Aspen Barnes >> Security Engineer II >> Pronouns | they/them >> Etsy >> >
