Adding ClickHouse as an alternative to Elasticsearch #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KaliszS
requested changes
Sep 4, 2025
Collaborator
KaliszS
left a comment
There was a problem hiding this comment.
Thanks your your pull request! Really appreciate and can't wait for the next update :)
KaliszS
requested changes
Sep 8, 2025
KaliszS
approved these changes
Sep 8, 2025
czajkub
added a commit
that referenced
this pull request
Sep 8, 2025
Resolves issues after merging #14 into main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ClickHouse support
This pull requests adds support for ClickHouse as an alternative to Elasticsearch (issue #13). The way it works now, the end user needs to set up elasticsearch in a docker container before connecting to the mcp server, while ClickHouse works in-memory, so it saves time and effort during setup while also offering similar (if not better) waiting times as elasticsearch, as supported by the screenshots.
The tools provided are exactly mirroring the 4 tools provided already by elasticsearch, returning data in a JSON format to the server.
What lacks so far is the config and launching the server - currently, the user has no way of specifying the path to his .xml export file or choosing the name of his database/table. Another thing to consider is the setup - as it stands, the user has to run the
app/services/ch.pyfile to index their data into the database, although there are plans to address this issue in the future.