Skip to content
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

Add user TTL refresh #684

Open
data-sync-user opened this issue Apr 22, 2024 · 0 comments
Open

Add user TTL refresh #684

data-sync-user opened this issue Apr 22, 2024 · 0 comments
Assignees

Comments

@data-sync-user
Copy link
Collaborator

Bigtable requires a cell timestamp and family, which is used for automatic garbage collection for data. (Once all cells for a given key are removed, the key is also removed.) Each family can specify when data should be deleted. A cell family can have a TTL rule added which will take effect immediately on all existing cell timestamps.
We currently are writing cell timestamps for all cells, but have not activated automatic deletion for all families. This means that we may retain some data longer than necessary.

Mobile devices will check in once a day, but we can also use message hand-off to the bridge as a reasonable proxy for device “liveliness” (See https://docs.google.com/document/d/1M_zJ9P3LI_lfs1xrDapIY6OJMRwQPesXlxVpOK0fvPM/edit#heading=h.dwdigq1bm1w3 ). Desktop devices have far more active connections, but would still require timestamp refreshes.

We should consider creating some mechanism to update the associated cell timestamps once per 24 hours of activity for a given UAID. This would mean more writes per day (since we would be updating/duplicating cells) however this should not be a high cost.

┆Issue is synchronized with this Jira Task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants