[SPARK-8420] [SQL] Inconsistent behavior with Dataframe Timestamp between 1.3.1 and 1.4.0 #6931
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
…ween 1.3.1 and 1.4.0
|
Can one of the admins verify this patch? |
|
@marmbrus Could you review this, plz? |
|
@navis looks like this is already fixed. Would you mind closing this patch? |
|
@andrewor14 Currently, "timestamp == string" converts string into timestamp, but for "timestamp > string", string is converted into timestamp. And this inconsistency makes me nervous a little, but I should accept that it's ok in most cases. Closing the issue. |
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.
Havn't seen that the issue was fixed already. But It seemed it still has a inconsistency problem on equals and non-eauls. This patch proposes normalized format for string type to be compared with timestamp type.