Skip to content
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

Support SQL pipe operator #14660

Open
simonvandel opened this issue Feb 14, 2025 · 2 comments
Open

Support SQL pipe operator #14660

simonvandel opened this issue Feb 14, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@simonvandel
Copy link
Contributor

simonvandel commented Feb 14, 2025

Is your feature request related to a problem or challenge?

Google BigQuery is releasing support for a pipe operator in their supported Sql dialect. See https://cloud.google.com/bigquery/docs/pipe-syntax-guide and https://research.google/pubs/sql-has-problems-we-can-fix-them-pipe-syntax-in-sql/

Databricks seem to be supporting a similar operator https://docs.databricks.com/en/sql/language-manual/sql-ref-syntax-qry-select-pipeop.html

Relates to #14514 which is on supporting Sql features that make SQL easier to write and read.

Describe the solution you'd like

Datafusion supports the pipe operator, which will allow writing queries more ergonomically.

Describe alternatives you've considered

No response

Additional context

No response

@simonvandel simonvandel added the enhancement New feature or request label Feb 14, 2025
@alamb
Copy link
Contributor

alamb commented Feb 15, 2025

Interesting idea -- the first thing needed is support in sqlparser if we don't alread have it

Thanks for the suggestion

@simonvandel
Copy link
Contributor Author

Here's a short video presentation by a Google engineer https://www.hytradboi.com/2025/f8582cd3-1e39-43a8-8749-46817b2910cf-pipe-syntax-in-sql-its-time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants