-
Notifications
You must be signed in to change notification settings - Fork 915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bigtable module only allows a single column family #1064
Labels
Comments
Thanks for catching this Israel, care to send a PR? We can do it together if you prefer. |
I am on it :) |
iht
added a commit
to iht/cloud-foundation-fabric
that referenced
this issue
Dec 22, 2022
iht
added a commit
to iht/cloud-foundation-fabric
that referenced
this issue
Dec 22, 2022
This commit fixes GoogleCloudPlatform#1064 by allowing to add more than one column family. Split keys are also now optional, and there is no possibility to set defaults for all tables (since keys and column families are related to the data and schema for each table, it is difficult that several tables share the same values). Also, declaring a table with no split keys nor column families requires initializing the table to an empty map, instead of using null.
iht
added a commit
to iht/cloud-foundation-fabric
that referenced
this issue
Dec 22, 2022
This commit fixes GoogleCloudPlatform#1064 by allowing to add more than one column family. Split keys are also now optional, and there is no possibility to set defaults for all tables (since keys and column families are related to the data and schema for each table, it is difficult that several tables share the same values). Also, declaring a table with no split keys nor column families requires initializing the table to an empty map, instead of using null.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A Bigtable table may contain more than one column family (tens and hundreds even). The current module implementation only creates the latest column family specified in the
tables
option.For instance:
The output of
tf plan
is:The output should be something like this:
The option
split_keys
should also be optional for each column family.The documentation of the resource
google_bigtable_table
specifies that the optioncolumn_family
can be specified several times.The text was updated successfully, but these errors were encountered: