-
Notifications
You must be signed in to change notification settings - Fork 921
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
SPARKC-504: Save null UDTs #1228
Conversation
Hi @acustiq, thanks for your contribution! In order for us to evaluate and accept your PR, we ask that you sign Spark Cassandra Connector CLA. It's all electronic and will take just minutes. |
Thank you @acustiq for signing the Spark Cassandra Connector CLA. |
Fix the hyperlink to save modes in the latest Spark documentation
Sorry, I really messed up the master branch so a rebase will be necessary. If you could please rebase on b3.0 and I will review as soon as possible. |
…connector into SPARKC-504 rebase
@@ -208,7 +208,7 @@ object MappedToGettableDataConverter extends StrictLogging { | |||
for (i <- columnValues.indices) | |||
columnValues(i) = converters(i).convert(columnValues(i)) | |||
struct.newInstance(columnValues: _*) | |||
case None => | |||
case _ => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe i'm just paranoid, but should we do None | null? I may just be paranoid (this wouldn't be the first time...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would think that the _
wildcard symbol catches both None
and null
as it matches anything:
case _ => // Wild card pattern -- matches anything
Source: https://docs.scala-lang.org/tutorials/FAQ/finding-symbols.html
All tests pass! Thanks so much for your pr, please let me know you response to my above comment. I'll change the target of this pr to b3.0 to make sure it gets in the next release. |
Ah we have a few of the master commits (just docs) got dragged in, could you please rebase on b3.0? |
@RussellSpitzer please close this PR in favor of #1241 which has this change rebased on b3.0 . |
No description provided.