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

Ismaël Mejía updated BEAM-3632:
-------------------------------
    Fix Version/s: 2.4.0

> 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: io-java-gcp
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Blaquiere Guillaume
>            Assignee: Chamikara Jayalath
>            Priority: Major
>             Fix For: 2.4.0
>
>   Original Estimate: 10m
>          Time Spent: 1h 20m
>  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)

Reply via email to