Hi Luke,
My understanding is that lookup files as a knowledge object do get replicated in a search head clustered environment. However, based on the above response, is it correct to state that lookup files modified via lookup editor do not get replicated in the cluster ?
We currently use lookups to store our application configurations, some of which could be modified by the end users. As you have mentioned, using a kvstore could be an option if we need replication, but the lookup editor app provides a very user friendly interface to modify values and hence achieving similar thing for kvstore would mean developing all of that.
Are there options that we could think of to continue to use lookups (and modify them via lookup editor and replicate them in the cluster) ? Here are few thoughts. Please let me know if it makes sense:
1. Once the lookups are modified, can they be pushed programatically to the deployer and invoke a script to replicate across all search heads ? If you have some idea about this, please do share.
2. As per the documentation REST API calls are replicated, so is it possible that once the lookup is modified, we trigger a REST API call to do something like :
|inputlookup | outputlookup . Would this then be actually considered for replication ?
3. Would it work if we enable lookup editor app in deployer itself and modify the changes there and push it to other components ? am not sure if the deployer can provide a web interface for this. Please do confirm.
Regards
Keshav
... View more