Just got off video chat with @tseaver and had some notes: - Why not just pass a different `Client` (instead of `timeout_seconds`) to API methods - ~~For the [`Row()` factory](http://gcloud-python-bigtable.readthedocs.org/en/latest/data-api.html#row-factory), need to document filter argument~~ 40b04fd06cc178a128319c4b0dda2b1b30515a52 - ~~Needed: Long-form about composing filters (like the one about GC rules: at [beginning](http://gcloud-python-bigtable.readthedocs.org/en/latest/column-family.html#column-families) of Column Families doc)~~ (https://github.com/GoogleCloudPlatform/gcloud-python/pull/1547) - Should we unify `commit()` and `commit_modifications()` on `Row()` into one method? - Worth using `Row()` as a context manager? (With `Row.commit()` on exit.) - Should `Row.delete_cells()` just default to `Row.ALL_COLUMNS`? (Is this dangerous to offer as a default?) - Would using properties on `Row()` for **conditional** mutations make things easier? E.g. `Row.true_muts.set_cell()` instead of `Row.set_cell(..., state=True)`.
Just got off video chat with @tseaver and had some notes:
Client(instead oftimeout_seconds) to API methodsFor the40b04fdRow()factory, need to document filter argumentNeeded: Long-form about composing filters (like the one about GC rules: at beginning of Column Families doc)(Adding Bigtable docs. googleapis/google-cloud-python#1547)commit()andcommit_modifications()onRow()into one method?Row()as a context manager? (WithRow.commit()on exit.)Row.delete_cells()just default toRow.ALL_COLUMNS? (Is this dangerous to offer as a default?)Row()for conditional mutations make things easier? E.g.Row.true_muts.set_cell()instead ofRow.set_cell(..., state=True).