We recently tried to turn on vsf api cache for some of our vsf magento2 powered stores.
We found that the module we pulled via composer (divante/magento2-vsbridge-indexer : 2.0.1) does contain the required cache invalidation processors from version 1 (for es5), but the corresponding trigger or class calls containing them have been removed.
Our Question: Was there a reason not to include them in the version or was something simply forgotten or postponed until later?
For us, the feature is now essential. As long as it is not available, we have to make do with the Redis TTL configuration in the VSF Api or FE instances.
An OnUpdate trigger when saving data in Magento would of course make much more sense (and was probably once thought of that way).
Thanks for your help
And Thankyou for your work! The vsf-bridge module and your vsf stack in general is great nonetheless!
Magento: v2.3.6 Elasticsearch: v7.4
We recently tried to turn on vsf api cache for some of our vsf magento2 powered stores.
We found that the module we pulled via composer (divante/magento2-vsbridge-indexer : 2.0.1) does contain the required cache invalidation processors from version 1 (for es5), but the corresponding trigger or class calls containing them have been removed.
Our Question: Was there a reason not to include them in the version or was something simply forgotten or postponed until later?
For us, the feature is now essential. As long as it is not available, we have to make do with the Redis TTL configuration in the VSF Api or FE instances.
An OnUpdate trigger when saving data in Magento would of course make much more sense (and was probably once thought of that way).
Thanks for your help And Thankyou for your work! The vsf-bridge module and your vsf stack in general is great nonetheless!