-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-20597][SQL][SS][WIP] KafkaSourceProvider falls back on path as synonym for topic #23791
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
Closed
Nimfadora
wants to merge
5
commits into
apache:master
from
Nimfadora:SPARK-20597-ssPathAsKafkaTopicOption
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9e46ff0
[SPARK-20597][SQL][SS] KafkaSourceProvider falls back on path as syno…
Nimfad0ra de0e039
[SPARK-20597][SQL][SS] add docs and refactor
Nimfad0ra a5b6bf7
[SPARK-20597][SQL][SS] minor refactoring
Nimfad0ra 2a41611
merge with master
Nimfad0ra f88bfe6
[SPARK-20597][SQL][SS] remove duplications and refactor
Nimfad0ra File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
nit: Since you added it I'd change it to
.select($"key" cast "string", $"value" cast "string")even if it's the only place in the doc. It's simply more type-safe.Uh oh!
There was an error while loading. Please reload this page.
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.
would it be better to change this moment in all places in this doc file, as we anyway touch it?
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.
Why make a deviation compared to all other places?
Uh oh!
There was an error while loading. Please reload this page.
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.
With the latest change don't fully understand the direction. Now half of the doc uses
selectExprand the other partselect. Still questioning the need, what is the benefit? If theselectExprexecuted and properly formed not more unstable than the simpleselectin the doc right?Uh oh!
There was an error while loading. Please reload this page.
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.
We are trying to make this expression type safe, as it such case user will see mistakes at compile time if have some.
selectis used only for scala, as we cannot use same shortened($) syntax for Java and Python, but we can useselect(col("key").cast("string"))for all three languages if we really want it both to be typesafe and looks same in all three cases. What do you think?Uh oh!
There was an error while loading. Please reload this page.
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 see the intention now, thanks for the explanation. I personally would leave as it is in the original code but not telling the direction is wrong. Let's decide by a committer who potentially picks this up.
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.
@jaceklaskowski what do you think: should we revert the changes here or use
select(col("key").cast("string"))in all places to provide type safety?