[jira] [Commented] (BEAM-9210) Deprecate and remove "nested" schemas for pubsub tables

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-9210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174544#comment-17174544 ] 

Beam JIRA Bot commented on BEAM-9210:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Deprecate and remove "nested" schemas for pubsub tables
> -------------------------------------------------------
>
>                 Key: BEAM-9210
>                 URL: https://issues.apache.org/jira/browse/BEAM-9210
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Brian Hulette
>            Priority: P2
>              Labels: stale-P2
>
> Context: https://lists.apache.org/thread.html/bf4c37f21bda194d7f8c40f6e7b9a776262415755cc1658412af3c76%40%3Cdev.beam.apache.org%3E
> Currently we support two styles of schema in pubsub table definitions, a new "flattened" schema, as well as the original "nested" schema. The flattened style is preferred, but it currently provides no way to read or write pubsub message attributes, so switching over to it completely would be a regression.
> When flattened schemas support mapping to attributes, we should remove the nested style.



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