epic: clickhouse for elastic search on jsonb fields starting code from transaction details #454
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
0xneves
added
type: feature request
0xneves
changed the title
Contributor
Author
|
Maybe we should make this a totally separated product, because this defies how PostgreSQL works. Maybe a fully indexer of its own would make more sense. |
Contributor
Author
|
Closing in favor of optimizing the code field rather than making an elastic indexer for search with code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NOTE: This is an experimental feature that requires time and sensitive attention that could boost significantly the queries that uses search on jsonb fields.
This is an epic feature that is basically storing in an ES-like indexer whatever data we want to aid queries that rely on searching jsonb fields like code, result, data, etc. It should not affect the normal workflow of the indexer by any means, it's like a regex search on huge string fields on steroids.
It is fully optional based on env vars, and it affects:
And it has its own backfill for already running indexers.