Xavier Lange

This work got me closer but I'm unable to parse expressions with the filter proceeded a `[1]` term. ``` #[test] fn filter_with_array_access_sql() { env_logger::init(); let sql = r#"SELECT "organization_id" ,...

Should the select item `("some_name")[1][20]` be parseable? Right now it's not surviving a round trip.

> Is this query working for you in Hive/Trino? Yes, array agg then pull out an element. And the query does work on AWS Athena (presto under the hood).

Sounds like the technique being used is "filtering during aggregation" and the trino docs have more to say: https://trino.io/docs/current/functions/aggregate.html#filtering-during-aggregation . Not sure why they don't mention this in the presto...

I am now debugging this as a new test case for the Hive dialect: ``` #[test] fn filtering_during_aggregation() { env_logger::init(); let rename = "SELECT array_agg(name) FILTER (WHERE name IS NOT...

Looking at how Expr are built: ``` /// Parse a comma-delimited list of projections after SELECT pub fn parse_select_item(&mut self) -> Result { match self.parse_wildcard_expr()? { WildcardExpr::Expr(expr) => self .parse_optional_alias(keywords::RESERVED_FOR_COLUMN_ALIAS)...

I think this has to be run inside a JDK environment. I am successfully running this project inside of the docker image `java:openjdk-8-jdk`. ``` docker run --rm -it java:openjdk-8-jdk wget...

I am digging in to this issue as well. No idea why clang couldn't handle these `.S` files. This is openssl logic that hasn't been touched in boringssl either. Something...

I wanted to know what the build.rs was seeing, added this panic: ``` panic!("target arch: {}, os: {}, is_musl: {}, is_like_clang: {}", target.arch, target.os, target.is_musl, compiler.is_like_clang()); // thread 'main' panicked...

I am seeing this issue as well, 3.5.4 on linux/kubernetes using the official images. We are shipping our etcd using the bitnami helm chart.