jonahgao commented on issue #13822: URL: https://github.com/apache/datafusion/issues/13822#issuecomment-2551730481
> Correct, my proposal was to basically establish a convention on how to distinguish them. Currently it returns an error, so adding this as a convention seemed relatively harmless. This convention seems to be consistent with the current DataFusion, for example, "one.two.three" is not parsed as: `catalog`: None `schema`: one.two `table`: three Considering nested fields, we need to be careful with column parsing, such as establishing a reasonable search terms and priority in [generate_schema_search_terms](https://github.com/apache/datafusion/blob/82a40f3edf264834c28f3a1bf2a3143951802634/datafusion/sql/src/expr/identifier.rs#L311). ```sh DataFusion CLI v43.0.0 > create table a(b struct<c int>); 0 row(s) fetched. # c is a field name of struct > select a.b.c from a; +--------+ | a.b[c] | +--------+ +--------+ 0 row(s) fetched. Elapsed 0.017 seconds. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
