issues Search Results · repo:vitessio/vitess language:Go
Filter by
4k results
(125 ms)4k results
invitessio/vitess (press backspace or delete to remove)Overview of the Issue
Vitess currently does not recognize MySQL 9.x versions. When running tests or deploying with MySQL 9.0+, Vitess falls
back to treating the flavor as MySQL 5.7, which leads to incorrect ...
Needs Triage
Type: Enhancement
siddharth16396
- 1
- Opened 2 days ago
- #18400
Overview of the Issue
Issue Observed
We are doing some long running schema changes and noticing that the Schema change is progressing but liveness_timestamp
is never incrementing which is eventually ...
Needs Triage
Type: Bug
- 1
- Opened 3 days ago
- #18391
Question
I would like to know whether Vitess can be used as the database for OpenStack. Rather than jumping into functional
validation without a proper understanding of Vitess s capabilities, I wanted ...
Needs Triage
Type: Question
angry-tony
- 1
- Opened 6 days ago
- #18387
Feature Description
After completing https://github.com/vitessio/vitess/issues/18273 we added a flag that allows users to opt into receive
unmodified field/row events (table name does not include keyspace) ...
Needs Triage
twthorn
- Opened 7 days ago
- #18385
[!NOTE]
This release is scheduled for Thu 19 Jun 2025. The release of vitess-operator v2.15.1 is also planned. Release team:
@vitessio/release
[!IMPORTANT]
Please do not edit the content of the Issue ...
Component: General
Type: Release
GuptaManan100
- Opened 8 days ago
- #18373
[!NOTE]
This release is scheduled for Thu 19 Jun 2025. Release team: @vitessio/release
[!IMPORTANT]
Please do not edit the content of the Issue s body manually. The vitess-releaser tool is managing and ...
Component: General
Type: Release
- Opened 8 days ago
- #18371
[!NOTE]
This release is scheduled for Wed 18 Jun 2025. Release team: @vitessio/release
[!IMPORTANT]
Please do not edit the content of the Issue s body manually. The vitess-releaser tool is managing and ...
Component: General
Type: Release
- Opened 8 days ago
- #18370
For a query such as:
select id
from user
where id = 42
union
select id
from user
where id = 42
limit 3 offset 7
The planner is forgetting about the outer LIMIT/OFFSET, and sending the query down without ...
Component: Query Serving
systay
- Opened 10 days ago
- #18360
Overview of the Issue
The GitHub actions workflow does this:
https://github.com/vitessio/vitess/blob/42317c0ecf025c47fc2bcdc2eaf5267b93ca8d00/.github/workflows/local_example.yml#L89-L93
But the export ...
Needs Triage
Type: Bug
morgo
- 1
- Opened 12 days ago
- #18355
Overview of the Issue
We ran into an issue where a workflow successfully dropped the secondary indexes in an atomic copy (except the ones
needed for the FK relations, as addressed in https://github.com/vitessio/vitess/pull/14543) ...
Component: VReplication
Type: Bug
mcrauwel
- Opened 14 days ago
- #18353
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.