Conversation
* feat: Add named database support * test: Use named db in system tests
|
I've updated these PRs and got the tests green. Seeking a go ahead for merging this. |
kolea2
left a comment
There was a problem hiding this comment.
LGTM after nits and pending approval from @googleapis/yoshi-python
|
Wait for #436 |
* Feat: Parametrize the tests for multidb support Remove "database" argument from Query and AggregationQuery constructors. Use the "database" from the client instead. Once set in the client, the "database" will be used throughout and cannot be re-set. Parametrize the tests where-ever clients are used. Use the `system-tests-named-db` in the system test. * Add test case for when parent database name != child database name * Update owlbot, removing the named db parameter * Reverted test fixes * fixing tests * fix code coverage * pr suggestion * address pr comments --------- Co-authored-by: Vishwaraj Anand <vishwaraj.anand00@gmail.com>
|
@Mariatta - how sure are we on regression here? (Support case now open) |
|
Hi @smittysmee, Please could you file a bug with sample code? Please include the versions of |
|
@parthea - it was a lack of backwards compatibility in a rollover and cache.
Entity A did not update with latest key structure containing added attribute |
|
@smittysmee by cache hit, it suggests to me that the issue is local to your environment? Pls confirm if that was not the case. |
The branch
multi-dbwas outdated. This PR makes it up to date withmainand contains the commit from #398.We will create the multi db test parametrization PR (#436) branch against this branch instead of
main.Once the feature is out of preview, we should:
main.