-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] clp-package: Pass search arguments via msgpack object instead of command line to search processes. #421
base: main
Are you sure you want to change the base?
Conversation
e5307cd
to
81db451
Compare
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Description
This PR modifies clp-s and clo to pass most search arguments via a msgpack object written to stdin instead of via command line arguments. This allows the
fs_search_task
python wrapper to be less smart, and makes it easier to change the arguments passed to our search processes -- now we just need to modify theSearchConfig
object injob_config.py
and make clo/clp-s use the new fields directly.The diff is somewhat large, but mostly consists of simple changes to the
CommandLineArguments
classes of clp-s and clo to take config from a msgpack object instead of from command line arguments.We also change the search scheduler to make it augment the
SearchConfig
object with a mongodb output destination when no other output destination is specified. Having the mongodb output destination configured explicitly before the search job gets passed downstream allows downstream components to be less smart, and adding the mongodb output destination needs to happen inside the scheduler to follow our current convention that the job id is the result collection name.Validation performed