Upgrading Cloud Bigtable Client Libraries

This page explains changes that you will need to make in your code when you upgrade from earlier versions of the Cloud Bigtable client libraries.

Java

Upgrading to 0.9.4

No special steps are necessary when upgrading from version 0.9.3 to version 0.9.4.

If you are upgrading from an earlier version, see the upgrade instructions for earlier versions below.

Upgrading to 0.9.3

No special steps are necessary when upgrading from version 0.9.2 to version 0.9.3.

If you are upgrading from an earlier version, see the upgrade instructions for earlier versions below.

Upgrading to 0.9.2

No special steps are necessary when upgrading from version 0.9.1 to version 0.9.2.

If you are upgrading from an earlier version, see the upgrade instructions for earlier versions below.

Upgrading to 0.9.1

With version 0.9.1, you must upgrade to version 1.1.33.Fork19 of the netty-tcnative-boringssl-static library.

In addition, you can use a single netty-tcnative-boringssl-static JAR file for all supported platforms (Linux, OS X, and Windows). You no longer need to use an OS-specific classifier in your Maven project. The following example shows how to add the required artifact to your pom.xml file:

<dependency>
  <groupId>io.netty</groupId>
  <artifactId>netty-tcnative-boringssl-static</artifactId>
  <version>1.1.33.Fork19</version>
</dependency>

Upgrading to 0.9.0

Version 0.9.0 changes the way you connect to Cloud Bigtable. Instead of specifying a cluster ID and zone, you specify an instance ID. You can find the instance ID by visiting the Google Cloud Platform Console.

Updating hbase-site.xml

If you use an hbase-site.xml file to connect to Cloud Bigtable, you must make the following changes:

  • Add the property google.bigtable.instance.id, with the value set to your instance ID.
  • Remove the property google.bigtable.cluster.name.
  • Remove the property google.bigtable.zone.name.

Updating BigtableConfiguration

If you connect to Cloud Bigtable by calling BigtableConfiguration.connect(), you must update your code as shown below:

// Old code
BigtableConfiguration.connect(projectId, zone, clusterId);

// New code
BigtableConfiguration.connect(projectId, instanceId);

Updating the Dataflow connector

If you use the Cloud Dataflow connector for Cloud Bigtable, you must update the code that creates a CloudBigtableScanConfiguration as shown below:

// Old code
CloudBigtableScanConfiguration config = new CloudBigtableScanConfiguration.Builder()
    .withProjectId("project-id")
    .withClusterId("cluster-id")
    .withZoneId("zone")
    .withTableId("table")
    .build();

// New code
CloudBigtableScanConfiguration config = new CloudBigtableScanConfiguration.Builder()
    .withProjectId("project-id")
    .withInstanceId("instance-id")
    .withTableId("table")
    .build();

Go

June 2016 changes

In June 2016, the Go client was updated to change the way you connect to Cloud Bigtable. Instead of specifying a cluster ID and zone, you specify an instance ID. You can find the instance ID by visiting the Google Cloud Platform Console.

You must update your code as shown below:

// Old code
adminClient, err := bigtable.NewAdminClient(ctx, project, zone, cluster)
client, err := bigtable.NewClient(ctx, project, zone, cluster)

// New code
adminClient, err := bigtable.NewAdminClient(ctx, project, instance)
client, err := bigtable.NewClient(ctx, project, instance)

Send feedback about...

Cloud Bigtable Documentation