-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Lookup vindex with lookup key type 'unicode_loose_md5' seems to be broken in 8.0.0 #7254
Comments
I believe the problem is in this piece of code being case-sensitive: vitess/go/vt/vtgate/vindexes/lookup_internal.go Lines 120 to 128 in 88671b0
|
aquarapid
changed the title
Vindex with type 'unicode_loose_md5' seems to be broken in 8.0.0
Lookup vindex with lookup key type 'unicode_loose_md5' seems to be broken in 8.0.0
Jan 5, 2021
This was referenced Jan 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Issue
While trying to upgrade to v8.0.0 we have noticed that case-insensitive vindexes seem to not be working anymore.
Reproduction Steps
From the directory with sources of v8.0.0 of Vitess:
In docker shell:
source ./env.sh CELL=zone1 TABLET_UID=300 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=301 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=400 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=401 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=500 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=501 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=600 ./scripts/mysqlctl-up.sh CELL=zone1 TABLET_UID=601 ./scripts/mysqlctl-up.sh SHARD=-80 CELL=zone1 KEYSPACE=customer TABLET_UID=300 ./scripts/vttablet-up.sh SHARD=-80 CELL=zone1 KEYSPACE=customer TABLET_UID=301 ./scripts/vttablet-up.sh SHARD=80- CELL=zone1 KEYSPACE=customer TABLET_UID=400 ./scripts/vttablet-up.sh SHARD=80- CELL=zone1 KEYSPACE=customer TABLET_UID=401 ./scripts/vttablet-up.sh SHARD=-80 CELL=zone1 KEYSPACE=lookup TABLET_UID=500 ./scripts/vttablet-up.sh SHARD=-80 CELL=zone1 KEYSPACE=lookup TABLET_UID=501 ./scripts/vttablet-up.sh SHARD=80- CELL=zone1 KEYSPACE=lookup TABLET_UID=600 ./scripts/vttablet-up.sh SHARD=80- CELL=zone1 KEYSPACE=lookup TABLET_UID=601 ./scripts/vttablet-up.sh vtctlclient InitShardMaster -force customer/-80 zone1-300 vtctlclient InitShardMaster -force customer/80- zone1-400 vtctlclient InitShardMaster -force lookup/-80 zone1-500 vtctlclient InitShardMaster -force lookup/80- zone1-600 vtctlclient ApplySchema -sql-file lookup_schema.sql lookup vtctlclient ApplyVSchema -vschema_file lookup_vschema.json lookup vtctlclient ApplySchema -sql-file customer_schema.sql customer vtctlclient ApplyVSchema -vschema_file customer_vschema.json customer
After connecting to DB with mysql client:
Expected result: 1 row
Actual result: 0 rows
Files required to reproduce the issue:
lookup_vschema.json
lookup_schema.sql
customer_vschema.json
customer_schema.sql
Binary version
Git tag
v8.0.0
, commit 7e09d0c.Version: 7e09d0c20 (Git branch 'HEAD') built on Tue Jan 5 17:54:43 UTC 2021 by vitess@504c9a859469 using go1.13.15 linux/amd64
Operating system and Environment details
Bug is reproducible in docker_local environment.
Log Fragments
/debug/querylog
output when running the problematic query:On master tablet in
customer
namespace:On master tablet in
lookup
namespace:The text was updated successfully, but these errors were encountered: