[jira] [Commented] (SPARK-17057) ProbabilisticClassifierModels' prediction more reasonable with multi zero thresholds

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

[jira] [Assigned] (SPARK-17057) ProbabilisticClassifierModels' prediction more reasonable with multi zero thresholds

[ https://issues.apache.org/jira/browse/SPARK-17057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17057: Assignee: (was: Apache Spark) > ProbabilisticClassifierModels' prediction more

[jira] [Assigned] (SPARK-17057) ProbabilisticClassifierModels' prediction more reasonable with multi zero thresholds

[ https://issues.apache.org/jira/browse/SPARK-17057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17057: Assignee: Apache Spark > ProbabilisticClassifierModels' prediction more reasonable with

[jira] [Created] (SPARK-17057) ProbabilisticClassifierModels' prediction more reasonable with multi zero thresholds

zhengruifeng created SPARK-17057: Summary: ProbabilisticClassifierModels' prediction more reasonable with multi zero thresholds Key: SPARK-17057 URL: https://issues.apache.org/jira/browse/SPARK-17057

[jira] [Assigned] (SPARK-17056) Fix a wrong assert in MemoryStore

[ https://issues.apache.org/jira/browse/SPARK-17056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17056: Assignee: (was: Apache Spark) > Fix a wrong assert in MemoryStore >

[jira] [Commented] (SPARK-17056) Fix a wrong assert in MemoryStore

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

[jira] [Assigned] (SPARK-17056) Fix a wrong assert in MemoryStore

[ https://issues.apache.org/jira/browse/SPARK-17056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17056: Assignee: Apache Spark > Fix a wrong assert in MemoryStore >

[jira] [Created] (SPARK-17056) Fix a wrong assert in MemoryStore

Liang-Chi Hsieh created SPARK-17056: --- Summary: Fix a wrong assert in MemoryStore Key: SPARK-17056 URL: https://issues.apache.org/jira/browse/SPARK-17056 Project: Spark Issue Type: Bug

[jira] [Updated] (SPARK-17055) add labelKFold to CrossValidator

[ https://issues.apache.org/jira/browse/SPARK-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated SPARK-17055: Description: Current CrossValidator only supports k-fold, which randomly divides all the samples in k

[jira] [Updated] (SPARK-17055) add labelKFold to CrossValidator

[ https://issues.apache.org/jira/browse/SPARK-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent updated SPARK-17055: Affects Version/s: (was: 2.0.0) > add labelKFold to CrossValidator >

[jira] [Assigned] (SPARK-17055) add labelKFold to CrossValidator

[ https://issues.apache.org/jira/browse/SPARK-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17055: Assignee: Apache Spark > add labelKFold to CrossValidator >

[jira] [Assigned] (SPARK-17055) add labelKFold to CrossValidator

[ https://issues.apache.org/jira/browse/SPARK-17055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17055: Assignee: (was: Apache Spark) > add labelKFold to CrossValidator >

[jira] [Commented] (SPARK-17055) add labelKFold to CrossValidator

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

[jira] [Created] (SPARK-17055) add labelKFold to CrossValidator

Vincent created SPARK-17055: --- Summary: add labelKFold to CrossValidator Key: SPARK-17055 URL: https://issues.apache.org/jira/browse/SPARK-17055 Project: Spark Issue Type: New Feature

[jira] [Comment Edited] (SPARK-6235) Address various 2G limits

[ https://issues.apache.org/jira/browse/SPARK-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420554#comment-15420554 ] Guoqiang Li edited comment on SPARK-6235 at 8/15/16 1:53 AM: - [~hvanhovell]

[jira] [Commented] (SPARK-6235) Address various 2G limits

[ https://issues.apache.org/jira/browse/SPARK-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420554#comment-15420554 ] Guoqiang Li commented on SPARK-6235: [~hvanhovell] The main changes. 1. Replace DiskStore method

[jira] [Commented] (SPARK-17054) SparkR can not run in yarn-cluster mode on mac os

[ https://issues.apache.org/jira/browse/SPARK-17054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420553#comment-15420553 ] Jeff Zhang commented on SPARK-17054: Although I can fix it by using the correct cache dir for mac OS,

[jira] [Created] (SPARK-17054) SparkR can not run in yarn-cluster mode on mac os

Jeff Zhang created SPARK-17054: -- Summary: SparkR can not run in yarn-cluster mode on mac os Key: SPARK-17054 URL: https://issues.apache.org/jira/browse/SPARK-17054 Project: Spark Issue Type:

[jira] [Commented] (SPARK-16781) java launched by PySpark as gateway may not be the same java used in the spark environment

[ https://issues.apache.org/jira/browse/SPARK-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420547#comment-15420547 ] Jeff Zhang commented on SPARK-16781: JAVA_HOME will be set by yarn, not sure about other cluster

[jira] [Commented] (SPARK-14165) NoSuchElementException: None.get when joining DataFrames with Seq of fields of different case

[ https://issues.apache.org/jira/browse/SPARK-14165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420541#comment-15420541 ] Jacek Laskowski commented on SPARK-14165: - Thanks [~dongjoon] for looking into it. Yes, the more

[jira] [Commented] (SPARK-17035) Conversion of datetime.max to microseconds produces incorrect value

[ https://issues.apache.org/jira/browse/SPARK-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420534#comment-15420534 ] Michael Styles commented on SPARK-17035: I have a fix for this issue if you would like to assign

[jira] [Commented] (SPARK-14165) NoSuchElementException: None.get when joining DataFrames with Seq of fields of different case

[ https://issues.apache.org/jira/browse/SPARK-14165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420527#comment-15420527 ] Dongjoon Hyun commented on SPARK-14165: --- I'm wondering if we need to fix the example in your

[jira] [Commented] (SPARK-14165) NoSuchElementException: None.get when joining DataFrames with Seq of fields of different case

[ https://issues.apache.org/jira/browse/SPARK-14165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420525#comment-15420525 ] Dongjoon Hyun commented on SPARK-14165: --- Hi, [~ja...@japila.pl]. Spark 2.0 seems to be released

[jira] [Commented] (SPARK-17053) Spark ignores hive.exec.drop.ignorenonexistent=true option

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420515#comment-15420515 ] Dongjoon Hyun commented on SPARK-17053: --- Yep. I closed the PR, too. Thank you for the quick

[jira] [Closed] (SPARK-17053) Spark ignores hive.exec.drop.ignorenonexistent=true option

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin closed SPARK-17053. --- Resolution: Won't Fix > Spark ignores hive.exec.drop.ignorenonexistent=true option >

[jira] [Commented] (SPARK-17053) Spark ignores hive.exec.drop.ignorenonexistent=true option

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420507#comment-15420507 ] Reynold Xin commented on SPARK-17053: - It was by accident that this was supported, because Spark

[jira] [Comment Edited] (SPARK-17053) Spark ignores hive.exec.drop.ignorenonexistent=true option

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420507#comment-15420507 ] Reynold Xin edited comment on SPARK-17053 at 8/14/16 10:32 PM: --- It was by

[jira] [Commented] (SPARK-11374) skip.header.line.count is ignored in HiveContext

[ https://issues.apache.org/jira/browse/SPARK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420503#comment-15420503 ] Dongjoon Hyun commented on SPARK-11374: --- Hi [~stephane.maa...@gmail.com], Thank you for comments.

[jira] [Commented] (SPARK-11374) skip.header.line.count is ignored in HiveContext

[ https://issues.apache.org/jira/browse/SPARK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420491#comment-15420491 ] Stephane Maarek commented on SPARK-11374: - Hi, Thanks for the PR. Can you also test for the

[jira] [Commented] (SPARK-11374) skip.header.line.count is ignored in HiveContext

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

[jira] [Assigned] (SPARK-11374) skip.header.line.count is ignored in HiveContext

[ https://issues.apache.org/jira/browse/SPARK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-11374: Assignee: (was: Apache Spark) > skip.header.line.count is ignored in HiveContext >

[jira] [Assigned] (SPARK-11374) skip.header.line.count is ignored in HiveContext

[ https://issues.apache.org/jira/browse/SPARK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-11374: Assignee: Apache Spark > skip.header.line.count is ignored in HiveContext >

[jira] [Commented] (SPARK-2243) Support multiple SparkContexts in the same JVM

[ https://issues.apache.org/jira/browse/SPARK-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420467#comment-15420467 ] Stephen Boesch commented on SPARK-2243: --- Given this were not going to be fixed: please update

[jira] [Commented] (SPARK-17053) Spark ignores hive.exec.drop.ignorenonexistent=true option

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420456#comment-15420456 ] Dongjoon Hyun commented on SPARK-17053: --- Oh, I see! > Spark ignores

[jira] [Updated] (SPARK-17053) Spark ignores hive.exec.drop.ignorenonexistent=true option

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gokhan Civan updated SPARK-17053: - Summary: Spark ignores hive.exec.drop.ignorenonexistent=true option (was: DROP statement should

[jira] [Assigned] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17053: Assignee: (was: Apache Spark) > DROP statement should not require IF EXISTS >

[jira] [Assigned] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17053: Assignee: Apache Spark > DROP statement should not require IF EXISTS >

[jira] [Commented] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420443#comment-15420443 ] Qifan Pu commented on SPARK-17053: -- [~dongjoon]sorry, it was a accident click. > DROP statement should

[jira] [Comment Edited] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420430#comment-15420430 ] Dongjoon Hyun edited comment on SPARK-17053 at 8/14/16 6:32 PM: Oh, I

[jira] [Commented] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420430#comment-15420430 ] Dongjoon Hyun commented on SPARK-17053: --- Oh, I mentioned wrong username. Hi, [~qifan]. Could you

[jira] [Reopened] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun reopened SPARK-17053: --- Hi, [~superpanpan]. Could you leave some comment why you close this issue with `WON'T FIX`? >

[jira] [Assigned] (SPARK-16967) Collect Mesos support code into a module/profile

[ https://issues.apache.org/jira/browse/SPARK-16967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16967: Assignee: (was: Apache Spark) > Collect Mesos support code into a module/profile >

[jira] [Commented] (SPARK-16967) Collect Mesos support code into a module/profile

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

[jira] [Assigned] (SPARK-16967) Collect Mesos support code into a module/profile

[ https://issues.apache.org/jira/browse/SPARK-16967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16967: Assignee: Apache Spark > Collect Mesos support code into a module/profile >

[jira] [Resolved] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qifan Pu resolved SPARK-17053. -- Resolution: Won't Fix > DROP statement should not require IF EXISTS >

[jira] [Assigned] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17053: Assignee: (was: Apache Spark) > DROP statement should not require IF EXISTS >

[jira] [Commented] (SPARK-17053) DROP statement should not require IF EXISTS

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

[jira] [Assigned] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17053: Assignee: Apache Spark > DROP statement should not require IF EXISTS >

[jira] [Commented] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420405#comment-15420405 ] Dongjoon Hyun commented on SPARK-17053: --- Oh, I see what you mean. Yes, indeed. Currently, Spark

[jira] [Commented] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420398#comment-15420398 ] Gokhan Civan commented on SPARK-17053: -- I saw a lot of code base that used DROP without IF EXISTS,

[jira] [Commented] (SPARK-17053) DROP statement should not require IF EXISTS

[ https://issues.apache.org/jira/browse/SPARK-17053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420392#comment-15420392 ] Sean Owen commented on SPARK-17053: --- That would imply that "IF EXISTS" is redundant, that the behavior

[jira] [Created] (SPARK-17053) DROP statement should not require IF EXISTS

Gokhan Civan created SPARK-17053: Summary: DROP statement should not require IF EXISTS Key: SPARK-17053 URL: https://issues.apache.org/jira/browse/SPARK-17053 Project: Spark Issue Type: Bug

[jira] [Assigned] (SPARK-17052) Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala

[ https://issues.apache.org/jira/browse/SPARK-17052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17052: Assignee: (was: Apache Spark) > Remove Duplicate Test Cases auto_join from

[jira] [Assigned] (SPARK-17052) Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala

[ https://issues.apache.org/jira/browse/SPARK-17052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17052: Assignee: Apache Spark > Remove Duplicate Test Cases auto_join from

[jira] [Commented] (SPARK-17052) Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala

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

[jira] [Updated] (SPARK-17052) Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala

[ https://issues.apache.org/jira/browse/SPARK-17052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17052: Priority: Minor (was: Major) > Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala >

[jira] [Created] (SPARK-17052) Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala

Xiao Li created SPARK-17052: --- Summary: Remove Duplicate Test Cases auto_join from HiveCompatibilitySuite.scala Key: SPARK-17052 URL: https://issues.apache.org/jira/browse/SPARK-17052 Project: Spark

[jira] [Commented] (SPARK-17051) we should use hadoopConf in InsertIntoHiveTable

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

[jira] [Assigned] (SPARK-17051) we should use hadoopConf in InsertIntoHiveTable

[ https://issues.apache.org/jira/browse/SPARK-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17051: Assignee: Wenchen Fan (was: Apache Spark) > we should use hadoopConf in

[jira] [Assigned] (SPARK-17051) we should use hadoopConf in InsertIntoHiveTable

[ https://issues.apache.org/jira/browse/SPARK-17051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17051: Assignee: Apache Spark (was: Wenchen Fan) > we should use hadoopConf in

[jira] [Created] (SPARK-17051) we should use hadoopConf in InsertIntoHiveTable

Wenchen Fan created SPARK-17051: --- Summary: we should use hadoopConf in InsertIntoHiveTable Key: SPARK-17051 URL: https://issues.apache.org/jira/browse/SPARK-17051 Project: Spark Issue Type:

[jira] [Commented] (SPARK-17050) Improve initKMeansParallel with treeAggregate

[ https://issues.apache.org/jira/browse/SPARK-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420336#comment-15420336 ] Sean Owen commented on SPARK-17050: --- [~WeichenXu123] this sounds quite related to

[jira] [Assigned] (SPARK-17050) Improve initKMeansParallel with treeAggregate

[ https://issues.apache.org/jira/browse/SPARK-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17050: Assignee: Apache Spark > Improve initKMeansParallel with treeAggregate >

[jira] [Assigned] (SPARK-17050) Improve initKMeansParallel with treeAggregate

[ https://issues.apache.org/jira/browse/SPARK-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17050: Assignee: (was: Apache Spark) > Improve initKMeansParallel with treeAggregate >

[jira] [Commented] (SPARK-17050) Improve initKMeansParallel with treeAggregate

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

[jira] [Created] (SPARK-17050) Improve initKMeansParallel with treeAggregate

Weichen Xu created SPARK-17050: -- Summary: Improve initKMeansParallel with treeAggregate Key: SPARK-17050 URL: https://issues.apache.org/jira/browse/SPARK-17050 Project: Spark Issue Type:

[jira] [Reopened] (SPARK-6273) Got error when one table's alias name is the same with other table's column name

[ https://issues.apache.org/jira/browse/SPARK-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen reopened SPARK-6273: -- > Got error when one table's alias name is the same with other table's column > name >

[jira] [Resolved] (SPARK-6273) Got error when one table's alias name is the same with other table's column name

[ https://issues.apache.org/jira/browse/SPARK-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-6273. -- Resolution: Duplicate Fix Version/s: (was: 2.0.0) > Got error when one table's alias name is

[jira] [Updated] (SPARK-17027) PolynomialExpansion.choose is prone to integer overflow

[ https://issues.apache.org/jira/browse/SPARK-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-17027: -- Fix Version/s: (was: 1.6.3) > PolynomialExpansion.choose is prone to integer overflow >

[jira] [Resolved] (SPARK-16843) Select features according to a percentile of the highest scores of ChiSqSelector

[ https://issues.apache.org/jira/browse/SPARK-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16843. --- Resolution: Duplicate I'd like to call this a subset of the more general changes for chi-squared

[jira] [Resolved] (SPARK-16885) Spark shell failed to run in yarn-client mode

[ https://issues.apache.org/jira/browse/SPARK-16885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16885. --- Resolution: Not A Problem > Spark shell failed to run in yarn-client mode >

[jira] [Updated] (SPARK-17027) PolynomialExpansion.choose is prone to integer overflow

[ https://issues.apache.org/jira/browse/SPARK-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-17027: -- Assignee: Maciej Szymkiewicz > PolynomialExpansion.choose is prone to integer overflow >

[jira] [Resolved] (SPARK-17027) PolynomialExpansion.choose is prone to integer overflow

[ https://issues.apache.org/jira/browse/SPARK-17027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-17027. --- Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 1.6.3