You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:04 UTC

[jira] [Updated] (BEAM-8593) Define expected behavior of running ZetaSQL query on tables with unsupported field types

     [ https://issues.apache.org/jira/browse/BEAM-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-8593:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> 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: Robin Qiu
>            Priority: P3
>              Labels: stale-assigned
>          Time Spent: 0.5h
>  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.20.1#820001)