Uh oh!
There was an error while loading. Please reload this page.
[SPARK-9006] [PYSPARK] fix microsecond loss in Python 3 - #7363
Closed
davies wants to merge 1 commit into
Closed
Conversation
SparkQA
commented
Jul 13, 2015
Test build #37116 has finished for PR 7363 at commit
|
chenghao-intel
commented
Jul 13, 2015
Contributor
Is that the root causes for the unit test failure for Pyspark recently? |
davies
commented
Jul 13, 2015
ContributorAuthor
@chenghao-intel yes. |
davies
commented
Jul 13, 2015
ContributorAuthor
merged. |
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.