[jira] [Commented] (SPARK-16965) Fix bound checking for SparseVector

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

[jira] [Assigned] (SPARK-16965) Fix bound checking for SparseVector

[ https://issues.apache.org/jira/browse/SPARK-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16965: Assignee: (was: Apache Spark) > Fix bound checking for SparseVector >

[jira] [Assigned] (SPARK-16965) Fix bound checking for SparseVector

[ https://issues.apache.org/jira/browse/SPARK-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16965: Assignee: Apache Spark > Fix bound checking for SparseVector >

[jira] [Updated] (SPARK-16965) Fix bound checking for SparseVector

[ https://issues.apache.org/jira/browse/SPARK-16965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated SPARK-16965: --- Component/s: PySpark MLlib > Fix bound checking for SparseVector >

[jira] [Resolved] (SPARK-16887) Add SPARK_DIST_CLASSPATH to LAUNCH_CLASSPATH

[ https://issues.apache.org/jira/browse/SPARK-16887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai resolved SPARK-16887. -- Resolution: Won't Fix > Add SPARK_DIST_CLASSPATH to LAUNCH_CLASSPATH >

[jira] [Created] (SPARK-16965) Fix bound checking for SparseVector

Jeff Zhang created SPARK-16965: -- Summary: Fix bound checking for SparseVector Key: SPARK-16965 URL: https://issues.apache.org/jira/browse/SPARK-16965 Project: Spark Issue Type: Bug Affects

[jira] [Assigned] (SPARK-16964) Remove private[sql] and private[spark] from sql.execution package

[ https://issues.apache.org/jira/browse/SPARK-16964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16964: Assignee: Apache Spark (was: Reynold Xin) > Remove private[sql] and private[spark] from

[jira] [Commented] (SPARK-16964) Remove private[sql] and private[spark] from sql.execution package

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

[jira] [Assigned] (SPARK-16964) Remove private[sql] and private[spark] from sql.execution package

[ https://issues.apache.org/jira/browse/SPARK-16964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16964: Assignee: Reynold Xin (was: Apache Spark) > Remove private[sql] and private[spark] from

[jira] [Updated] (SPARK-16964) Remove private[sql] and private[spark] from sql.execution package

[ https://issues.apache.org/jira/browse/SPARK-16964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin updated SPARK-16964: Description: The execution package is meant to be internal, and as a result it does not make

[jira] [Created] (SPARK-16964) Remove private[sql] and private[spark] from sql.execution package

Reynold Xin created SPARK-16964: --- Summary: Remove private[sql] and private[spark] from sql.execution package Key: SPARK-16964 URL: https://issues.apache.org/jira/browse/SPARK-16964 Project: Spark

[jira] [Commented] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

[ https://issues.apache.org/jira/browse/SPARK-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412893#comment-15412893 ] Dongjoon Hyun commented on SPARK-16955: --- Hi, [~yhuai]. Could you review the PR? The root cause was

[jira] [Comment Edited] (SPARK-16951) Alternative implementation of NOT IN to Anti-join

[ https://issues.apache.org/jira/browse/SPARK-16951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412882#comment-15412882 ] Nattavut Sutyanyong edited comment on SPARK-16951 at 8/9/16 3:54 AM: -

[jira] [Commented] (SPARK-16951) Alternative implementation of NOT IN to Anti-join

[ https://issues.apache.org/jira/browse/SPARK-16951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412882#comment-15412882 ] Nattavut Sutyanyong commented on SPARK-16951: - The following output is tested on Spark master

[jira] [Commented] (SPARK-16951) Alternative implementation of NOT IN to Anti-join

[ https://issues.apache.org/jira/browse/SPARK-16951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412878#comment-15412878 ] Nattavut Sutyanyong commented on SPARK-16951: - The semantic of {{NOT IN}} is described in

[jira] [Updated] (SPARK-12920) Honor "spark.ui.retainedStages" to reduce mem-pressure

[ https://issues.apache.org/jira/browse/SPARK-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Balamohan updated SPARK-12920: - Summary: Honor "spark.ui.retainedStages" to reduce mem-pressure (was: Fix high CPU

[jira] [Commented] (SPARK-16804) Correlated subqueries containing non-deterministic operators return incorrect results

[ https://issues.apache.org/jira/browse/SPARK-16804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412849#comment-15412849 ] Nattavut Sutyanyong commented on SPARK-16804: - Thank you, @hvanhovell, for merging my PR. >

[jira] [Assigned] (SPARK-16963) Change Source API so that sources do not need to keep unbounded state

[ https://issues.apache.org/jira/browse/SPARK-16963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16963: Assignee: Apache Spark > Change Source API so that sources do not need to keep unbounded

[jira] [Assigned] (SPARK-16963) Change Source API so that sources do not need to keep unbounded state

[ https://issues.apache.org/jira/browse/SPARK-16963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16963: Assignee: (was: Apache Spark) > Change Source API so that sources do not need to keep

[jira] [Commented] (SPARK-16963) Change Source API so that sources do not need to keep unbounded state

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

[jira] [Updated] (SPARK-16610) When writing ORC files, orc.compress should not be overridden if users do not set "compression" in the options

[ https://issues.apache.org/jira/browse/SPARK-16610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan updated SPARK-16610: Assignee: Hyukjin Kwon > When writing ORC files, orc.compress should not be overridden if users do

[jira] [Resolved] (SPARK-16610) When writing ORC files, orc.compress should not be overridden if users do not set "compression" in the options

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

[jira] [Created] (SPARK-16963) Change Source API so that sources do not need to keep unbounded state

Frederick Reiss created SPARK-16963: --- Summary: Change Source API so that sources do not need to keep unbounded state Key: SPARK-16963 URL: https://issues.apache.org/jira/browse/SPARK-16963 Project:

[jira] [Assigned] (SPARK-16952) [MESOS] MesosCoarseGrainedSchedulerBackend requires spark.mesos.executor.home even if spark.executor.uri is set

[ https://issues.apache.org/jira/browse/SPARK-16952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16952: Assignee: (was: Apache Spark) > [MESOS] MesosCoarseGrainedSchedulerBackend requires

[jira] [Assigned] (SPARK-16952) [MESOS] MesosCoarseGrainedSchedulerBackend requires spark.mesos.executor.home even if spark.executor.uri is set

[ https://issues.apache.org/jira/browse/SPARK-16952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16952: Assignee: Apache Spark > [MESOS] MesosCoarseGrainedSchedulerBackend requires

[jira] [Commented] (SPARK-16952) [MESOS] MesosCoarseGrainedSchedulerBackend requires spark.mesos.executor.home even if spark.executor.uri is set

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

[jira] [Created] (SPARK-16962) Unsafe accesses (Platform.getLong()) not supported on unaligned boundaries in SPARC/Solaris

Suman Somasundar created SPARK-16962: Summary: Unsafe accesses (Platform.getLong()) not supported on unaligned boundaries in SPARC/Solaris Key: SPARK-16962 URL:

[jira] [Issue Comment Deleted] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

[ https://issues.apache.org/jira/browse/SPARK-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas updated SPARK-16961: - Comment: was deleted (was: I am submitting a PR) > Utils.randomizeInPlace does not shuffle arrays

[jira] [Assigned] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

[ https://issues.apache.org/jira/browse/SPARK-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16961: Assignee: (was: Apache Spark) > Utils.randomizeInPlace does not shuffle arrays

[jira] [Commented] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

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

[jira] [Assigned] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

[ https://issues.apache.org/jira/browse/SPARK-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16961: Assignee: Apache Spark > Utils.randomizeInPlace does not shuffle arrays uniformly >

[jira] [Resolved] (SPARK-16563) Repeat calling Spark SQL thrift server fetchResults return empty for ExecuteStatement operation

[ https://issues.apache.org/jira/browse/SPARK-16563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin resolved SPARK-16563. - Resolution: Fixed Assignee: Gu Huiqin Alice Fix Version/s: 2.1.0

[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=15412727#comment-15412727 ] Brian commented on SPARK-6235: -- How is it possible that Spark 2.0 comes and and this bug isn't solved? A

[jira] [Resolved] (SPARK-16898) Adds argument type information for typed logical plan like MapElements, TypedFilter, and AppendColumn

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

[jira] [Updated] (SPARK-16898) Adds argument type information for typed logical plan like MapElements, TypedFilter, and AppendColumn

[ https://issues.apache.org/jira/browse/SPARK-16898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan updated SPARK-16898: Assignee: Sean Zhong > Adds argument type information for typed logical plan like MapElements, >

[jira] [Commented] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

[ https://issues.apache.org/jira/browse/SPARK-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412705#comment-15412705 ] Nicholas commented on SPARK-16961: -- I am submitting a PR > Utils.randomizeInPlace does not shuffle

[jira] [Updated] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

[ https://issues.apache.org/jira/browse/SPARK-16961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas updated SPARK-16961: - Description: The Utils.randomizeInPlace method, which is meant to uniformly shuffle the elements on an

[jira] [Created] (SPARK-16961) Utils.randomizeInPlace does not shuffle arrays uniformly

Nicholas created SPARK-16961: Summary: Utils.randomizeInPlace does not shuffle arrays uniformly Key: SPARK-16961 URL: https://issues.apache.org/jira/browse/SPARK-16961 Project: Spark Issue Type:

[jira] [Assigned] (SPARK-16960) Deprecate approxCountDistinct, toDegrees and toRadians according to FunctionRegistry in Scala and Python

[ https://issues.apache.org/jira/browse/SPARK-16960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16960: Assignee: (was: Apache Spark) > Deprecate approxCountDistinct, toDegrees and

[jira] [Commented] (SPARK-16960) Deprecate approxCountDistinct, toDegrees and toRadians according to FunctionRegistry in Scala and Python

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

[jira] [Created] (SPARK-16960) Deprecate approxCountDistinct, toDegrees and toRadians according to FunctionRegistry in Scala and Python

Hyukjin Kwon created SPARK-16960: Summary: Deprecate approxCountDistinct, toDegrees and toRadians according to FunctionRegistry in Scala and Python Key: SPARK-16960 URL:

[jira] [Assigned] (SPARK-16960) Deprecate approxCountDistinct, toDegrees and toRadians according to FunctionRegistry in Scala and Python

[ https://issues.apache.org/jira/browse/SPARK-16960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16960: Assignee: Apache Spark > Deprecate approxCountDistinct, toDegrees and toRadians according

[jira] [Commented] (SPARK-16959) Table Comment in the CatalogTable returned from HiveMetastore is Always Empty

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

[jira] [Assigned] (SPARK-16959) Table Comment in the CatalogTable returned from HiveMetastore is Always Empty

[ https://issues.apache.org/jira/browse/SPARK-16959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16959: Assignee: (was: Apache Spark) > Table Comment in the CatalogTable returned from

[jira] [Assigned] (SPARK-16959) Table Comment in the CatalogTable returned from HiveMetastore is Always Empty

[ https://issues.apache.org/jira/browse/SPARK-16959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16959: Assignee: Apache Spark > Table Comment in the CatalogTable returned from HiveMetastore is

[jira] [Created] (SPARK-16959) Table Comment in the CatalogTable returned from HiveMetastore is Always Empty

Xiao Li created SPARK-16959: --- Summary: Table Comment in the CatalogTable returned from HiveMetastore is Always Empty Key: SPARK-16959 URL: https://issues.apache.org/jira/browse/SPARK-16959 Project: Spark

[jira] [Resolved] (SPARK-16749) Clean-up OffsetWindowFrame

[ https://issues.apache.org/jira/browse/SPARK-16749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai resolved SPARK-16749. -- Resolution: Fixed Fix Version/s: 2.1.0 Issue resolved by pull request 14376

[jira] [Commented] (SPARK-12909) Spark on Mesos accessing Secured HDFS w/Kerberos

[ https://issues.apache.org/jira/browse/SPARK-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412624#comment-15412624 ] Michael Gummelt commented on SPARK-12909: - DC/OS Spark has this functionality, and we'll be

[jira] [Resolved] (SPARK-16779) Fix unnecessary use of postfix operations

[ https://issues.apache.org/jira/browse/SPARK-16779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-16779. Resolution: Fixed Assignee: holdenk Fix Version/s: 2.1.0 > Fix unnecessary

[jira] [Assigned] (SPARK-16958) Reuse subqueries within single query

[ https://issues.apache.org/jira/browse/SPARK-16958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16958: Assignee: Apache Spark (was: Davies Liu) > Reuse subqueries within single query >

[jira] [Assigned] (SPARK-16958) Reuse subqueries within single query

[ https://issues.apache.org/jira/browse/SPARK-16958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16958: Assignee: Davies Liu (was: Apache Spark) > Reuse subqueries within single query >

[jira] [Commented] (SPARK-16958) Reuse subqueries within single query

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

[jira] [Created] (SPARK-16958) Reuse subqueries within single query

Davies Liu created SPARK-16958: -- Summary: Reuse subqueries within single query Key: SPARK-16958 URL: https://issues.apache.org/jira/browse/SPARK-16958 Project: Spark Issue Type: New Feature

[jira] [Updated] (SPARK-11150) Dynamic partition pruning

[ https://issues.apache.org/jira/browse/SPARK-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davies Liu updated SPARK-11150: --- Assignee: (was: Davies Liu) > Dynamic partition pruning > - > >

[jira] [Updated] (SPARK-11150) Dynamic partition pruning

[ https://issues.apache.org/jira/browse/SPARK-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davies Liu updated SPARK-11150: --- Target Version/s: (was: 2.1.0) > Dynamic partition pruning > - > >

[jira] [Commented] (SPARK-16718) gbm-style treeboost

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

[jira] [Assigned] (SPARK-16718) gbm-style treeboost

[ https://issues.apache.org/jira/browse/SPARK-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16718: Assignee: Vladimir Feinberg (was: Apache Spark) > gbm-style treeboost >

[jira] [Assigned] (SPARK-16718) gbm-style treeboost

[ https://issues.apache.org/jira/browse/SPARK-16718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16718: Assignee: Apache Spark (was: Vladimir Feinberg) > gbm-style treeboost >

[jira] [Assigned] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

[ https://issues.apache.org/jira/browse/SPARK-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16955: Assignee: (was: Apache Spark) > Using ordinals in ORDER BY causes an analysis error

[jira] [Assigned] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

[ https://issues.apache.org/jira/browse/SPARK-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16955: Assignee: Apache Spark > Using ordinals in ORDER BY causes an analysis error when the

[jira] [Commented] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

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

[jira] [Resolved] (SPARK-12326) Move GBT implementation from spark.mllib to spark.ml

[ https://issues.apache.org/jira/browse/SPARK-12326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-12326. --- Resolution: Done > Move GBT implementation from spark.mllib to spark.ml >

[jira] [Resolved] (SPARK-12383) Move unit tests for GBT from spark.mllib to spark.ml

[ https://issues.apache.org/jira/browse/SPARK-12383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-12383. --- Resolution: Duplicate > Move unit tests for GBT from spark.mllib to spark.ml >

[jira] [Updated] (SPARK-12326) Move GBT implementation from spark.mllib to spark.ml

[ https://issues.apache.org/jira/browse/SPARK-12326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-12326: -- Priority: Minor (was: Major) > Move GBT implementation from spark.mllib to spark.ml >

[jira] [Resolved] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-12381. --- Resolution: Duplicate > Copy public decision tree helper classes from spark.mllib to spark.ml and >

[jira] [Commented] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412476#comment-15412476 ] Seth Hendrickson commented on SPARK-12381: -- I haven't looked at this in a while. Please feel

[jira] [Commented] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

[ https://issues.apache.org/jira/browse/SPARK-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412475#comment-15412475 ] Dongjoon Hyun commented on SPARK-16955: --- `ResolveAggregateFunctions` seems to have a bug to drop

[jira] [Commented] (SPARK-11150) Dynamic partition pruning

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

[jira] [Updated] (SPARK-16957) Use weighted midpoints for split values.

[ https://issues.apache.org/jira/browse/SPARK-16957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph K. Bradley updated SPARK-16957: -- Priority: Trivial (was: Major) > Use weighted midpoints for split values. >

[jira] [Commented] (SPARK-11638) Run Spark on Mesos with bridge networking

[ https://issues.apache.org/jira/browse/SPARK-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412461#comment-15412461 ] Michael Gummelt commented on SPARK-11638: - [~radekg] > The only advantage we had was using the

[jira] [Commented] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412459#comment-15412459 ] Vladimir Feinberg commented on SPARK-12381: --- Yeah, that'd be a good idea. > Copy public

[jira] [Updated] (SPARK-16957) Use weighted midpoints for split values.

[ https://issues.apache.org/jira/browse/SPARK-16957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Feinberg updated SPARK-16957: -- Issue Type: Improvement (was: Sub-task) Parent: (was: SPARK-14045) > Use

[jira] [Created] (SPARK-16957) Use weighted midpoints for split values.

Vladimir Feinberg created SPARK-16957: - Summary: Use weighted midpoints for split values. Key: SPARK-16957 URL: https://issues.apache.org/jira/browse/SPARK-16957 Project: Spark Issue

[jira] [Commented] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412451#comment-15412451 ] Sean Owen commented on SPARK-12381: --- Are you also basically subsuming

[jira] [Issue Comment Deleted] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-12381: -- Comment: was deleted (was: I will be out of the office until Monday 15 August. I will not have

[jira] [Updated] (SPARK-11150) Dynamic partition pruning

[ https://issues.apache.org/jira/browse/SPARK-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davies Liu updated SPARK-11150: --- Affects Version/s: 2.0.0 Target Version/s: 2.1.0 Issue Type: New Feature (was: Bug)

[jira] [Assigned] (SPARK-11150) Dynamic partition pruning

[ https://issues.apache.org/jira/browse/SPARK-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davies Liu reassigned SPARK-11150: -- Assignee: Davies Liu > Dynamic partition pruning > - > >

[jira] [Commented] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412439#comment-15412439 ] Matthew Carle commented on SPARK-12381: --- I will be out of the office until Monday 15 August. I

[jira] [Commented] (SPARK-12381) Copy public decision tree helper classes from spark.mllib to spark.ml and make private

[ https://issues.apache.org/jira/browse/SPARK-12381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412438#comment-15412438 ] Vladimir Feinberg commented on SPARK-12381: --- [~sethah] Just so we don't clash, I think these

[jira] [Resolved] (SPARK-16953) Make requestTotalExecutors public to be consistent with requestExecutors/killExecutors

[ https://issues.apache.org/jira/browse/SPARK-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tathagata Das resolved SPARK-16953. --- Resolution: Fixed Fix Version/s: 2.1.0 2.0.1 Issue resolved by

[jira] [Assigned] (SPARK-16956) Make ApplicationState.MAX_NUM_RETRY configurable

[ https://issues.apache.org/jira/browse/SPARK-16956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16956: Assignee: Josh Rosen (was: Apache Spark) > Make ApplicationState.MAX_NUM_RETRY

[jira] [Assigned] (SPARK-16956) Make ApplicationState.MAX_NUM_RETRY configurable

[ https://issues.apache.org/jira/browse/SPARK-16956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16956: Assignee: Apache Spark (was: Josh Rosen) > Make ApplicationState.MAX_NUM_RETRY

[jira] [Created] (SPARK-16956) Make ApplicationState.MAX_NUM_RETRY configurable

Josh Rosen created SPARK-16956: -- Summary: Make ApplicationState.MAX_NUM_RETRY configurable Key: SPARK-16956 URL: https://issues.apache.org/jira/browse/SPARK-16956 Project: Spark Issue Type: New

[jira] [Commented] (SPARK-11638) Run Spark on Mesos with bridge networking

[ https://issues.apache.org/jira/browse/SPARK-11638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412293#comment-15412293 ] Radoslaw Gruchalski commented on SPARK-11638: - [~mandoskippy] Yes, there my lack of knowledge

[jira] [Updated] (SPARK-16552) Store the Inferred Schemas into External Catalog Tables when Creating Tables

[ https://issues.apache.org/jira/browse/SPARK-16552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai updated SPARK-16552: - Labels: release_notes releasenotes (was: ) > Store the Inferred Schemas into External Catalog Tables

[jira] [Assigned] (SPARK-16953) Make requestTotalExecutors public to be consistent with requestExecutors/killExecutors

[ https://issues.apache.org/jira/browse/SPARK-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16953: Assignee: Apache Spark (was: Tathagata Das) > Make requestTotalExecutors public to be

[jira] [Commented] (SPARK-16953) Make requestTotalExecutors public to be consistent with requestExecutors/killExecutors

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

[jira] [Assigned] (SPARK-16953) Make requestTotalExecutors public to be consistent with requestExecutors/killExecutors

[ https://issues.apache.org/jira/browse/SPARK-16953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16953: Assignee: Tathagata Das (was: Apache Spark) > Make requestTotalExecutors public to be

[jira] [Commented] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

[ https://issues.apache.org/jira/browse/SPARK-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412265#comment-15412265 ] Dongjoon Hyun commented on SPARK-16955: --- Sure! Thank you, [~yhuai]. I'll take a look this. > Using

[jira] [Commented] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

[ https://issues.apache.org/jira/browse/SPARK-16955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412263#comment-15412263 ] Yin Huai commented on SPARK-16955: -- [~dongjoon] Will have time to take a look? > Using ordinals in

[jira] [Created] (SPARK-16955) Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals

Yin Huai created SPARK-16955: Summary: Using ordinals in ORDER BY causes an analysis error when the query has a GROUP BY clause using ordinals Key: SPARK-16955 URL: https://issues.apache.org/jira/browse/SPARK-16955

[jira] [Commented] (SPARK-14666) Using DISTINCT on a UDF (like CONCAT) is not supported

[ https://issues.apache.org/jira/browse/SPARK-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412250#comment-15412250 ] Dongjoon Hyun commented on SPARK-14666: --- Great! > Using DISTINCT on a UDF (like CONCAT) is not

[jira] [Resolved] (SPARK-14666) Using DISTINCT on a UDF (like CONCAT) is not supported

[ https://issues.apache.org/jira/browse/SPARK-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Ricard resolved SPARK-14666. Resolution: Fixed Fix Version/s: 2.0.0 > Using DISTINCT on a UDF (like CONCAT) is

[jira] [Commented] (SPARK-14666) Using DISTINCT on a UDF (like CONCAT) is not supported

[ https://issues.apache.org/jira/browse/SPARK-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412243#comment-15412243 ] Dominic Ricard commented on SPARK-14666: It does indeed work in Spark 2.0. Thanks. > Using

[jira] [Updated] (SPARK-16951) Alternative implementation of NOT IN to Anti-join

[ https://issues.apache.org/jira/browse/SPARK-16951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-16951: Fix Version/s: (was: 2.1.0) > Alternative implementation of NOT IN to Anti-join >

[jira] [Updated] (SPARK-16951) Alternative implementation of NOT IN to Anti-join

[ https://issues.apache.org/jira/browse/SPARK-16951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-16951: Target Version/s: (was: 2.1.0) > Alternative implementation of NOT IN to Anti-join >

[jira] [Resolved] (SPARK-16586) spark-class crash with "[: too many arguments" instead of displaying the correct error message

[ https://issues.apache.org/jira/browse/SPARK-16586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-16586. Resolution: Fixed Assignee: Marcelo Vanzin Fix Version/s: 2.1.0

[jira] [Assigned] (SPARK-16930) ApplicationMaster's code that waits for SparkContext is race-prone

[ https://issues.apache.org/jira/browse/SPARK-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16930: Assignee: (was: Apache Spark) > ApplicationMaster's code that waits for SparkContext

[jira] [Assigned] (SPARK-16930) ApplicationMaster's code that waits for SparkContext is race-prone

[ https://issues.apache.org/jira/browse/SPARK-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16930: Assignee: Apache Spark > ApplicationMaster's code that waits for SparkContext is

[jira] [Commented] (SPARK-16930) ApplicationMaster's code that waits for SparkContext is race-prone

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

  1   2   >