Remove CQL features unsupported by CosmosDB #18
Merged
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
Unlike many CSV engines, Cassandra requires quotes within quotes fields
to be escaped with a back-slash, not by doubling the quotes.
Do this: `"{\"foo\":\"bar\",\"baz\":\"foo\"}"`
Not this: `"{""foo"":""bar"",""baz"":""foo""}"`
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.
Going forward, we'll likely want to move our configuration data out of Cassandra on k8s and into a more stable data-store. CosmosDB has a Cassandra API so it would be a relatively low risk migration.
However, some features aren't supported in the CosmosDB Cassandra API yet, e.g. frozen columns, map columns, list columns or set columns. This pull request removes references to all the non-supported features in the settings keyspace in anticipation of moving that keyspace to CosmosDB.
Requesting review from @kevinhartman since this touches the streams/configuration code in the Spark pipeline with which I'm not super familiar.