[jira] [Created] (SPARK-33733) PullOutNondeterministic should check and collect deterministic field

ulysses you created SPARK-33733: --- Summary: PullOutNondeterministic should check and collect deterministic field Key: SPARK-33733 URL: https://issues.apache.org/jira/browse/SPARK-33733 Project: Spark

[jira] [Resolved] (SPARK-33732) Kubernetes integration tests doesn't work with Minikube 1.9+

[ https://issues.apache.org/jira/browse/SPARK-33732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-33732. --- Fix Version/s: 3.1.0 Resolution: Fixed This is resolved via

[jira] [Resolved] (SPARK-33714) Migrate ALTER VIEW ... SET/UNSET TBLPROPERTIES to new resolution framework

[ https://issues.apache.org/jira/browse/SPARK-33714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan resolved SPARK-33714. - Fix Version/s: 3.2.0 Resolution: Fixed Issue resolved by pull request 30676

[jira] [Assigned] (SPARK-33714) Migrate ALTER VIEW ... SET/UNSET TBLPROPERTIES to new resolution framework

[ https://issues.apache.org/jira/browse/SPARK-33714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-33714: --- Assignee: Terry Kim > Migrate ALTER VIEW ... SET/UNSET TBLPROPERTIES to new resolution

[jira] [Resolved] (SPARK-33558) Unify v1 and v2 ALTER TABLE .. ADD PARTITION tests

[ https://issues.apache.org/jira/browse/SPARK-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan resolved SPARK-33558. - Fix Version/s: 3.1.0 Resolution: Fixed Issue resolved by pull request 30685

[jira] [Assigned] (SPARK-33558) Unify v1 and v2 ALTER TABLE .. ADD PARTITION tests

[ https://issues.apache.org/jira/browse/SPARK-33558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-33558: --- Assignee: Maxim Gekk > Unify v1 and v2 ALTER TABLE .. ADD PARTITION tests >

[jira] [Resolved] (SPARK-33724) Allow decommissioning script location to be configured

[ https://issues.apache.org/jira/browse/SPARK-33724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-33724. --- Fix Version/s: 3.2.0 Resolution: Fixed Issue resolved by pull request 30694

[jira] [Commented] (SPARK-33732) Kubernetes integration tests doesn't work with Minikube 1.9+

[ https://issues.apache.org/jira/browse/SPARK-33732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17247009#comment-17247009 ] Apache Spark commented on SPARK-33732: -- User 'sarutak' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33732) Kubernetes integration tests doesn't work with Minikube 1.9+

[ https://issues.apache.org/jira/browse/SPARK-33732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33732: Assignee: Kousuke Saruta (was: Apache Spark) > Kubernetes integration tests doesn't

[jira] [Assigned] (SPARK-33732) Kubernetes integration tests doesn't work with Minikube 1.9+

[ https://issues.apache.org/jira/browse/SPARK-33732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33732: Assignee: Apache Spark (was: Kousuke Saruta) > Kubernetes integration tests doesn't

[jira] [Commented] (SPARK-33732) Kubernetes integration tests doesn't work with Minikube 1.9+

[ https://issues.apache.org/jira/browse/SPARK-33732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17247008#comment-17247008 ] Apache Spark commented on SPARK-33732: -- User 'sarutak' has created a pull request for this issue:

[jira] [Created] (SPARK-33732) Kubernetes integration tests doesn't work with Minikube 1.9+

Kousuke Saruta created SPARK-33732: -- Summary: Kubernetes integration tests doesn't work with Minikube 1.9+ Key: SPARK-33732 URL: https://issues.apache.org/jira/browse/SPARK-33732 Project: Spark

[jira] [Updated] (SPARK-33730) Standardize warning types

[ https://issues.apache.org/jira/browse/SPARK-33730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon updated SPARK-33730: - Description: We should use warnings properly per

[jira] [Updated] (SPARK-33730) Standardize warning types

[ https://issues.apache.org/jira/browse/SPARK-33730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon updated SPARK-33730: - Description: We should use warnings properly per

[jira] [Updated] (SPARK-33730) Standardize warning types

[ https://issues.apache.org/jira/browse/SPARK-33730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon updated SPARK-33730: - Description: We should use warnings properly per

[jira] [Updated] (SPARK-33730) Standardize warning types

[ https://issues.apache.org/jira/browse/SPARK-33730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon updated SPARK-33730: - Description: We should use warnings properly per

[jira] [Commented] (SPARK-33730) Standardize warning types

[ https://issues.apache.org/jira/browse/SPARK-33730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246997#comment-17246997 ] Hyukjin Kwon commented on SPARK-33730: -- [~zero323] would you be interested in this? > Standardize

[jira] [Created] (SPARK-33731) Standardize exception types

Hyukjin Kwon created SPARK-33731: Summary: Standardize exception types Key: SPARK-33731 URL: https://issues.apache.org/jira/browse/SPARK-33731 Project: Spark Issue Type: Sub-task

[jira] [Created] (SPARK-33730) Standardize warning types

Hyukjin Kwon created SPARK-33730: Summary: Standardize warning types Key: SPARK-33730 URL: https://issues.apache.org/jira/browse/SPARK-33730 Project: Spark Issue Type: Sub-task

[jira] [Assigned] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon reassigned SPARK-33727: Assignee: Holden Karau > `gpg: keyserver receive failed: No name` during K8s IT >

[jira] [Resolved] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon resolved SPARK-33727. -- Fix Version/s: 3.0.2 3.1.0 Resolution: Fixed Issue resolved by pull

[jira] [Updated] (SPARK-33721) Support to use Hive build-in functions by configuration

[ https://issues.apache.org/jira/browse/SPARK-33721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated SPARK-33721: -- Description: Hive and Spark SQL engines have many differences in built-in functions.The differences

[jira] [Updated] (SPARK-33721) Support to use Hive build-in functions by configuration

[ https://issues.apache.org/jira/browse/SPARK-33721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated SPARK-33721: -- Description: Hive and Spark SQL engines have many differences in built-in functions.The differences

[jira] [Updated] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33725: -- Fix Version/s: 2.4.8 > Upgrade snappy-java to 1.1.8.2 > -- > >

[jira] [Updated] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33725: -- Fix Version/s: (was: 3.2.0) 3.1.0 > Upgrade snappy-java to 1.1.8.2 >

[jira] [Reopened] (SPARK-22769) When driver stopping, there is errors: "Could not find CoarseGrainedScheduler" and "RpcEnv already stopped"

[ https://issues.apache.org/jira/browse/SPARK-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Su Qilong reopened SPARK-22769: --- The original reporter gave up work on this，i make a new change for this > When driver stopping, there

[jira] [Comment Edited] (SPARK-23086) Spark SQL cannot support high concurrency for lock in HiveMetastoreCatalog

[ https://issues.apache.org/jira/browse/SPARK-23086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246957#comment-17246957 ] GeoffreyStark edited comment on SPARK-23086 at 12/10/20, 1:59 AM: -- In

[jira] [Comment Edited] (SPARK-23086) Spark SQL cannot support high concurrency for lock in HiveMetastoreCatalog

[ https://issues.apache.org/jira/browse/SPARK-23086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246958#comment-17246958 ] GeoffreyStark edited comment on SPARK-23086 at 12/10/20, 1:58 AM: --

[jira] [Commented] (SPARK-23086) Spark SQL cannot support high concurrency for lock in HiveMetastoreCatalog

[ https://issues.apache.org/jira/browse/SPARK-23086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246958#comment-17246958 ] GeoffreyStark commented on SPARK-23086: --- Sorry, I forgot to say, I changed my nickname, I am the

[jira] [Commented] (SPARK-23086) Spark SQL cannot support high concurrency for lock in HiveMetastoreCatalog

[ https://issues.apache.org/jira/browse/SPARK-23086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246957#comment-17246957 ] GeoffreyStark commented on SPARK-23086: --- In the case I encountered before, I checked later that

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246946#comment-17246946 ] Hyukjin Kwon commented on SPARK-33713: -- Yeah, I think it's fine. +1 no worries! > Remove

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246945#comment-17246945 ] Hyukjin Kwon commented on SPARK-33727: -- I am facing this error in my local too. Thanks

[jira] [Commented] (SPARK-33729) When refreshing cache, Spark should not use cached plan when recaching data

[ https://issues.apache.org/jira/browse/SPARK-33729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246942#comment-17246942 ] Apache Spark commented on SPARK-33729: -- User 'sunchao' has created a pull request for this issue:

[jira] [Commented] (SPARK-33729) When refreshing cache, Spark should not use cached plan when recaching data

[ https://issues.apache.org/jira/browse/SPARK-33729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246941#comment-17246941 ] Apache Spark commented on SPARK-33729: -- User 'sunchao' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33729) When refreshing cache, Spark should not use cached plan when recaching data

[ https://issues.apache.org/jira/browse/SPARK-33729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33729: Assignee: Apache Spark > When refreshing cache, Spark should not use cached plan when

[jira] [Assigned] (SPARK-33729) When refreshing cache, Spark should not use cached plan when recaching data

[ https://issues.apache.org/jira/browse/SPARK-33729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33729: Assignee: (was: Apache Spark) > When refreshing cache, Spark should not use cached

[jira] [Created] (SPARK-33729) When refreshing cache, Spark should not use cached plan when recaching data

Chao Sun created SPARK-33729: Summary: When refreshing cache, Spark should not use cached plan when recaching data Key: SPARK-33729 URL: https://issues.apache.org/jira/browse/SPARK-33729 Project: Spark

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246934#comment-17246934 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246932#comment-17246932 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246931#comment-17246931 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246930#comment-17246930 ] Apache Spark commented on SPARK-33727: -- User 'holdenk' has created a pull request for this issue:

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246929#comment-17246929 ] Apache Spark commented on SPARK-33727: -- User 'holdenk' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33727: Assignee: (was: Apache Spark) > `gpg: keyserver receive failed: No name` during K8s

[jira] [Assigned] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33727: Assignee: Apache Spark > `gpg: keyserver receive failed: No name` during K8s IT >

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246928#comment-17246928 ] Shane Knapp commented on SPARK-33727: - [~dongjoon] the build that i looked at

[jira] [Assigned] (SPARK-33728) Improve error messages during K8s integration test failure

[ https://issues.apache.org/jira/browse/SPARK-33728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33728: Assignee: (was: Apache Spark) > Improve error messages during K8s integration test

[jira] [Commented] (SPARK-33728) Improve error messages during K8s integration test failure

[ https://issues.apache.org/jira/browse/SPARK-33728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246925#comment-17246925 ] Apache Spark commented on SPARK-33728: -- User 'holdenk' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33728) Improve error messages during K8s integration test failure

[ https://issues.apache.org/jira/browse/SPARK-33728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33728: Assignee: Apache Spark > Improve error messages during K8s integration test failure >

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246923#comment-17246923 ] Holden Karau commented on SPARK-33727: -- So I've seen the keys.gnupg.net key server be flaky on my

[jira] [Commented] (SPARK-33728) Improve error messages during K8s integration test failure

[ https://issues.apache.org/jira/browse/SPARK-33728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246924#comment-17246924 ] Apache Spark commented on SPARK-33728: -- User 'holdenk' has created a pull request for this issue:

[jira] [Created] (SPARK-33728) Improve error messages during K8s integration test failure

Holden Karau created SPARK-33728: Summary: Improve error messages during K8s integration test failure Key: SPARK-33728 URL: https://issues.apache.org/jira/browse/SPARK-33728 Project: Spark

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246899#comment-17246899 ] Dongjoon Hyun commented on SPARK-33727: --- BTW, K8s IT succeed 4 hours ago in this run. So, I guess

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246897#comment-17246897 ] Dongjoon Hyun commented on SPARK-33727: --- The patch landed 28 days ago to recover K8S IT failure. -

[jira] [Comment Edited] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246894#comment-17246894 ] Shane Knapp edited comment on SPARK-33727 at 12/9/20, 11:30 PM: ok, this

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246894#comment-17246894 ] Shane Knapp commented on SPARK-33727: - ok, this is not a failure on the jenkins worker – it's

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246891#comment-17246891 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246890#comment-17246890 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246883#comment-17246883 ] Dongjoon Hyun commented on SPARK-33727: --- Hi, [~shaneknapp]. Could you try `gpg` command in the

[jira] [Commented] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246884#comment-17246884 ] Dongjoon Hyun commented on SPARK-33727: --- cc [~hyukjin.kwon] > `gpg: keyserver receive failed: No

[jira] [Updated] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

[ https://issues.apache.org/jira/browse/SPARK-33727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33727: -- Description: K8s IT fails with gpg: keyserver receive failed: No name. This seems to be

[jira] [Created] (SPARK-33727) `gpg: keyserver receive failed: No name` during K8s IT

Dongjoon Hyun created SPARK-33727: - Summary: `gpg: keyserver receive failed: No name` during K8s IT Key: SPARK-33727 URL: https://issues.apache.org/jira/browse/SPARK-33727 Project: Spark

[jira] [Resolved] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-33725. --- Fix Version/s: 3.2.0 Resolution: Fixed This is resolved via

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246858#comment-17246858 ] Sean R. Owen commented on SPARK-33713: -- I don't think we care much about build history, yes. Don't

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246850#comment-17246850 ] Shane Knapp commented on SPARK-33713: - got it.  gonna rejigger my rejiggering of the JJB configs. >

[jira] [Commented] (SPARK-33724) Allow decommissioning script location to be configured

[ https://issues.apache.org/jira/browse/SPARK-33724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246848#comment-17246848 ] Apache Spark commented on SPARK-33724: -- User 'holdenk' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33724) Allow decommissioning script location to be configured

[ https://issues.apache.org/jira/browse/SPARK-33724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33724: Assignee: Holden Karau (was: Apache Spark) > Allow decommissioning script location to

[jira] [Assigned] (SPARK-33724) Allow decommissioning script location to be configured

[ https://issues.apache.org/jira/browse/SPARK-33724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33724: Assignee: Apache Spark (was: Holden Karau) > Allow decommissioning script location to

[jira] [Commented] (SPARK-33724) Allow decommissioning script location to be configured

[ https://issues.apache.org/jira/browse/SPARK-33724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246847#comment-17246847 ] Apache Spark commented on SPARK-33724: -- User 'holdenk' has created a pull request for this issue:

[jira] [Commented] (SPARK-33716) Decommissioning Race Condition during Pod Snapshot

[ https://issues.apache.org/jira/browse/SPARK-33716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246846#comment-17246846 ] Apache Spark commented on SPARK-33716: -- User 'holdenk' has created a pull request for this issue:

[jira] [Commented] (SPARK-33716) Decommissioning Race Condition during Pod Snapshot

[ https://issues.apache.org/jira/browse/SPARK-33716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246845#comment-17246845 ] Apache Spark commented on SPARK-33716: -- User 'holdenk' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33716) Decommissioning Race Condition during Pod Snapshot

[ https://issues.apache.org/jira/browse/SPARK-33716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33716: Assignee: Apache Spark (was: Holden Karau) > Decommissioning Race Condition during Pod

[jira] [Assigned] (SPARK-33716) Decommissioning Race Condition during Pod Snapshot

[ https://issues.apache.org/jira/browse/SPARK-33716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33716: Assignee: Holden Karau (was: Apache Spark) > Decommissioning Race Condition during Pod

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246833#comment-17246833 ] Dongjoon Hyun commented on SPARK-33713: --- For master and branch-3.1, we don't need a build history.

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246830#comment-17246830 ] Dongjoon Hyun commented on SPARK-33713: --- Oh, this was a request for only `master/branch-3.1`

[jira] [Updated] (SPARK-33726) Duplicate field names causes wrong answers during aggregation

[ https://issues.apache.org/jira/browse/SPARK-33726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Krogen updated SPARK-33726: Labels: correctness (was: ) > Duplicate field names causes wrong answers during aggregation >

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246816#comment-17246816 ] Shane Knapp commented on SPARK-33713: - also, let me think about other sneaky ways of making this

[jira] [Created] (SPARK-33726) Duplicate field names causes wrong answers during aggregation

Yian Liou created SPARK-33726: - Summary: Duplicate field names causes wrong answers during aggregation Key: SPARK-33726 URL: https://issues.apache.org/jira/browse/SPARK-33726 Project: Spark

[jira] [Commented] (SPARK-33726) Duplicate field names causes wrong answers during aggregation

[ https://issues.apache.org/jira/browse/SPARK-33726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246812#comment-17246812 ] Yian Liou commented on SPARK-33726: --- Will create a PR for the issue. > Duplicate field names causes

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246810#comment-17246810 ] Shane Knapp commented on SPARK-33713: - fwiw, here's what the new and sexy build names will be:

[jira] [Comment Edited] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246810#comment-17246810 ] Shane Knapp edited comment on SPARK-33713 at 12/9/20, 8:42 PM: --- fwiw,

[jira] [Commented] (SPARK-33713) Remove `hive-2.3` post fix at master/branch-3.1 Jenkins job names

[ https://issues.apache.org/jira/browse/SPARK-33713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246808#comment-17246808 ] Shane Knapp commented on SPARK-33713: - hmm.  so while i heartily endorse this, there will be a

[jira] [Updated] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33725: -- Affects Version/s: 3.1.0 2.4.7 3.0.1 > Upgrade

[jira] [Updated] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33725: -- Issue Type: Bug (was: Improvement) > Upgrade snappy-java to 1.1.8.2 >

[jira] [Assigned] (SPARK-32920) Add support in Spark driver to coordinate the finalization of the push/merge phase in push-based shuffle for a given shuffle and the initiation of the reduce stage

[ https://issues.apache.org/jira/browse/SPARK-32920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-32920: Assignee: (was: Apache Spark) > Add support in Spark driver to coordinate the

[jira] [Commented] (SPARK-32920) Add support in Spark driver to coordinate the finalization of the push/merge phase in push-based shuffle for a given shuffle and the initiation of the reduce stage

[ https://issues.apache.org/jira/browse/SPARK-32920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246804#comment-17246804 ] Apache Spark commented on SPARK-32920: -- User 'venkata91' has created a pull request for this issue:

[jira] [Assigned] (SPARK-32920) Add support in Spark driver to coordinate the finalization of the push/merge phase in push-based shuffle for a given shuffle and the initiation of the reduce stage

[ https://issues.apache.org/jira/browse/SPARK-32920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-32920: Assignee: Apache Spark > Add support in Spark driver to coordinate the finalization of

[jira] [Commented] (SPARK-32920) Add support in Spark driver to coordinate the finalization of the push/merge phase in push-based shuffle for a given shuffle and the initiation of the reduce stage

[ https://issues.apache.org/jira/browse/SPARK-32920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246803#comment-17246803 ] Apache Spark commented on SPARK-32920: -- User 'venkata91' has created a pull request for this issue:

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246799#comment-17246799 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33725: Assignee: L. C. Hsieh (was: Apache Spark) > Upgrade snappy-java to 1.1.8.2 >

[jira] [Commented] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246798#comment-17246798 ] Apache Spark commented on SPARK-33725: -- User 'viirya' has created a pull request for this issue:

[jira] [Assigned] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

[ https://issues.apache.org/jira/browse/SPARK-33725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-33725: Assignee: Apache Spark (was: L. C. Hsieh) > Upgrade snappy-java to 1.1.8.2 >

[jira] [Updated] (SPARK-33261) Allow people to extend the pod feature steps

[ https://issues.apache.org/jira/browse/SPARK-33261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33261: -- Parent: (was: SPARK-33005) Issue Type: Improvement (was: Sub-task) > Allow

[jira] [Updated] (SPARK-33261) Allow people to extend the pod feature steps

[ https://issues.apache.org/jira/browse/SPARK-33261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-33261: -- Affects Version/s: (was: 3.1.0) 3.2.0 > Allow people to extend the

[jira] [Created] (SPARK-33725) Upgrade snappy-java to 1.1.8.2

L. C. Hsieh created SPARK-33725: --- Summary: Upgrade snappy-java to 1.1.8.2 Key: SPARK-33725 URL: https://issues.apache.org/jira/browse/SPARK-33725 Project: Spark Issue Type: Improvement

[jira] [Created] (SPARK-33724) Allow decommissioning script location to be configured

Holden Karau created SPARK-33724: Summary: Allow decommissioning script location to be configured Key: SPARK-33724 URL: https://issues.apache.org/jira/browse/SPARK-33724 Project: Spark Issue

[jira] [Resolved] (SPARK-33722) Handle DELETE in ReplaceNullWithFalseInPredicate

[ https://issues.apache.org/jira/browse/SPARK-33722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun resolved SPARK-33722. --- Fix Version/s: 3.2.0 Resolution: Fixed Issue resolved by pull request 30688

[jira] [Assigned] (SPARK-33722) Handle DELETE in ReplaceNullWithFalseInPredicate

[ https://issues.apache.org/jira/browse/SPARK-33722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun reassigned SPARK-33722: - Assignee: Anton Okolnychyi > Handle DELETE in ReplaceNullWithFalseInPredicate >

[jira] [Commented] (SPARK-32110) -0.0 vs 0.0 is inconsistent

[ https://issues.apache.org/jira/browse/SPARK-32110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246727#comment-17246727 ] Dongjoon Hyun commented on SPARK-32110: --- How do you think about the above [~revans2]'s comment,

[jira] [Commented] (SPARK-18105) LZ4 failed to decompress a stream of shuffled data

[ https://issues.apache.org/jira/browse/SPARK-18105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246725#comment-17246725 ] Dongjoon Hyun commented on SPARK-18105: --- Apache Spark 3.x is using lz4-java-1.7.1.jar and this

[jira] [Commented] (SPARK-33722) Handle DELETE in ReplaceNullWithFalseInPredicate

[ https://issues.apache.org/jira/browse/SPARK-33722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246722#comment-17246722 ] Apache Spark commented on SPARK-33722: -- User 'aokolnychyi' has created a pull request for this

  1   2   >