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.

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

[CherryPick] : Fix failed BVT query in Secondary Index (#16429) #16499

Merged
merged 5 commits into from
May 30, 2024

Conversation

arjunsk
Copy link
Contributor

@arjunsk arjunsk commented May 30, 2024

What type of PR is this?

  • API-change
  • BUG
  • Improvement
  • Documentation
  • Feature
  • Test and CI
  • Code Refactoring

Which issue(s) this PR fixes:

issue # #16427

What this PR does / why we need it:

Cherry Pick #16427 to 1.2-dev

Replace
```sql
select name, type, column_name from mo_catalog.mo_indexes mi where mi.column_name ="name" or mi.column_name="__mo_alias_id";
```
To
```sql
select name, type, column_name from mo_catalog.mo_indexes mi where name="idx5";
```

to match the set of other queries in that BVT file.

Approved by: @heni02
Copy link

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Review 🔍

⏱️ Estimated effort to review [1-5]

2, because the changes are localized to specific test cases and involve straightforward renaming of an index, which is easy to verify for correctness.

🧪 Relevant tests

Yes

⚡ Possible issues

No

🔒 Security concerns

No

@matrix-meow matrix-meow added the size/S Denotes a PR that changes [10,99] lines label May 30, 2024
@mergify mergify bot requested a review from sukki37 May 30, 2024 04:00
@mergify mergify bot added the kind/bug Something isn't working label May 30, 2024
Copy link

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Code Suggestions ✨

CategorySuggestion                                                                                                                                    Score
Best practice
Use a more descriptive name for the index to improve code readability and maintainability

To ensure consistency and avoid potential issues with index naming conventions, consider
using a more descriptive name for the index instead of idx5. This will make the code more
readable and maintainable.

test/distributed/cases/ddl/secondary_index_create.result [87]

-create table t1(id VARCHAR(255) PRIMARY KEY,name VARCHAR(255),age int, index idx5(name));
+create table t1(id VARCHAR(255) PRIMARY KEY,name VARCHAR(255),age int, index idx_name(name));
 
Suggestion importance[1-10]: 6

Why: The suggestion to rename the index to something more descriptive is valid as it enhances readability and maintainability. However, 'idx5' might be sufficient depending on the context and naming conventions used in the project, so the impact of this change is moderate.

6

@mergify mergify bot merged commit 085936b into matrixorigin:1.2-dev May 30, 2024
18 checks passed
@aylei aylei mentioned this pull request Jun 5, 2024
@arjunsk arjunsk deleted the 1.2-dev-sec_idx+bvt branch June 11, 2024 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug fix kind/bug Something isn't working Review effort [1-5]: 2 size/S Denotes a PR that changes [10,99] lines Tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants