sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M. Le Bihan (JIRA)" <>
Subject [jira] [Commented] (SIS-304) Attempt to use Calcite SQL Parser instead of the one currently used to parse SQL statements
Date Mon, 07 Dec 2015 08:11:11 GMT


M. Le Bihan commented on SIS-304:

The 25th of November, I asked Calcite dev mailling-list how Calcite can help us in our case.
Julian Hyde replied to me :
Since thanksgiving is coming up, I’ll give the short answer: Yes, Avatica/Calcite can do

The general advice is as follows. If you already have a SQL parser and execution engine, you
could use Avatica to convert it into a solid, JDBC provider supporting both local and remote
clients. If you do not have a SQL parser, use Calcite. Calcite can support the gamut from
where you just have simple relations (such as CSV files) and no query-processing operators
to where you have a rich set of operators. We recommend that you start off with just relations
and add more rules to allow pushing down of filters, projects and other operators to your

I’ll give you more specific advice in a day or two. I have downloaded and built your source
code and will read through it with the specifics of your proposal in mind.

I hope it can work out — it’s always rewarding to work with other Apache projects.

> Attempt to use Calcite SQL Parser instead of the one currently used to parse SQL statements
> -------------------------------------------------------------------------------------------
>                 Key: SIS-304
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Shapefile
>    Affects Versions: 0.7
>            Reporter: M. Le Bihan
>            Assignee: M. Le Bihan
>              Labels: Calcite, JDBC
> The current SQL parser developped with DBase III JDBC driver has many limitations, and
it can only works for simple SELECT statements.
> The [Calcite|] open source project might be of great help if
it matches our need.
> This task is a PoC that if it goes well, will allow the removal of 
> org.apache.sis.internal.shapefile.jdbc.sql.CrudeSQLParser
> org.apache.sis.internal.shapefile.jdbc.sql.ConditionalClauseResolver
> org.apache.sis.internal.shapefile.jdbc.sql.ClauseResolver
> in favor of the Calcite API

This message was sent by Atlassian JIRA

View raw message