-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Closed
Labels
state:releasedReleased as stable versionReleased as stable versionstate:released-betaReleased as beta versionReleased as beta versiontype:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Issue Description
It seems schemaCacheTTL ParseServerOption is not working. It still follows cacheAdapter's setting.
Steps to reproduce
ParseOption
enableSingleSchemaCache: true,
schemaCacheTTL: 3600000, (1hr)
cacheAdapter: RedisCacheAdapter
Actual Outcome
After a simple request, I check the keys in Redis. The schema cache's TTL is 30 seconds which is the RedisCacheAdapter's default TTL.
Environment
Server
- Parse Server version:
4.3.0 - Operating system:
MacOS - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
Local
Database
- System (MongoDB or Postgres):
MongoDB - Database version:
3.6 - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
Local
I'm not quite sure, but I think the problem might be here. It doesn't pass the TTL config to the cache.
Metadata
Metadata
Assignees
Labels
state:releasedReleased as stable versionReleased as stable versionstate:released-betaReleased as beta versionReleased as beta versiontype:bugImpaired feature or lacking behavior that is likely assumedImpaired feature or lacking behavior that is likely assumed