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 2021/05/26 17:20:02 UTC
[jira] [Commented] (BEAM-11831) Remove duplicated Spanner client
configuration
[ https://issues.apache.org/jira/browse/BEAM-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351949#comment-17351949 ]
Beam JIRA Bot commented on BEAM-11831:
--------------------------------------
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.
> Remove duplicated Spanner client configuration
> ----------------------------------------------
>
> Key: BEAM-11831
> URL: https://issues.apache.org/jira/browse/BEAM-11831
> Project: Beam
> Issue Type: Task
> Components: io-java-gcp
> Reporter: Brian Hulette
> Priority: P2
> Labels: stale-P2
>
> The resolution for BEAM-11805 was to duplicate the default values from the Spanner client, and then modify them to include the updated spanner agent.
> Once there's a GCP bom release with a spanner client that fixes https://github.com/googleapis/java-spanner/pull/871 (4.0.0 release has it: https://github.com/googleapis/java-spanner/releases/tag/v4.0.0), we should upgrade to the new client and remove the duplicated code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)