Expose getters from CREATE statements#2087
Open
chibenwa wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello from Apache James.
Apache James runs a Cassandra backend and we uses a light and modular table declaration system allowing aggregating tables defined everywhere in the code. It just wraps
com.datastax.oss.driver.api.querybuilder.schema.CreateTableWithOptionsand allow dependency injection to do it's job.We are able to create missing table and create them on the fly.
However we often add colomns onto existing tables and we currently fails at correcting it: admin needs to run the ALTER statement itself. And I would love to go from our table definitions and be able to asses if the existing table matches it - and see if we need to create extra coloms or not.
I was faced with 2 bad options:
I chose to try to contribute this upstream: being able to reliable describe the table that we wishes to operate on. To me at the very least this seems like a general need and is the minimal friction angle of attack to my problem.
If you have remarks I'm happy to make this work evolve.
Cheers,
Benoit