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
As a JS API consumer, I want to filter a columns in tables with types that can be deserialized in the client, but cannot yet be referenced in a filter. This includes
LocalDate
LocalTime
BigInteger
BigDecimal
In other API calls we tend to encourage using Flight serialization to send arbitrary values back to the server (note that these types are not yet supported there either, see #1041), but filters are not usually built this way. Instead, we have a simplified AST for filters that focuses on composing boolean expressions, and only supports String, long, double (and other numerics that fit in that size), boolean, and instant.
See also #6364 - while considering a more powerful AST for expressions, we should consider expanding literals that we support for filters - or a way to serialize generic data, even if we just send them as strings and support various factory methods (e.g. LocalDate.of(...) or parse(String) calls.
The text was updated successfully, but these errors were encountered:
As a JS API consumer, I want to filter a columns in tables with types that can be deserialized in the client, but cannot yet be referenced in a filter. This includes
In other API calls we tend to encourage using Flight serialization to send arbitrary values back to the server (note that these types are not yet supported there either, see #1041), but filters are not usually built this way. Instead, we have a simplified AST for filters that focuses on composing boolean expressions, and only supports String, long, double (and other numerics that fit in that size), boolean, and instant.
See also #6364 - while considering a more powerful AST for expressions, we should consider expanding literals that we support for filters - or a way to serialize generic data, even if we just send them as strings and support various factory methods (e.g. LocalDate.of(...) or parse(String) calls.
The text was updated successfully, but these errors were encountered: