Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Disabling elastic search and indexing
See original GitHub issueI looked through some of the existing issues opened and some indicated that it was not possible to disable use of elastic search (https://github.com/Netflix/conductor/issues/668), while others imply that indexing is optional (https://github.com/Netflix/conductor/issues/1087 and https://github.com/Netflix/conductor/issues/181).
What exactly is the process of disabling indexing and elastic search?
1 ) Is there a configuration flag I can pass?
2) Do I have to extend IndexDAO that does nothing, and rebuild conductor from source?
3) Can I simply use an in-memory indexing, i.e. https://github.com/Netflix/conductor/blob/master/docker/server/config/config-local.properties#L38? It seems indexing is not useful for any of conductor’s core functions, besides search abilities?
Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@kyle--lee It is not advised to use in-memory indexing for your production usage, this should only be used for testing purposes.
Thanks for the quick reply!