-
Notifications
You must be signed in to change notification settings - Fork 385
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
🐛 [firestore-send-email] delete email documents on TTL expire #1946
Comments
I was wondering if it's possible to create a TTL Policy for a 2nd level field by specifying the timestamp field with dot notation, such as "delivery.expireAt". However, if setting the TTL manually is required, I believe it would be beneficial to include this information in the documentation. Unfortunately, I could not find any related instructions. Could you please clarify this? |
its not much help but this works for us. using |
Indeed, a TTL policy with |
Documents updated explaining how to add the TTL policy properly. Apologies for the lack of information before. New documents will be merged shortly. |
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs for a specific extension in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
with the firebase tag.
google group.
Firebase support directly.
[REQUIRED] Step 2: Describe your configuration
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Expected result
The documents in the configured collection are expected to be deleted automatically.
Actual result
The documents are never deleted.
Please note, that it is not even possible to manually set up a TTL policy, because expireAt field is at 2nd level in the document created by the plugin, however, only 1st level fields can be configure as timestamp field when creating a TTL policy (see https://console.cloud.google.com/firestore/databases/-default-/ttl)
Example document:
The text was updated successfully, but these errors were encountered: