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.
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
feat: Support search logs by timestamp for structured and unstructured logs. #42
base: main
Are you sure you want to change the base?
feat: Support search logs by timestamp for structured and unstructured logs. #42
Changes from all commits
ea23947
7edaa48
7481573
3ee05a2
f1a71a1
5263385
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we discussed offline that there would be some changes in both clp-ffi-js and ylv to return a nullable-integer instead, we ended up with a temporary conclusion that using a const value
-1
was sufficient to indicate that no matching log event can be found.However, returning
null
may only seem necessary now I realize that we have been (implicitly) usingsize_t
as the type ofLogEventIdx
and such values are always non-negative. Can we declare a TS type and change the return type to it? You may refer to toFilteredLogEventMapTsType
for such type declarations and usages; let me know if you need more help.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to check against
m_deserialized_log_events->empty()
at the beginning of the method and early return, so that we can avoid checkingit == m_deserialized_log_events->end() && it == m_deserialized_log_events->begin()
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use
std::range::upper_bound
instead and alwaysit--
after, so that we can avoid checking(it == m_deserialized_log_events->end() || it->get_timestamp() > input_timestamp)
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's deduplicate this with
StructuredIrStreamReader::find_timestamp_last_occurrence
.You may refer to
generic_decode_range
.