This repository was archived by the owner on Nov 7, 2025. It is now read-only.
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.
An attempt to introduce unique object IDs in the ClickHouse realm.
A returned document id (
_idfield) would have the following syntax:Of course, the
{hex-encoded hash of the document}lives only in Quesma memory:Therefore when fetching document with specific
_idwe could filter out documents with matching timestamp and then filter for that with matching fields, returning the right entry.This fixes the issue, where JSON view of single document could return a random object from search hits, not necessarily the one clicked.

However (and it's a pretty big however), the "surrounding document" view cannot return the surrounding documents. While the query doesn't error it also doesn't return any documents. The experiment to have that working is carried out is a separate PR, although it's not clear yet if this way of doing things is going to guarantee 100% correctness.