beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-3417) Fix Calcite assertions
Date Wed, 09 May 2018 19:10:00 GMT


ASF GitHub Bot logged work on BEAM-3417:

                Author: ASF GitHub Bot
            Created on: 09/May/18 19:09
            Start Date: 09/May/18 19:09
    Worklog Time Spent: 10m 
      Work Description: apilloud commented on issue #5318: [BEAM-3417] Fix calcite assertions
   run java precommit

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 100218)
    Time Spent: 40m  (was: 0.5h)

> Fix Calcite assertions
> ----------------------
>                 Key: BEAM-3417
>                 URL:
>             Project: Beam
>          Issue Type: Task
>          Components: dsl-sql
>            Reporter: Anton Kedin
>            Assignee: Andrew Pilloud
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
> 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

View raw message