Skip to content

enh: Add timerange expr type check and Relax the criteria for determi…#33220

Merged
dapan1121 merged 4 commits into3.0from
enh/3.0/ext-window
Nov 5, 2025
Merged

enh: Add timerange expr type check and Relax the criteria for determi…#33220
dapan1121 merged 4 commits into3.0from
enh/3.0/ext-window

Conversation

@Simon9997
Copy link
Contributor

…ning external windows.

Description

Please briefly describe the code changes in this pull request.

Checklist

Please check the items in the checklist if applicable.

  • Is the user manual updated?
  • Are the test cases passed and automated?
  • Is there no significant decrease in test coverage?

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Simon9997, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces an enhancement that improves the robustness of timerange expression handling by enforcing a timestamp type check. Concurrently, it relaxes the conditions for identifying external windows, which could lead to more flexible or efficient query planning and execution within the system.

Highlights

  • Timerange Expression Type Check: A type check has been added to the filterExtractTsNeedCollect function in parTranslater.c to ensure that expressions evaluated for timerange filtering are explicitly of TSDB_DATA_TYPE_TIMESTAMP.
  • Relaxed External Window Criteria: The criteria for determining external windows have been relaxed in the filterHasPlaceHolderRange function within planLogicCreater.c by removing a specific condition related to placeholder types, allowing for broader applicability.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces two enhancements: adding a type check for timerange expressions and relaxing the criteria for determining external windows. The changes appear correct and align with the PR's objectives. My review focuses on improving code readability and conciseness by simplifying boolean logic in both modified files.

@Simon9997 Simon9997 force-pushed the enh/3.0/ext-window branch 2 times, most recently from aae1f66 to fafa016 Compare October 13, 2025 08:28
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Simon9997
❌ dapan1121
You have signed the CLA already but the status is still pending? Let us recheck it.

@dapan1121 dapan1121 requested a review from a team as a code owner October 16, 2025 10:14
@dapan1121 dapan1121 merged commit d288994 into 3.0 Nov 5, 2025
10 of 11 checks passed
@minhuinie minhuinie deleted the enh/3.0/ext-window branch February 4, 2026 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants