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

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

                Author: ASF GitHub Bot
            Created on: 14/Jan/20 06:56
            Start Date: 14/Jan/20 06:56
    Worklog Time Spent: 10m 
      Work Description: stale[bot] commented on issue #10020: [BEAM-8593] 
Remove testSelectFromTableWithMap from ZetaSQLDialectSpecTest
URL: https://github.com/apache/beam/pull/10020#issuecomment-574031658
 
 
   This pull request has been closed due to lack of activity. If you think that 
is incorrect, or the pull request requires review, you can revive the PR at any 
time.
   
 
----------------------------------------------------------------
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:
us...@infra.apache.org


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

    Worklog Id:     (was: 371389)
    Time Spent: 20m  (was: 10m)

> Define expected behavior of running ZetaSQL query on tables with unsupported 
> field types
> ----------------------------------------------------------------------------------------
>
>                 Key: BEAM-8593
>                 URL: https://issues.apache.org/jira/browse/BEAM-8593
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql-zetasql
>            Reporter: Yueyang Qiu
>            Assignee: Yueyang Qiu
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> What should be the expected behavior if a user run a ZetaSQL query on a table 
> with a field type (e.g. MAP) that is not supported by ZetaSQL?
> More context: 
> [https://github.com/apache/beam/pull/10020#issuecomment-551368105]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to