Thanks, Michael and Julian. I have opened CALCITE-1814 to track this
effort. I'm sure that you will need to correct my guesses for the values
of some of the JIRA fields.
Thanks,
-Rick
On 5/30/17 11:03 AM, Julian Hyde wrote:
Rick,
Good to meet you! Our paths have ALMOST crossed quite a few times, I
think. And I'm pleased to hear that you are working at SQLstream.
I would be delighted to have better Derby support. For one thing, I've
always found Derby to be very close to the SQL standard, so if Derby
doesn't understand the SQL that Calcite is generating, it's probably
Calcite's problem.
Were you planning on using Derby embedded or via client-server? I
would imagine that it makes no difference to the SQL dialect, a small
difference to connect strings, but possibly a larger difference to the
test infrastructure.
One option to consider, if Derby supports it: create an embedded Derby
database for the most important data sets (foodmart [1] and scott
[2]). We do this for hsqldb: we wrap each database in a jar (which is
1% code and 99% data) and deploy the databases to Maven central. If
you are able to take that option, people will be able to run against
Derby without any setup.
Can you create a JIRA case and we can discuss further there?
Julian
[1] https://github.com/julianhyde/foodmart-data-hsqldb
[2] https://github.com/julianhyde/scott-data-hsqldb
On Tue, May 30, 2017 at 6:25 AM, Michael Mior <[email protected]> wrote:
Rick,
While I'm not a Derby user, I think it would be great to have better
integration (and tests!). If you're looking to add integration tests for
Derby, the first step would be to get Derby running in the test VM image (
https://github.com/vlsi/calcite-test-dataset). You should be able to model
the tests after the existing integration tests for MySQL and PostgreSQL. A
JIRA to track this would be a good idea.
Cheers,
--
Michael Mior
[email protected]
2017-05-29 15:17 GMT-04:00 Rick Hillegas <[email protected]>:
Hello Calcite community,
My name is Rick Hillegas. I am a Derby committer and a former VP of the
Apache DB project. For ten-plus years, I worked at Sun/Oracle, where I
served as an alternate delegate to the INCITS SQL committee. Currently, I
work at a company called SQLstream, which some of you know well.
I would like to start contributing to Calcite by improving Calcite's
integration with Derby. That is, I would like to make Derby as well
integrated with Calcite as h2, hsqldb, MySQL, and PostgreSQL are. I noticed
the following: although Derby is already a supported
org.apache.calcite.sql.SqlDialect, Derby does not appear in the list of
databases exercised by Calcite tests (see https://calcite.apache.org/doc
s/howto.html#running-tests).
Would this contribution be welcome? If so, I can open a Calcite JIRA issue
to track this effort--or take whatever next steps you think are appropriate.
Thanks,
-Rick
