Cache Parameter Metadata#1845
Conversation
…p to ConcurrentHashMap
…r on test setup method.
| * @return true, if the metadata for the query can be retrieved | ||
| * | ||
| */ | ||
| static boolean getQueryMetadata(Parameter[] params, ArrayList<String> parameterNames, |
There was a problem hiding this comment.
we don't need all these static methods this takes up memory. The caller should create an instance of the cache and invoke the methods
… alongside the error code.
…s problems, test will still correctly assess the error code path in ParameterMetaDataCache
345ef9f
|
@Jeffery-Wasty this is an exciting change! Thank you for working on it!
|
|
Hi @alex-bochkov, We'll be releasing documentation regarding new features shortly, in the meantime I can answer the questions you have included: 1. What's the cache TTL? The cache doesn't have an independent TTL, rather the enclave session it belongs to has a TTL of eight hours. 2. Is it possible to disable cache if needed? For example, if we need to make schema changes and make sure the app won't break in the middle. It's not possible to disable the cache at the moment. This is something we can potentially add a later time, however current efforts are towards extending caching for secure enclave scenarios. |
Cache sp_describe_parameter_encryption calls to improved performance by reducing trips to the server. For now, supports AE without secure enclaves, with enclave support (v3) to be added in a later update.