beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Romanenko (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (BEAM-3539) BigtableIO.Write javadoc of some methods is incorrect
Date Fri, 26 Jan 2018 09:53:00 GMT

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

Alexey Romanenko reassigned BEAM-3539:
--------------------------------------

    Assignee: Alexey Romanenko

> BigtableIO.Write javadoc of some methods is incorrect
> -----------------------------------------------------
>
>                 Key: BEAM-3539
>                 URL: https://issues.apache.org/jira/browse/BEAM-3539
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-gcp
>    Affects Versions: 2.2.0
>            Reporter: Alexey Romanenko
>            Assignee: Alexey Romanenko
>            Priority: Trivial
>             Fix For: 2.3.0
>
>
> Some methods in BigtableIO.Write have wrong javadoc which says that it returns new
instance of BigtableIO.Read.
> For example:
>  
> {code:java}
> /**
>  * Returns a new {@link BigtableIO.Read} that will write into the Cloud Bigtable project
>  * indicated by given parameter, requires {@link #withInstanceId}
>  * to be called to determine the instance.
>  *
>  * <p>Does not modify this object.
>  */
> public Write withProjectId(ValueProvider<String> projectId) {...}
> {code}
>  
> Actually, it returns new BigtableIO.Write



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

Mime
View raw message