-
Notifications
You must be signed in to change notification settings - Fork 178
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
Shouldn't Cluster.hdd_bytes and Cluster.ssd_bytes be in a oneof block? #366
Comments
/cc @coryoconnor @carterpage @maxluebbe -- Can a Bigtable cluster have both |
The cluster api is not currently enabled. There will be some iteration on it. This fields are likely to not be used any time soon, prefer using only default_storage_type instead. Right now clusters are only created via the UI and a cluster can only be SSD. In the future we plan to enable HDD clusters, and maybe one day mixed HDD and SSD in the same cluster, which would make these fields meaningful. |
OK. This leads to a second question. If we were to send a pull request to modify these protos, would it be worthwhile? Or is this "read-only" open source that will have changes blasted out during some sync job? |
Thanks for the reply @mgarolera ! Regarding
I have been able to use it (with a user account, not with a service account) when enabling the "Cloud Bigtable Table Admin API" in the APIs console. See googleapis/google-cloud-python#872 for discussion. @jgeewax It doesn't seem we'd want to make a PR for this issue. |
@jgeewax: Yes, there protos are not yet the authoritative source and a change would be overwritten. |
Thanks @sduskis! |
I'm implementing the Python library for the API and noticed that both
hdd_bytes
andssd_bytes
can be set on aCreateCluster
call (and they persist when callingGetCluster
).Shouldn't the values (in the
Cluster
message class) be in aoneof
block:The text was updated successfully, but these errors were encountered: