I filed a JIRA for this: https://issues.apache.org/jira/browse/BEAM-12331
On Wed, May 12, 2021 at 12:53 PM Burkay Gur wrote:
> It looks to me like the `matches(RelOptRuleCall x)` function in
> BeamCalcRule is being skipped due to the logic here:
>
>
> https://github.com/apache/beam/pull/11975/f
It looks to me like the `matches(RelOptRuleCall x)` function in
BeamCalcRule is being skipped due to the logic here:
https://github.com/apache/beam/pull/11975/files#diff-919be1e4bcc11c17b725cbf04168b583886ffe16286f9291893247954128ad81R43
Below is more detail with the plans with and without the WH
The exception you shared is truncated so I am not sure the root cause of
this exception (it only shows the top which says BeamSql cannot convert the
query to a pipeline PTransforms).
Assuming you have basic knowledge of BeamSQL and Calcite. If you want to
contribute to analytics function, there is
If I'm understanding correctly, this query is taken from an existing test
[1], the only modification is the addition of "WHERE purchases > 3".
This seems like a bug -- I'm guessing the planner/matching logic doesn't
handle filters properly. To really figure out what's going on, you'd have
to compa
Hi folks,
When we try to run the following query on BeamSQL:
SELECT item, purchases, category, sum(purchases) over (PARTITION BY
category ORDER BY purchases ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT
ROW) as total_purchases FROM PCOLLECTION WHERE purchases > 3
We are getting the following err
