[jira] [Comment Edited] (SPARK-40351) Spark Sum increases the precision of DecimalType arguments by 10

[ https://issues.apache.org/jira/browse/SPARK-40351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630001#comment-17630001 ] Dustin Smith edited comment on SPARK-40351 at 11/7/22 8:14 PM: ---

[jira] [Comment Edited] (SPARK-40351) Spark Sum increases the precision of DecimalType arguments by 10

[ https://issues.apache.org/jira/browse/SPARK-40351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630001#comment-17630001 ] Dustin Smith edited comment on SPARK-40351 at 11/7/22 8:14 PM: ---

[jira] [Comment Edited] (SPARK-40351) Spark Sum increases the precision of DecimalType arguments by 10

[ https://issues.apache.org/jira/browse/SPARK-40351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630001#comment-17630001 ] Dustin Smith edited comment on SPARK-40351 at 11/7/22 8:07 PM: ---

[jira] [Commented] (SPARK-40351) Spark Sum increases the precision of DecimalType arguments by 10

[ https://issues.apache.org/jira/browse/SPARK-40351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630001#comment-17630001 ] Dustin Smith commented on SPARK-40351: -- [~tkhomichuk] For point 3, I think it is related to logical

[jira] [Commented] (SPARK-40934) pyspark.pandas.read_csv parses dates, but docs state otherwise

[ https://issues.apache.org/jira/browse/SPARK-40934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17629542#comment-17629542 ] Dustin Smith commented on SPARK-40934: -- What should be the desired behavior of a this date column

[jira] [Comment Edited] (SPARK-27981) Remove `Illegal reflective access` warning for `java.nio.Bits.unaligned()`

[ https://issues.apache.org/jira/browse/SPARK-27981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263052#comment-17263052 ] Dustin Smith edited comment on SPARK-27981 at 1/12/21, 3:33 AM: This

[jira] [Commented] (SPARK-27981) Remove `Illegal reflective access` warning for `java.nio.Bits.unaligned()`

[ https://issues.apache.org/jira/browse/SPARK-27981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17263052#comment-17263052 ] Dustin Smith commented on SPARK-27981: -- This problem exist on 2.4.6 as well > Remove `Illegal

[jira] [Created] (SPARK-33929) Spark-submit with --package deequ doesn't pull all jars

Dustin Smith created SPARK-33929: Summary: Spark-submit with --package deequ doesn't pull all jars Key: SPARK-33929 URL: https://issues.apache.org/jira/browse/SPARK-33929 Project: Spark

[jira] [Updated] (SPARK-33929) Spark-submit with --package deequ doesn't pull all jars

[ https://issues.apache.org/jira/browse/SPARK-33929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-33929: - Description: This issue was marked as solved SPARK-24074; however, another [~hyukjin.kwon]

[jira] [Commented] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203753#comment-17203753 ] Dustin Smith commented on SPARK-32046: -- [~planga82] this works every time without issue

[jira] [Commented] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203598#comment-17203598 ] Dustin Smith commented on SPARK-32046: -- [~planga82] the fact that the dataframes are named

[jira] [Comment Edited] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203043#comment-17203043 ] Dustin Smith edited comment on SPARK-32046 at 9/28/20, 7:12 AM:

[jira] [Commented] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17203043#comment-17203043 ] Dustin Smith commented on SPARK-32046: -- [~planga82] the use case is related to a working

[jira] [Commented] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177584#comment-17177584 ] Dustin Smith commented on SPARK-32046: -- [~maropu] yes one would expect the current timestamp to be

[jira] [Comment Edited] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177401#comment-17177401 ] Dustin Smith edited comment on SPARK-32046 at 8/14/20, 12:51 AM: -

[jira] [Comment Edited] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177401#comment-17177401 ] Dustin Smith edited comment on SPARK-32046 at 8/14/20, 12:49 AM: -

[jira] [Commented] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17177401#comment-17177401 ] Dustin Smith commented on SPARK-32046: -- [~maropu] the definition of current timestamp is as

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Affects Version/s: 3.0.0 > current_timestamp called in a cache dataframe freezes the time for

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Description: If I call current_timestamp 3 times while caching the dataframe variable in order

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Description: If I call current_timestamp 3 times while caching the dataframe variable in order

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Labels: caching sql time (was: ) > current_timestamp called in a cache dataframe freezes the

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Description: If I call current_timestamp 3 times while caching the dataframe variable in order

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Description: If I call current_timestamp 3 times while caching the dataframe variable in order

[jira] [Updated] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

[ https://issues.apache.org/jira/browse/SPARK-32046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dustin Smith updated SPARK-32046: - Description: If I call current_timestamp 3 times while caching the dataframe variable in order

[jira] [Created] (SPARK-32046) current_timestamp called in a cache dataframe freezes the time for all future calls

Dustin Smith created SPARK-32046: Summary: current_timestamp called in a cache dataframe freezes the time for all future calls Key: SPARK-32046 URL: https://issues.apache.org/jira/browse/SPARK-32046