beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blaquiere Guillaume (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-3632) Table partioning in DynamicDestination is lost with project is not set in Table Destination
Date Tue, 06 Feb 2018 22:29:00 GMT

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

Blaquiere Guillaume commented on BEAM-3632:
-------------------------------------------

Pull request: https://github.com/apache/beam/pull/4622

> Table partioning in DynamicDestination is lost with project is not set in Table Destination
> -------------------------------------------------------------------------------------------
>
>                 Key: BEAM-3632
>                 URL: https://issues.apache.org/jira/browse/BEAM-3632
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Blaquiere Guillaume
>            Assignee: Chamikara Jayalath
>            Priority: Major
>   Original Estimate: 10m
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the following class https://github.com/apache/beam/tree/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/*WriteTables.java*
> line 140
> When the project is not set in table name, a new TableDestination is created but all
the time partitioning parameter is lost.
> Fix is very easy. Add a get time partitioning on the new creation:
>  tableDestination = new TableDestination(tableReference, tableDestination.getTableDescription()*{color:#ff0000},tableDestination{color}**{color:#ff0000}.getTimePartitioning(){color}*);
>   
>  Should be enought :P



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

Mime
View raw message