|
| 1 | +# Bigtable Sink |
| 2 | + |
| 3 | +A Bigtable sink requires the following variables to be set along with Generic ones |
| 4 | + |
| 5 | +## `SINK_BIGTABLE_GOOGLE_CLOUD_PROJECT_ID` |
| 6 | + |
| 7 | +Contains information of google cloud project id of the bigtable table where the records need to be inserted/updated. Further |
| 8 | +documentation on google cloud [project id](https://cloud.google.com/resource-manager/docs/creating-managing-projects). |
| 9 | + |
| 10 | +* Example value: `gcp-project-id` |
| 11 | +* Type: `required` |
| 12 | + |
| 13 | +## `SINK_BIGTABLE_INSTANCE_ID` |
| 14 | + |
| 15 | +A Bigtable instance is a container for your data, which contain clusters that your applications can connect to. Each cluster contains nodes, compute units that manage your data and perform maintenance tasks. |
| 16 | + |
| 17 | +A table belongs to an instance, not to a cluster or node. Here you provide the name of that bigtable instance your table belongs to. Further |
| 18 | +documentation on [bigtable Instances, clusters, and nodes](https://cloud.google.com/bigtable/docs/instances-clusters-nodes). |
| 19 | + |
| 20 | +* Example value: `cloud-bigtable-instance-id` |
| 21 | +* Type: `required` |
| 22 | + |
| 23 | +## `SINK_BIGTABLE_CREDENTIAL_PATH` |
| 24 | + |
| 25 | +Full path of google cloud credentials file. Further documentation of google cloud authentication |
| 26 | +and [credentials](https://cloud.google.com/docs/authentication/getting-started). |
| 27 | + |
| 28 | +* Example value: `/.secret/google-cloud-credentials.json` |
| 29 | +* Type: `required` |
| 30 | + |
| 31 | +## `SINK_BIGTABLE_TABLE_ID` |
| 32 | + |
| 33 | +Bigtable stores data in massively scalable tables, each of which is a sorted key/value map. |
| 34 | + |
| 35 | +Here you provide the name of the table where the records need to be inserted/updated. Further documentation on |
| 36 | +[bigtable tables](https://cloud.google.com/bigtable/docs/managing-tables). |
| 37 | + |
| 38 | +* Example value: `depot-sample-table` |
| 39 | +* Type: `required` |
| 40 | + |
| 41 | +## `SINK_BIGTABLE_ROW_KEY_TEMPLATE` |
| 42 | + |
| 43 | +Bigtable tables are composed of rows, each of which typically describes a single entity. Each row is indexed by a single row key. |
| 44 | + |
| 45 | +Here you provide a string template which will be used to create row keys using one or many fields of your input data. Further documentation on [Bigtable storage model](https://cloud.google.com/bigtable/docs/overview#storage-model). |
| 46 | + |
| 47 | +In the example below, If field_1 and field_2 are `String` and `Integer` data types respectively with values as `alpha` and `10` for a specific record, row key generated for this record will be: `key-alpha-10` |
| 48 | + |
| 49 | +* Example value: `key-%s-%d, field_1, field_2` |
| 50 | +* Type: `required` |
| 51 | + |
| 52 | +## `SINK_BIGTABLE_COLUMN_FAMILY_MAPPING` |
| 53 | + |
| 54 | +Bigtable columns that are related to one another are typically grouped into a column family. Each column is identified by a combination of the column family and a column qualifier, which is a unique name within the column family. |
| 55 | + |
| 56 | +Here you provide the mapping of the table's `column families` and `qualifiers`, and the field names from input data that we intent to insert into the table. Further documentation on [Bigtable storage model](https://cloud.google.com/bigtable/docs/overview#storage-model). |
| 57 | + |
| 58 | +Please note that `Column families` being provided in this configuration, need to exist in the table beforehand. While `Column Qualifiers` will be created if they don't exist. |
| 59 | + |
| 60 | +* Example value: `{ "depot-sample-family" : { "depot-sample-qualifier-1" : "field_1", "depot-sample-qualifier-2" : "field_7", "depot-sample-qualifier-3" : "field_5"} }` |
| 61 | +* Type: `required` |
0 commit comments