-
Notifications
You must be signed in to change notification settings - Fork 245
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
bug(node): filtering doesn't work, no errors thrown #1081
Comments
Okay this was a weird one. The bug turns out to be we are silently ignoring filter expressions In SQL, the column references are not case sensitive. To make them case sensitive, you need to wrap in a backtick ("`"): console.log(await table.filter("`allowedGroups` LIKE '%[[admin]]%'").execute()) Or you can use lower-case column names. I'll see if I can make this return a proper error, as it is indeed not good that it would let data through. |
In Rust and Node, we have been swallowing filter validation errors. If there was an error in parsing the filter, then the filter was silently ignored, returning unfiltered results. Fixes #1081
In Rust and Node, we have been swallowing filter validation errors. If there was an error in parsing the filter, then the filter was silently ignored, returning unfiltered results. Fixes lancedb#1081
In Rust and Node, we have been swallowing filter validation errors. If there was an error in parsing the filter, then the filter was silently ignored, returning unfiltered results. Fixes lancedb#1081
In Rust and Node, we have been swallowing filter validation errors. If there was an error in parsing the filter, then the filter was silently ignored, returning unfiltered results. Fixes #1081
LanceDB version
0.4.12
What happened?
I would expect this to have instead returned:
this issue is particularly concerning, because this filtering may be used for access control. Applications that depend on that behavior may leak data to unauthorized users.
Are there known steps to reproduce?
No response
The text was updated successfully, but these errors were encountered: