You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/11/02 17:11:00 UTC

[jira] [Commented] (BEAM-10851) Determine Spanner schema at pipeline construction in cross-language SpannerIO

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

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

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.


> Determine Spanner schema at pipeline construction in cross-language SpannerIO
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-10851
>                 URL: https://issues.apache.org/jira/browse/BEAM-10851
>             Project: Beam
>          Issue Type: Improvement
>          Components: cross-language, io-java-gcp, io-py-gcp
>            Reporter: Piotr Szuberski
>            Priority: P2
>              Labels: stale-P2
>
> For now Spanner's cross-language transform requires to get Beam Schema. It should be possible to determine the schema otherwise.
> One solution would be to execute query with spanner client and then translate spanner schema to beam schema. But this is very poor solution as the query would be executed twice.
> Look for it at SpannerTransformRegistrar.ReadBuilder



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