You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The filemanager API can use [] to query for parameters that should be combined with an "or" condition. Query parameters without [] get combined into "and" conditions.
Which could combine into a statement that looks like:
select*from s3_object
where key like'%.fastq.gz'and (key like'%123%'or key like'%456%')
Currently this is not possible and results in a deserialization error:
"Failed to deserialize query string. Error: Multiple values for one key: \"key\""
Note, that I think the order of the query parameters shouldn't matter, so if they are out of order, keys with [] would be grouped anyway. Fixing this still won't enable complex logic that involves nesting conditions.
The text was updated successfully, but these errors were encountered:
mmalenic
changed the title
fix: filemanager api should allow singular and list-based queries for the same key
bug: filemanager api should allow singular and list-based queries for the same key
Nov 19, 2024
mmalenic
changed the title
bug: filemanager api should allow singular and list-based queries for the same key
filemanager: API should allow singular and list-based queries for the same key
Nov 19, 2024
The filemanager API can use
[]
to query for parameters that should be combined with an "or" condition. Query parameters without[]
get combined into "and" conditions.The following should be possible:
Which could combine into a statement that looks like:
Currently this is not possible and results in a deserialization error:
Note, that I think the order of the query parameters shouldn't matter, so if they are out of order, keys with
[]
would be grouped anyway. Fixing this still won't enable complex logic that involves nesting conditions.The text was updated successfully, but these errors were encountered: