[
https://issues.apache.org/jira/browse/CALCITE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356654#comment-16356654
]
Christian Tzolov commented on CALCITE-2059:
-------------------------------------------
[~julianhyde] much appreciate the help for cleaning the code! I've reviewed and
squashed your changes. I also removed the GeodeAggregationSort and Main1Foo as
redundant.
Lets discuss REGION_MAP and JAVA_TYPE_FACTORY. Can you elaborate on your
concerns? I am concerned that we don't close the connections until a new
re-connection is attempted. Perhaps there are some examples from the other
adapters that "auto-close" the backend connection on "certain" conditions?
[~michaelmior] i was wondering about the JDK9 Travis build indeed. Thanks for
the clarification.
> Apache Geode adapter
> --------------------
>
> Key: CALCITE-2059
> URL: https://issues.apache.org/jira/browse/CALCITE-2059
> Project: Calcite
> Issue Type: New Feature
> Components: geode
> Reporter: Christian Tzolov
> Assignee: Julian Hyde
> Priority: Major
>
> I've been working on a Calcite adapter for [Apache
> Geode|http://geode.apache.org].
> Current implementation uses the plain Geode API and
> [OQL|http://geode.apache.org/docs/guide/13/developing/querying_basics/chapter_overview.html](Object
> Query Interface) to push down relational expressions such as projections,
> filtering, sorting, and grouping .
> Provided functionality can hopefully address certain Geode use cases and will
> provide a stepping stone for future improvements.
> Here are some remaining tasks as i see it:
> * New tests for test suite (and update calcite-test-dataset to support Geode)
> * Add Integration tests that use calcite-test-dataset
> * Documentation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
