You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2017/05/04 00:56:04 UTC

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

     [ https://issues.apache.org/jira/browse/SPARK-17833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph K. Bradley updated SPARK-17833:
--------------------------------------
    Priority: Critical  (was: Minor)

> '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.3.15#6346)

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