Allow tables with several column families in Bigtable #1069
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A table in Bigtable can have more than one column family (or none), and
split_keys
is optional forgoogle_bigtable_table
resources.This PR fixes #1064. It lets the user specify 0 or more column families for each table, and makes
split_keys
an optional parameter for each declared table.Because column families are schema properties of a Bigtable table and
split_keys
are related to the actual values stored in a table, I don't think it makes sense to speak of default settings for those properties, and I have removed that option from this module. Now users should specify (or not)column_families
andsplit_keys
for each one of the declared tables.The default value for a table with no additional options was
null
. I have changed that to an empty map{}
so the default values of the correspondingoptional
parameters are used.