⚡ Bolt: Defer heavy columns in issue deduplication queries

[RohanExploit]

⚡ Performance Optimization

What:
Deferred action_plan, image_path, and location columns in create_issue (deduplication logic) and get_nearby_issues queries.

Why:
These endpoints fetch lists of issues to check for duplicates or display on a map. The action_plan field is a large JSON blob stored as TEXT, and image_path can be long. Fetching these for every candidate issue in a bounding box (even if filtered later by distance) wastes memory and DB bandwidth.

Impact:

• Reduces memory footprint for deduplication checks in dense areas.
• Reduces payload size from DB to App.
• Prevents loading of unused data.

Verification:

• Verified with a reproduction test case that the endpoints still return correct data (including description which is not deferred).
• Confirmed via code inspection that deferred fields are NOT accessed during NearbyIssueResponse construction, ensuring no N+1 query regression.

---

PR created automatically by Jules for task 4160832973954895673 started by @RohanExploit

Summary by CodeRabbit

• Refactor
  • Optimized database query performance for issue retrieval operations.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[netlify]

✅ Deploy Preview for fixmybharat canceled.

Name	Link
🔨 Latest commit	d1ccca5
🔍 Latest deploy log	https://app.netlify.com/projects/fixmybharat/deploys/6985f790ffcc7d000822ac34

[github-actions]

🙏 Thank you for your contribution, @RohanExploit!

PR Details:

• Title: ⚡ Bolt: Defer heavy columns in issue deduplication queries
• Number: ⚡ Bolt: Defer heavy columns in issue deduplication queries #347

Quality Checklist:
Please ensure your PR meets the following criteria:

• Code follows the project's style guidelines
• Self-review of code completed
• Code is commented where necessary
• Documentation updated (if applicable)
• No new warnings generated
• Tests added/updated (if applicable)
• All tests passing locally
• No breaking changes to existing functionality

Review Process:

1. Automated checks will run on your code
2. A maintainer will review your changes
3. Address any requested changes promptly
4. Once approved, your PR will be merged! 🎉

Note: The maintainers will monitor code quality and ensure the overall project flow isn't broken.

[coderabbitai]

📝 Walkthrough

Walkthrough

Optimizes database queries in issue endpoints by adding SQLAlchemy deferred loading for action_plan, image_path, and location fields. The deferred loading is applied to two queries: in create_issue (search within 50 meters) and in get_nearby_issues (nearby filter). This reduces initial query payload by deferring non-critical column loading.

Changes

Cohort / File(s)	Summary
Query Optimization backend/routers/issues.py	Adds SQLAlchemy deferred loading for action_plan, image_path, and location fields in create_issue and get_nearby_issues queries to reduce initial database payload.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Performance Optimization & Structural Improvements #346: Modifies the same file to optimize field loading from the database using deferred column loading.

Suggested labels

size/s

Poem

🐰 A rabbit hops through databases so deep,
Deferring the columns that rest and sleep,
Action plans, images, locations deferred—
Faster queries, swiftly preferred!
Payload lighter, performance gains,
Efficiency whispers through data lanes. 🎯

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly relates to the main change: deferring heavy columns in issue deduplication queries in the backend router.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bolt/defer-heavy-columns-issues-4160832973954895673

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR optimizes issue “candidate list” queries used for deduplication and nearby-issues lookup by deferring loading of large/rarely-needed columns, reducing DB-to-app payload and memory usage during spatial filtering.

Changes:

• Deferred Issue.action_plan, Issue.image_path, and Issue.location when querying candidate open issues in create_issue deduplication logic.
• Deferred the same columns in get_nearby_issues bounding-box candidate query.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.