[
https://issues.apache.org/jira/browse/BEAM-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Kedin updated BEAM-3417:
------------------------------
Description:
Currently we disable assertions in test for every project which depends on Beam
SQL / Calcite. Otherwise it fails assertions when Calcite validates relational
representation of the query. E.g. in projects which depend on Beam SQL /
Calcite we have to specify
{code:java|title=build.gradle}
test {
jvmArgs "-da"
}
{code}
We need to either update our relational conversion logic or come up with some
other solution so that we don't have to disable assertions globally. If it's an
incorrect assertion in Calcite then we need to fix it there.
was:
Currently we disable assertions in test for every project which depends on Beam
SQL / Calcite. Otherwise it fails assertions when Calcite validates relational
representation of the query. E.g. in `build.gradle` you have to specify
```java
test {
jvmArgs "-da"
}
```
We need to either update our relational conversion logic or come up with some
other solution so that we don't have to disable assertions globally.
> Fix Calcite assertions
> ----------------------
>
> Key: BEAM-3417
> URL: https://issues.apache.org/jira/browse/BEAM-3417
> Project: Beam
> Issue Type: Task
> Components: dsl-sql
> Reporter: Anton Kedin
> Assignee: Xu Mingmin
>
> Currently we disable assertions in test for every project which depends on
> Beam SQL / Calcite. Otherwise it fails assertions when Calcite validates
> relational representation of the query. E.g. in projects which depend on Beam
> SQL / Calcite we have to specify
> {code:java|title=build.gradle}
> test {
> jvmArgs "-da"
> }
> {code}
> We need to either update our relational conversion logic or come up with some
> other solution so that we don't have to disable assertions globally. If it's
> an incorrect assertion in Calcite then we need to fix it there.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
