"schemaCacheTTL" ParseServerOption is not working

[jack092123]

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.

[davimacedo]

@dplewis I actually don't see the schemaCacheTTL being used here: https://github.com/parse-community/parse-server/blob/e6ac3b6932186a6a85601c65143305f86f63e948/src/Controllers/SchemaCache.js

Thoughts?

[dplewis]

Check the constructor

[jack092123]

Hi @davimacedo @dplewis , is there any update?

The schemaCacheTTL was set to ttl at the constructor, but it doesn't pass to the cacheController at Line 33. I'm not sure is it the main problem here.

[davimacedo]

Check the constructor

The constructor uses only the default value but not a value eventually passed via parse server options, right?

[dplewis]

Should be passed here

parse-server/src/Config.js

Line 31 in e6ac3b6

const schemaCache = new SchemaCache(

[davimacedo]

@jack092123 would you mind to write a failing test case?

[jack092123]

Hi @davimacedo, this is my first time reporting issue & writing a test script. So feel free to correct me if there is a mistake.

I add a failing test case to my forked repo here. So what should I do next? Summit a pull request?
https://github.com/jack092123/parse-server/blob/issue7119/spec/SchemaCache.spec.js

[davimacedo]

Yes. You can open a PR with the test. Are you willed to also investigate and try to send a fix?

[parseplatformorg]

🎉 This change has been released in version 5.0.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 5.0.0