[ 
https://issues.apache.org/jira/browse/BEAM-7070?focusedWorklogId=230293&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-230293
 ]

ASF GitHub Bot logged work on BEAM-7070:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Apr/19 22:33
            Start Date: 19/Apr/19 22:33
    Worklog Time Spent: 10m 
      Work Description: amaliujia commented on pull request #8301: [BEAM-7070] 
JOIN condition should accept field access
URL: https://github.com/apache/beam/pull/8301#discussion_r277105959
 
 

 ##########
 File path: 
sdks/java/testing/nexmark/src/test/java/org/apache/beam/sdk/nexmark/queries/QueryTest.java
 ##########
 @@ -188,12 +188,14 @@ public void query5MatchesModelStreaming() {
 
   @Test
   @Category(NeedsRunner.class)
+  @Ignore("https://jira.apache.org/jira/browse/BEAM-7072";)
 
 Review comment:
   I see. I will explore a general way to supports these: equi-join, AND/OR, 
function call/operators, Column Ref and FieldAccess. 
   
   
   There are no tests to test rejections of unsupported JOIN. I will add some.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 230293)
    Time Spent: 5h 20m  (was: 5h 10m)

> JOIN condition should accept field access
> -----------------------------------------
>
>                 Key: BEAM-7070
>                 URL: https://issues.apache.org/jira/browse/BEAM-7070
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Rui Wang
>            Assignee: Rui Wang
>            Priority: Major
>          Time Spent: 5h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to