[SQL][DOCS][MINOR] Fix typos and wrong phrases in docs #27819
Closed
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
Member
Author
maropu
commented
Mar 6, 2020
|
|
||
| In Spark SQL, arithmetic operations performed on numeric types (with the exception of decimal) are not checked for overflows by default. | ||
| This means that in case an operation causes overflows, the result is the same that the same operation returns in a Java/Scala program (e.g., if the sum of 2 integers is higher than the maximum value representable, the result is a negative number). | ||
| This means that in case an operation causes overflows, the result is the same with the corresponding operation in a Java/Scala program (e.g., if the sum of 2 integers is higher than the maximum value representable, the result is a negative number). |
HyukjinKwon
reviewed
Mar 6, 2020
| ALTER TABLE test_tab SET SERDE 'org.apache.hadoop.hive.serde2.columnar.LazyBinaryColumnarSerDe'; | ||
|
|
||
| ALTER TABLE dbx.tab1 SET SERDE 'org.apache.madoop' WITH SERDEPROPERTIES ('k' = 'v', 'kay' = 'vee') | ||
| ALTER TABLE dbx.tab1 SET SERDE 'org.apache.hadoop' WITH SERDEPROPERTIES ('k' = 'v', 'kay' = 'vee') |
gengliangwang
approved these changes
Mar 6, 2020
Member
gengliangwang
left a comment
gengliangwang
left a comment
There was a problem hiding this comment.
LGTM, thanks for doing this!
HyukjinKwon
approved these changes
Mar 6, 2020
|
Test build #119432 has finished for PR 27819 at commit
|
Member
|
Merging to master/3.0 |
Member
Author
|
Thanks, @gengliangwang and @HyukjinKwon ! |
gengliangwang
pushed a commit
that referenced
this pull request
Mar 6, 2020
### What changes were proposed in this pull request? This PR intends to fix typos and phrases in the `/docs` directory. To find them, I run the Intellij typo checker. ### Why are the changes needed? For better documents. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? N/A Closes #27819 from maropu/TypoFix-20200306. Authored-by: Takeshi Yamamuro <[email protected]> Signed-off-by: Gengliang Wang <[email protected]> (cherry picked from commit ffec7a1) Signed-off-by: Gengliang Wang <[email protected]>
sjincho
pushed a commit
to sjincho/spark
that referenced
this pull request
Apr 15, 2020
### What changes were proposed in this pull request? This PR intends to fix typos and phrases in the `/docs` directory. To find them, I run the Intellij typo checker. ### Why are the changes needed? For better documents. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? N/A Closes apache#27819 from maropu/TypoFix-20200306. Authored-by: Takeshi Yamamuro <[email protected]> Signed-off-by: Gengliang Wang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What changes were proposed in this pull request?
This PR intends to fix typos and phrases in the
/docsdirectory. To find them, I run the Intellij typo checker.Why are the changes needed?
For better documents.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A