Skip to content

Conversation

@dconeybe
Copy link
Contributor

This PR reverts #1044, which disabled the test aggregateQueryInATransactionShouldRespectReadTime because of a known issue: b/220918135 (When creating a new read-only or read-write transaction, the Firestore emulator creates the transaction at the current time regardless of the user's specified TransactionsOptions. In the case of read-only transaction, if the user specifies the read_time, that will not be honoured. If the user specifies a retry_transaction, that will not be honored).

The issue has been confirmed fixed in cloud-firestore-emulator-v1.15.1.jar, so skipping the test is no longer required. This PR re-enables the test when run against he Firestore Emulator.

@dconeybe dconeybe added the api: firestore Issues related to the googleapis/java-firestore API. label Sep 30, 2022
@dconeybe dconeybe self-assigned this Sep 30, 2022
@dconeybe dconeybe requested a review from a team as a code owner September 30, 2022 14:48
@dconeybe dconeybe requested a review from ehsannas September 30, 2022 14:51
@dconeybe
Copy link
Contributor Author

Meh, I'm just going to merge this. Don't worry about the code review.

@dconeybe dconeybe merged commit 558db75 into dconeybe/CountRelease Sep 30, 2022
@dconeybe dconeybe deleted the dconeybe/ReEnableAggregateQueryInATransactionShouldRespectReadTimeOnEmulator branch September 30, 2022 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: firestore Issues related to the googleapis/java-firestore API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants