Skip to content
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.

Sign up for GitHub

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

Jump to bottom

BLUE-206 Revert to the original index applied in the tables due to slow db queries #59

Merged
merged 1 commit into from
Aug 6, 2024
Merged

BLUE-206 Revert to the original index applied in the tables due to slow db queries #59

merged 1 commit into from
Aug 6, 2024

Conversation

jairajdev
Copy link
Contributor

No description provided.

@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 5, 2024

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Key issues to review

Hardcoded Value
The timeout value REQUEST_NETCONFIG_TIMEOUT_SECOND is hardcoded. Consider making it configurable to allow easier adjustments without code changes.

Index Changes
The changes in database index definitions (e.g., from ASC to DESC) might affect performance. Ensure these changes are tested for performance impacts.

@jairajdev jairajdev changed the title Revert to the original index applied in the tables due to slow db queries BLUE-206 Revert to the original index applied in the tables due to slow db queries Aug 5, 2024
@afostr afostr merged commit 9896f3c into dev Aug 6, 2024
7 checks passed
@mhanson-github mhanson-github deleted the db-index-revert branch September 2, 2024 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Review effort [1-5]: 3
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jairajdev @afostr