Filtering Issue on UUID Column in Version 0.49.0 #40176
Assignees
Labels
.Backend
Priority:P1
Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness
Querying/GUI
Query builder catch-all, including simple mode
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Type:Bug
Product defects
Milestone
Comments
|
What is the actual data type in the db? |
|
"id" uuid DEFAULT uuid_generate_v4(), |
|
Facing the same issue, filtering on UUID is broken
here is the console log issue
troubleshoot logs |
|
Same issue here, here is the troubleshooting log I get: With a uuid field of type |
|
Hi - We have this exact same issue 0.49.0 - Can it be prioritised? |
|
I too am getting the same issue after upgrading to v49: This comes from this SQL: |
|
Can we please treat this as high priority item? For many people they use uuid as their primay id. I test with v0.49.1 and the issue is still there. Im not able to downgrade back to 0.48 for some reason (cause major version?). Our ability to explore the data is stopped right now under your mercy. |
|
Hi - We have this exact same issue 0.49.0 - Can it be prioritized? |
|
Hi - we still cannot filter UUIDs with 49.1 and cannot bring back .48 (major version downgrade does not work) Thanks again for prioritising this item |
|
Following the update to version 49.1, we are still encountering the previously reported issue. Could we prioritize its resolution? |
|
Hi guys, there is a temporary fix which can be applied through the Metabase Admin. Go to "Table Metadata", select your table and field, then change "Filtering on this field" from "Search Box" to "Plain input box".: Obviously it won't do a like search anymore, but you will be able to enter a single ID and your editor won't break - which is what we do 99% of the time with UUIDs anyway. Hope this helps a bit while we get a fix. |
|
To enhance efficiency and automation of the process outlined by @hnb2 , the following SQL command is crafted for direct execution in your Metabase database: UPDATE metabase_field
SET has_field_values = 'none'
WHERE has_field_values IS NULL
AND effective_type = 'type/UUID'
AND semantic_type = 'type/PK';This approach has been proven effective in our operational context. |
|
Thanks @hnb2 But we need the actual fix as we have tons of databases connected, and altering the metadata for all of them is not a viable options for us |
ranquild
added
Priority:P1
ranquild
added
.Regression
|
Hello, following the update to 0.49.5, I still have the issue, clicking on the filter option from a PK column do nothing, search box doesn't show up |
|
This issue shouldn't be closed as it still exists in both the v48 and v49 releases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When attempting to apply a filter on a UUID column within a table in our database, the operation consistently fails, and the error message "Something's gone wrong" is displayed. This issue appears to specifically affect the filtering functionality on UUID columns.
Actual Behavior:
Upon attempting to filter the UUID column, the system immediately returns an error message "Something's gone wrong", and no filtering action is completed. This indicates a malfunction in the filtering capability for UUID columns.
To Reproduce
Navigate to the table containing the UUID column in the database.
Attempt to apply a filter to the UUID column (e.g., filtering for a specific UUID value).
Observe the error message that appears.
Expected behavior
The filter operation should successfully apply to the UUID column, allowing records that match the filter criteria to be displayed without any error.
Logs
In logs, we have error "Erreur dans la recherche des valeurs des champs,java.lang.IllegalArgumentException: UUID string too large, at java.base/java.util.UUID.fromString(UUID.java:199), at metabase.driver.postgres$fn__83669.invokeStatic(postgres.clj:363),"
Information about your Metabase installation
{ "browser-info": { "language": "fr-FR", "platform": "MacIntel", "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36", "vendor": "Google Inc." }, "system-info": { "file.encoding": "UTF-8", "java.runtime.name": "OpenJDK Runtime Environment", "java.runtime.version": "11.0.22+7", "java.vendor": "Eclipse Adoptium", "java.vendor.url": "https://adoptium.net/", "java.version": "11.0.22", "java.vm.name": "OpenJDK 64-Bit Server VM", "java.vm.version": "11.0.22+7", "os.name": "Linux", "os.version": "6.1.75+", "user.language": "en", "user.timezone": "Etc/UTC" }, "metabase-info": { "databases": [ "postgres" ], "hosting-env": "unknown", "application-database": "postgres", "application-database-details": { "database": { "name": "PostgreSQL", "version": "11.22" }, "jdbc-driver": { "name": "PostgreSQL JDBC Driver", "version": "42.7.2" } }, "run-mode": "prod", "version": { "date": "2024-03-14", "tag": "v0.49.0", "hash": "46c668b" }, "settings": { "report-timezone": "Europe/Berlin" } } }Severity
Block usage when filtering on a UUID column
Additional context
This issue was not present in the previous version (V0.48.8), indicating a regression introduced in V0.49.0.
The text was updated successfully, but these errors were encountered: