Enhancement Request
As mentioned by @hoophalab in PR #104, projection support has been added within the query handler. The current timestamp and log level key search implementation can now be replaced by using this projection functionality.
Background
Currently, the IR stream reader performs timestamp and log level key searches separately. With the newly added projection support in the query handler, this can be refactored to use a more unified approach.
Proposed Enhancement
Refactor the existing timestamp and log level key search implementation to leverage the projection support within the query handler, which should:
- Improve code consistency: Use the same projection mechanism across the codebase
- Reduce code duplication: Eliminate separate search logic for timestamps and log levels
- Enhance maintainability: Centralize projection-related functionality
Context
This refactoring was discussed during the review of PR #104 for KQL filtering support. The KQL query UI delivery timeline requires this refactoring to be done in a future PR.
Requested by: @junhaoliao
Context: PR #104
Reference: Comment Thread
Enhancement Request
As mentioned by @hoophalab in PR #104, projection support has been added within the query handler. The current timestamp and log level key search implementation can now be replaced by using this projection functionality.
Background
Currently, the IR stream reader performs timestamp and log level key searches separately. With the newly added projection support in the query handler, this can be refactored to use a more unified approach.
Proposed Enhancement
Refactor the existing timestamp and log level key search implementation to leverage the projection support within the query handler, which should:
Context
This refactoring was discussed during the review of PR #104 for KQL filtering support. The KQL query UI delivery timeline requires this refactoring to be done in a future PR.
Requested by: @junhaoliao
Context: PR #104
Reference: Comment Thread