-
Notifications
You must be signed in to change notification settings - Fork 40
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
DataConverter should be configurable so as to allow conversion of any type of ValueSchema to CQL query #16
Labels
Milestone
Comments
Hi @aaruna, the PR I'm working on in another branch which I believe resolves this actually. |
aaruna
added a commit
to aaruna/kafka-connect-cassandra
that referenced
this issue
Apr 13, 2016
…kRecord to CQL columns
I have raised a PR #18 fixing this issue. |
aaruna
added a commit
to aaruna/kafka-connect-cassandra
that referenced
this issue
May 3, 2016
…kRecord to CQL columns
aaruna
added a commit
to aaruna/kafka-connect-cassandra
that referenced
this issue
May 4, 2016
…kRecord to CQL columns
aaruna
added a commit
to aaruna/kafka-connect-cassandra
that referenced
this issue
May 4, 2016
…kRecord to CQL columns
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now,
DataConverter.sinkRecordToQuery(r, configProperties)
assumes one-to-one mapping between fields in ValuesSchema of SinkRecord to the columns in the CQL table.I saw this need when I am trying to use
kafka-connect-twitter
which uses a particular schema and the Sink table might have a different schema.@helena Is this a valid use-case?
The text was updated successfully, but these errors were encountered: