Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@cyyeh
Copy link
Member

@cyyeh cyyeh commented Jul 3, 2025

Summary by CodeRabbit

  • Documentation

    • Updated SQL generation rules to clarify that the "EXTRACT()" function cannot be used with INTERVAL data types.
  • New Features

    • Enhanced support for constructing history messages from both object and dictionary formats in the ask history feature.

@cyyeh cyyeh requested a review from yichieh-lu July 3, 2025 07:06
@cyyeh cyyeh added module/ai-service ai-service related ci/ai-service ai-service related labels Jul 3, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 3, 2025

Walkthrough

The SQL generation rules documentation was updated to forbid the use of the EXTRACT() function with INTERVAL data types. Additionally, the function for constructing ask history messages was modified to accept both AskHistory objects and dictionaries, adjusting its logic to handle both data structures accordingly.

Changes

File(s) Change Summary
wren-ai-service/src/pipelines/generation/utils/sql.py Updated SQL rules documentation to disallow EXTRACT() on INTERVAL; modified function to accept and process both AskHistory objects and dictionaries for message construction.

Poem

In the land of SQL, new rules now apply,
No EXTRACT on INTERVALβ€”just pass it by!
Histories now blend, both dict and class,
Messages constructed, no matter their past.
A hop and a skip, the code’s feeling spry!
πŸ‡βœ¨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

πŸ”§ Pylint (3.3.7)
wren-ai-service/src/pipelines/generation/utils/sql.py
✨ Finishing Touches
  • πŸ“ Generate Docstrings
πŸ§ͺ Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in a Comment
  • Commit Unit Tests in branch chore/ai-service/improve-text2sql

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share
πŸͺ§ Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
wren-ai-service/src/pipelines/generation/utils/sql.py (1)

468-485: Consider improving type safety and error handling.

The function modification adds flexibility to handle both AskHistory objects and dictionaries, but the current implementation has some potential issues:

  1. Mixed list handling: The function doesn't explicitly handle cases where the list contains both AskHistory objects and dictionaries
  2. Error handling: If an item is neither an AskHistory object nor a dictionary with the required keys, it will raise a KeyError
  3. Type safety: Using hasattr for duck typing works but isinstance checks would be more explicit

Consider this more robust implementation:

def construct_ask_history_messages(
    histories: list[AskHistory] | list[dict],
) -> list[ChatMessage]:
    messages = []
    for history in histories:
-        messages.append(
-            ChatMessage.from_user(
-                history.question
-                if hasattr(history, "question")
-                else history["question"]
-            )
-        )
-        messages.append(
-            ChatMessage.from_assistant(
-                history.sql if hasattr(history, "sql") else history["sql"]
-            )
-        )
+        if isinstance(history, AskHistory):
+            question = history.question
+            sql = history.sql
+        elif isinstance(history, dict):
+            question = history["question"]
+            sql = history["sql"]
+        else:
+            raise TypeError(f"Expected AskHistory or dict, got {type(history)}")
+        
+        messages.append(ChatMessage.from_user(question))
+        messages.append(ChatMessage.from_assistant(sql))
    return messages
πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 7c6355c and 84e15ab.

πŸ“’ Files selected for processing (1)
  • wren-ai-service/src/pipelines/generation/utils/sql.py (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
πŸ““ Common learnings
Learnt from: wwwy3y3
PR: Canner/WrenAI#1585
File: wren-ui/src/pages/api/v1/generate_sql.ts:98-106
Timestamp: 2025-04-24T16:10:43.308Z
Learning: In the generate_sql API, allow users to specify language codes not predefined in the WrenAILanguage enum, passing them through directly rather than strictly validating against the enum.
wren-ai-service/src/pipelines/generation/utils/sql.py (1)
Learnt from: wwwy3y3
PR: Canner/WrenAI#1585
File: wren-ui/src/pages/api/v1/generate_sql.ts:98-106
Timestamp: 2025-04-24T16:10:43.308Z
Learning: In the generate_sql API, allow users to specify language codes not predefined in the WrenAILanguage enum, passing them through directly rather than strictly validating against the enum.
🧬 Code Graph Analysis (1)
wren-ai-service/src/pipelines/generation/utils/sql.py (1)
wren-ai-service/src/web/v1/services/ask.py (1)
  • AskHistory (16-18)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: pytest
  • GitHub Check: pytest
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (go)
πŸ”‡ Additional comments (1)
wren-ai-service/src/pipelines/generation/utils/sql.py (1)

209-209: LGTM! Good addition to SQL constraints.

The new rule appropriately forbids the use of EXTRACT() function with INTERVAL data types, which aligns with the existing constraint pattern and helps prevent potential SQL generation issues.

@cyyeh cyyeh merged commit bd04884 into main Jul 3, 2025
15 checks passed
@cyyeh cyyeh deleted the chore/ai-service/improve-text2sql branch July 3, 2025 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci/ai-service ai-service related module/ai-service ai-service related wren-ai-service

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants