[SPARK-9006] [PYSPARK] fix microsecond loss in Python 3 #7363
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
|
Test build #37116 has finished for PR 7363 at commit
|
davies
pushed a commit
that referenced
this pull request
Jul 13, 2015
It may loss a microsecond if using timestamp as float, should be `int` instead. Author: Davies Liu <[email protected]> Closes #7363 from davies/fix_microsecond and squashes the following commits: 36f6007 [Davies Liu] fix microsecond loss in Python 3
Contributor
|
Is that the root causes for the unit test failure for Pyspark recently? |
Contributor
Author
|
@chenghao-intel yes. |
Contributor
Author
|
merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
It may loss a microsecond if using timestamp as float, should be
intinstead.