Hello, We definitely welcome contributions that could improve the graph query capabilities in Calcite. If something is part of the SQL standard then it can be contributed to the core SQL parser of Calcite. If it is not standard but still widely accepted/used it should probably land in the babel parser. In every other case, we have the adapters and we can accept new ones if necessary.
In general smaller contributions are easier to review and merge so if you can divide your work into smaller parts and create JIRA tickets for each we can reason about them individually. Other than that the following threads/topics may be somewhat relevant to what you are doing. * https://lists.apache.org/thread/q3yx5tmoxzwwh1n8x4oct0vfxcfpcjwg * https://lists.apache.org/thread/oohfsp1ddyytn8v13btv21trwkbl5y2f * https://issues.apache.org/jira/browse/CALCITE-3679 * https://calcite.apache.org/docs/reference.html#match_recognize Best, Stamatis On Mon, Jun 19, 2023 at 6:03 AM pzwpzw <[email protected]> wrote: > > Hi everyone, I have noticed that the SQL 2023 have proposed the Graph > Property Query support. > http://peter.eisentraut.org/blog/2023/04/04/sql-2023-is-finished-here-is-whats-new > which we can combine the graph query "Match" statement with the sql. > > And also the ISO/GQL have proposed the GQL query. We have implement the SQL > extend which can combine SQL with the ISO/GQL query in our open source stream > graph engine > TuGraph-Analytics(https://github.com/TuGraph-family/tugraph-analytics) based > on calcite which can combine the SQL process with the graph query in one > streaming engine. We can see the syntax here: > https://github.com/TuGraph-family/tugraph-analytics/blob/master/docs/docs-en/application-development/dsl/overview.md > > So I would like to know if the Calcite community plans to support graph query > language in the future. If possible, we would like to contribute our graph > query extension to the community. > > Thanks.
