Remove datastore related code (#1906)

This commit is contained in:
Lai Jiang 2023-01-19 14:44:11 -05:00 committed by GitHub
parent 913edb23ee
commit e41fd7877e
152 changed files with 886 additions and 4460 deletions

View file

@ -582,7 +582,7 @@ that window, this flow allows the losing client to explicitly approve the
transfer request, which then becomes effective immediately.
When the transfer was requested, poll messages and billing events were saved to
Datastore with timestamps such that they only would become active when the
the database with timestamps such that they only would become active when the
transfer period passed. In this flow, those speculative objects are deleted and
replaced with new ones with the correct approval time.
@ -621,7 +621,7 @@ that window, this flow allows the gaining client to withdraw the transfer
request.
When the transfer was requested, poll messages and billing events were saved to
Datastore with timestamps such that they only would become active when the
the database with timestamps such that they only would become active when the
transfer period passed. In this flow, those speculative objects are deleted.
### Errors
@ -705,8 +705,8 @@ default five days) after which the transfer is automatically approved. Within
that window, the transfer might be approved explicitly by the losing registrar
or rejected, and the gaining registrar can also cancel the transfer request.
When a transfer is requested, poll messages and billing events are saved to
Datastore with timestamps such that they only become active when the
When a transfer is requested, poll messages and billing events are saved to the
database with timestamps such that they only become active when the
server-approval period passes. Keys to these speculative objects are saved in
the domain's transfer data, and on explicit approval, rejection or cancellation
of the request, they will be deleted (and in the approval case, replaced with
@ -1033,8 +1033,9 @@ An EPP flow for acknowledging {@link PollMessage}s.
Registrars refer to poll messages using an externally visible id generated by
{@link PollMessageExternalKeyConverter}. One-time poll messages are deleted from
Datastore once they are ACKed, whereas autorenew poll messages are simply marked
as read, and won't be delivered again until the next year of their recurrence.
the database once they are ACKed, whereas autorenew poll messages are simply
marked as read, and won't be delivered again until the next year of their
recurrence.
### Errors