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

[CALCITE-1080] Cassandra adapter #195

Closed
wants to merge 1 commit into from

Conversation

michaelmior
Copy link
Member

This is the basis for a working Cassandra adapter for Calcite. There's still a lot to be done, but the basics are working. Currently there are rules for filtering, sorting, and projections. There are some basic integration tests written which test each of these. The tests use a fork of calcite-test-dataset which would presumably be merged along with this work when the time comes. Tests can be run the same as with MongoDB.

I'd love to get some early feedback and see what it will take to get this merged so others can start playing with it.

https://issues.apache.org/jira/browse/CALCITE-1080

@michaelmior michaelmior force-pushed the cassandra branch 2 times, most recently from 85061dc to 150dae1 Compare February 13, 2016 01:52
@michaelmior michaelmior changed the title Cassandra adapter [CALCITE-1080] Cassandra adapter Feb 13, 2016
</execution>
</executions>
</plugin>
<plugin>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems unnecessary to have the maven-release-plugin here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not really familiar with Maven. I just copied this from mongodb/pom.xml. Aren't individual projects released as separate artifacts? I assumed the release plugin was necessary to coordinate the release process. If not, I can remove.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, ok. No, it shouldn't be necessary to define any plugin unless you have some special configuration necessary for that plugin. If you copied from the mongodb module, that's fine. I can clean up every at once later :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants