You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I create an index with TTL through the web interface and inspect it, the parameter "expireAfterSeconds"
has its value as String no Int. This causes that docs that should be deleted are not.
Expected Behavior
Use the web interface to create an Index with TTL and inspect it, the "expireAfterSeconds" should be an Int.
If you create the index through "Collections" and select "createIndex", the index is created correctly.
alexandre-slp
changed the title
TTL indexes are created with "expireAfterSeconds" as string not int
TTL indexes are created with "expireAfterSeconds" as String not Int
Oct 7, 2020
Thanks for reporting this @alexandre-slp I don't know how such a bug couldn't be found earlier. Also interestingly MongoDB nodejs driver accepts it as a string somehow 🤔
Fixed, as soon as build finished I'll also prepare the hotfix release.
When I create an index with TTL through the web interface and inspect it, the parameter "expireAfterSeconds"
has its value as String no Int. This causes that docs that should be deleted are not.
Expected Behavior
Use the web interface to create an Index with TTL and inspect it, the "expireAfterSeconds" should be an Int.
You should see something like this:
Current Behavior
Use the web interface to create an Index with TTL and inspect it, the "expireAfterSeconds" and its a String.
You will see something like this:
Steps to Reproduce
Context
Docs that should be deleted after the TTL are not.
Your Environment
The text was updated successfully, but these errors were encountered: