You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sujith Jay Nair (JIRA)" <ji...@apache.org> on 2018/01/03 10:08:00 UTC

[jira] [Commented] (SPARK-17833) 'monotonicallyIncreasingId()' should be deterministic

    [ https://issues.apache.org/jira/browse/SPARK-17833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309411#comment-16309411 ] 

Sujith Jay Nair commented on SPARK-17833:
-----------------------------------------

This issue is resolved in 2.0, as mentioned in [SPARK-14241 | https://issues.apache.org/jira/browse/SPARK-14241]

> 'monotonicallyIncreasingId()' should be deterministic
> -----------------------------------------------------
>
>                 Key: SPARK-17833
>                 URL: https://issues.apache.org/jira/browse/SPARK-17833
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Kevin Ushey
>            Priority: Critical
>
> Right now, it's (IMHO) too easy to shoot yourself in the foot using 'monotonicallyIncreasingId()', as it's easy to expect the generated numbers to function as a 'stable' primary key, for example, and then go on to use that key in e.g. 'joins' and so on.
> Is there any reason why this function can't be made deterministic? Or, could a deterministic analogue of this function be added (e.g. 'withPrimaryKey(columnName = ...)')?
> A solution is to immediately cache / persist the table after calling 'monotonicallyIncreasingId()'; it's also possible that the documentation should spell that out loud and clear.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org