code: public static PTransform<PCollection<Mutation>, PDone> writeToTable(
        CloudBigtableTableConfiguration config) {
      DoFn<Mutation, Void> writeFn = new CloudBigtableSingleTableBufferedWriteFn(config);
      return new CloudBigtableWriteTransform<>(writeFn, config);
    }
docs: Creates a {@link PTransform} that can write either a bounded or unbounded {@link PCollection}
  of {@link Mutation}s to a table specified via a {@link CloudBigtableTableConfiguration}.
  
  <p>NOTE: This {@link PTransform} will write {@link Put}s and {@link Delete}s, not {@link
  org.apache.hadoop.hbase.client.Append}s and {@link org.apache.hadoop.hbase.client.Increment}s.
  This limitation exists because if the batch fails partway through, Appends/Increments might be
  re-run, causing the {@link Mutation} to be executed twice, which is never the user's intent.
  Re-running a Delete will not cause any differences. Re-running a Put isn't normally a problem,
  but might cause problems in some cases when the number of versions supported by the column
  family is greater than one. In a case where multiple versions could be a problem, it's best to
  add a timestamp to the {@link Put}.