[jira] [Commented] (SPARK-17681) Empty DataFrame with non-zero rows after using drop

[ https://issues.apache.org/jira/browse/SPARK-17681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528639#comment-15528639 ] Ian Hellstrom commented on SPARK-17681: --- I understand where the logic comes from, e

[jira] [Comment Edited] (SPARK-17681) Empty DataFrame with non-zero rows after using drop

[ https://issues.apache.org/jira/browse/SPARK-17681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528639#comment-15528639 ] Ian Hellstrom edited comment on SPARK-17681 at 9/28/16 6:55 AM: ---

[jira] [Commented] (SPARK-17154) Wrong result can be returned or AnalysisException can be thrown after self-join or similar operations

[ https://issues.apache.org/jira/browse/SPARK-17154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528612#comment-15528612 ] Wenchen Fan commented on SPARK-17154: - I took a look at the new proposal. I think it

[jira] [Commented] (SPARK-16292) Failed to create spark client

[ https://issues.apache.org/jira/browse/SPARK-16292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528561#comment-15528561 ] Arcflash commented on SPARK-16292: -- If you use this command like ./make-distribution.sh

[jira] [Commented] (SPARK-17631) Structured Streaming - Do we need to output results through http API?

[ https://issues.apache.org/jira/browse/SPARK-17631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528403#comment-15528403 ] Frederick Reiss commented on SPARK-17631: - I can think of two use cases where one

[jira] [Assigned] (SPARK-17702) Code generation including too many mutable states exceeds JVM size limit.

[ https://issues.apache.org/jira/browse/SPARK-17702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17702: Assignee: (was: Apache Spark) > Code generation including too many mutable states exce

[jira] [Commented] (SPARK-17702) Code generation including too many mutable states exceeds JVM size limit.

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

[jira] [Assigned] (SPARK-17702) Code generation including too many mutable states exceeds JVM size limit.

[ https://issues.apache.org/jira/browse/SPARK-17702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17702: Assignee: Apache Spark > Code generation including too many mutable states exceeds JVM siz

[jira] [Created] (SPARK-17702) Code generation including too many mutable states exceeds JVM size limit.

Takuya Ueshin created SPARK-17702: - Summary: Code generation including too many mutable states exceeds JVM size limit. Key: SPARK-17702 URL: https://issues.apache.org/jira/browse/SPARK-17702 Project:

[jira] [Commented] (SPARK-17694) convert DataFrame to DataSet should check columns match

[ https://issues.apache.org/jira/browse/SPARK-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528295#comment-15528295 ] Hyukjin Kwon commented on SPARK-17694: -- FWIW, this reminds me of SPARK-15918 > conv

[jira] [Updated] (SPARK-17631) Structured Streaming - Do we need to output results through http API?

[ https://issues.apache.org/jira/browse/SPARK-17631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxinyu updated SPARK-17631: --- Description: Streaming query results can be sinked to http server through http post request was:

[jira] [Created] (SPARK-17701) Refactor DataSourceScanExec so its sameResult call does not compare strings

Eric Liang created SPARK-17701: -- Summary: Refactor DataSourceScanExec so its sameResult call does not compare strings Key: SPARK-17701 URL: https://issues.apache.org/jira/browse/SPARK-17701 Project: Spar

[jira] [Updated] (SPARK-17701) Refactor DataSourceScanExec so its sameResult call does not compare strings

[ https://issues.apache.org/jira/browse/SPARK-17701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Liang updated SPARK-17701: --- Component/s: SQL > Refactor DataSourceScanExec so its sameResult call does not compare strings >

[jira] [Commented] (SPARK-17631) Structured Streaming - Do we need to output results through http API?

[ https://issues.apache.org/jira/browse/SPARK-17631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528228#comment-15528228 ] zhangxinyu commented on SPARK-17631: The pr is still open. I want to discuss it with

[jira] [Created] (SPARK-17700) org.apache.hadoop.hive.ql.metadata.HiveException: Failed to create spark client

Alpha created SPARK-17700: - Summary: org.apache.hadoop.hive.ql.metadata.HiveException: Failed to create spark client Key: SPARK-17700 URL: https://issues.apache.org/jira/browse/SPARK-17700 Project: Spark

[jira] [Assigned] (SPARK-17699) from_json function for parsing json Strings into Structs

[ https://issues.apache.org/jira/browse/SPARK-17699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17699: Assignee: Apache Spark (was: Michael Armbrust) > from_json function for parsing json Stri

[jira] [Assigned] (SPARK-17699) from_json function for parsing json Strings into Structs

[ https://issues.apache.org/jira/browse/SPARK-17699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17699: Assignee: Michael Armbrust (was: Apache Spark) > from_json function for parsing json Stri

[jira] [Commented] (SPARK-17699) from_json function for parsing json Strings into Structs

[ https://issues.apache.org/jira/browse/SPARK-17699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528201#comment-15528201 ] Apache Spark commented on SPARK-17699: -- User 'marmbrus' has created a pull request f

[jira] [Created] (SPARK-17699) from_json function for parsing json Strings into Structs

Michael Armbrust created SPARK-17699: Summary: from_json function for parsing json Strings into Structs Key: SPARK-17699 URL: https://issues.apache.org/jira/browse/SPARK-17699 Project: Spark

[jira] [Commented] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

[ https://issues.apache.org/jira/browse/SPARK-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528145#comment-15528145 ] Eric Liang commented on SPARK-17673: Russell, could you try applying this patch (wip)

[jira] [Assigned] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

[ https://issues.apache.org/jira/browse/SPARK-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17673: Assignee: Apache Spark > Reused Exchange Aggregations Produce Incorrect Results >

[jira] [Commented] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

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

[jira] [Assigned] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

[ https://issues.apache.org/jira/browse/SPARK-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17673: Assignee: (was: Apache Spark) > Reused Exchange Aggregations Produce Incorrect Results

[jira] [Assigned] (SPARK-17698) Join predicates should not contain filter clauses

[ https://issues.apache.org/jira/browse/SPARK-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17698: Assignee: Apache Spark > Join predicates should not contain filter clauses > -

[jira] [Commented] (SPARK-17698) Join predicates should not contain filter clauses

[ https://issues.apache.org/jira/browse/SPARK-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528057#comment-15528057 ] Apache Spark commented on SPARK-17698: -- User 'tejasapatil' has created a pull reques

[jira] [Assigned] (SPARK-17698) Join predicates should not contain filter clauses

[ https://issues.apache.org/jira/browse/SPARK-17698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17698: Assignee: (was: Apache Spark) > Join predicates should not contain filter clauses > --

[jira] [Commented] (SPARK-17549) InMemoryRelation doesn't scale to large tables

[ https://issues.apache.org/jira/browse/SPARK-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528040#comment-15528040 ] Dongjoon Hyun commented on SPARK-17549: --- Thank you, [~vanzin]! > InMemoryRelation

[jira] [Commented] (SPARK-17666) take() or isEmpty() on dataset leaks s3a connections

[ https://issues.apache.org/jira/browse/SPARK-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528038#comment-15528038 ] Apache Spark commented on SPARK-17666: -- User 'JoshRosen' has created a pull request

[jira] [Commented] (SPARK-17549) InMemoryRelation doesn't scale to large tables

[ https://issues.apache.org/jira/browse/SPARK-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528035#comment-15528035 ] Marcelo Vanzin commented on SPARK-17549: Done. Forgot to update the bug after the

[jira] [Updated] (SPARK-17549) InMemoryRelation doesn't scale to large tables

[ https://issues.apache.org/jira/browse/SPARK-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin updated SPARK-17549: --- Fix Version/s: (was: 2.0.1) > InMemoryRelation doesn't scale to large tables > --

[jira] [Updated] (SPARK-17549) InMemoryRelation doesn't scale to large tables

[ https://issues.apache.org/jira/browse/SPARK-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin updated SPARK-17549: --- Fix Version/s: (was: 2.1.0) > InMemoryRelation doesn't scale to large tables > --

[jira] [Commented] (SPARK-17549) InMemoryRelation doesn't scale to large tables

[ https://issues.apache.org/jira/browse/SPARK-17549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528029#comment-15528029 ] Dongjoon Hyun commented on SPARK-17549: --- Hi, All. Could we add this into RC4 or rem

[jira] [Created] (SPARK-17698) Join predicates should not contain filter clauses

Tejas Patil created SPARK-17698: --- Summary: Join predicates should not contain filter clauses Key: SPARK-17698 URL: https://issues.apache.org/jira/browse/SPARK-17698 Project: Spark Issue Type: B

[jira] [Resolved] (SPARK-17666) take() or isEmpty() on dataset leaks s3a connections

[ https://issues.apache.org/jira/browse/SPARK-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin resolved SPARK-17666. - Resolution: Fixed Fix Version/s: 2.1.0 > take() or isEmpty() on dataset leaks s3a connecti

[jira] [Commented] (SPARK-17666) take() or isEmpty() on dataset leaks s3a connections

[ https://issues.apache.org/jira/browse/SPARK-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527994#comment-15527994 ] Reynold Xin commented on SPARK-17666: - This still needs to be backported to branch-2.

[jira] [Created] (SPARK-17697) BinaryLogisticRegressionSummary should handle non-Double numeric types

Joseph K. Bradley created SPARK-17697: - Summary: BinaryLogisticRegressionSummary should handle non-Double numeric types Key: SPARK-17697 URL: https://issues.apache.org/jira/browse/SPARK-17697 Proj

[jira] [Commented] (SPARK-17695) Deserialization error when using DataFrameReader.json on JSON line that contains an empty JSON object

[ https://issues.apache.org/jira/browse/SPARK-17695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527900#comment-15527900 ] Hyukjin Kwon commented on SPARK-17695: -- Related with SPARK-8093. It seems empty stru

[jira] [Comment Edited] (SPARK-17694) convert DataFrame to DataSet should check columns match

[ https://issues.apache.org/jira/browse/SPARK-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527887#comment-15527887 ] Chenliang Xu edited comment on SPARK-17694 at 9/28/16 12:20 AM: ---

[jira] [Commented] (SPARK-17694) convert DataFrame to DataSet should check columns match

[ https://issues.apache.org/jira/browse/SPARK-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527887#comment-15527887 ] Chenliang Xu commented on SPARK-17694: -- It returns a DataSet, for example {noformat}

[jira] [Resolved] (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 ] Josh Rosen resolved SPARK-17056. Resolution: Fixed Fix Version/s: 2.1.0 2.0.2 Issue resolved by pull reque

[jira] [Commented] (SPARK-14301) Java examples code merge and clean up

[ https://issues.apache.org/jira/browse/SPARK-14301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527702#comment-15527702 ] Sean Owen commented on SPARK-14301: --- It's an example; this is OK. > Java examples code

[jira] [Assigned] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

[ https://issues.apache.org/jira/browse/SPARK-17696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17696: Assignee: Apache Spark > Race in CoarseGrainedExecutorBackend shutdown can lead to wrong e

[jira] [Assigned] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

[ https://issues.apache.org/jira/browse/SPARK-17696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17696: Assignee: (was: Apache Spark) > Race in CoarseGrainedExecutorBackend shutdown can lead

[jira] [Commented] (SPARK-12330) Mesos coarse executor does not cleanup blockmgr properly on termination if data is stored on disk

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

[jira] [Commented] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

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

[jira] [Updated] (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 ] Josh Rosen updated SPARK-17056: --- Assignee: Liang-Chi Hsieh > Fix a wrong assert in MemoryStore > - > >

[jira] [Updated] (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 ] Josh Rosen updated SPARK-17056: --- Component/s: (was: Spark Core) Block Manager > Fix a wrong assert in MemoryStore

[jira] [Resolved] (SPARK-17631) Structured Streaming - Do we need to output results through http API?

[ https://issues.apache.org/jira/browse/SPARK-17631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-17631. --- Resolution: Invalid Not sure what's going on with this, because it sounds like a question for user@,

[jira] [Resolved] (SPARK-17687) Structured Streaming - Does anyone need kafka sink

[ https://issues.apache.org/jira/browse/SPARK-17687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-17687. --- Resolution: Invalid This sounds like a question for user@ > Structured Streaming - Does anyone need

[jira] [Commented] (SPARK-17694) convert DataFrame to DataSet should check columns match

[ https://issues.apache.org/jira/browse/SPARK-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527653#comment-15527653 ] Sean Owen commented on SPARK-17694: --- Here what do you mean that it succeeds? it's a laz

[jira] [Commented] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

[ https://issues.apache.org/jira/browse/SPARK-17696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527600#comment-15527600 ] Marcelo Vanzin commented on SPARK-17696: This is actually fixed in 2.0 by SPARK-1

[jira] [Updated] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

[ https://issues.apache.org/jira/browse/SPARK-17696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin updated SPARK-17696: --- Affects Version/s: (was: 2.0.0) > Race in CoarseGrainedExecutorBackend shutdown can lead

[jira] [Updated] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

[ https://issues.apache.org/jira/browse/SPARK-17696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin updated SPARK-17696: --- Description: There's a race in the shutdown path of CoarseGrainedExecutorBackend that may le

[jira] [Created] (SPARK-17696) Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status

Marcelo Vanzin created SPARK-17696: -- Summary: Race in CoarseGrainedExecutorBackend shutdown can lead to wrong exit status Key: SPARK-17696 URL: https://issues.apache.org/jira/browse/SPARK-17696 Proje

[jira] [Created] (SPARK-17695) Deserialization error when using DataFrameReader.json on JSON line that contains an empty JSON object

Jonathan Simozar created SPARK-17695: Summary: Deserialization error when using DataFrameReader.json on JSON line that contains an empty JSON object Key: SPARK-17695 URL: https://issues.apache.org/jira/browse/

[jira] [Commented] (SPARK-14301) Java examples code merge and clean up

[ https://issues.apache.org/jira/browse/SPARK-14301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527557#comment-15527557 ] Suman Somasundar commented on SPARK-14301: -- This merge removed the generic JavaK

[jira] [Created] (SPARK-17694) convert DataFrame to DataSet should check columns match

Chenliang Xu created SPARK-17694: Summary: convert DataFrame to DataSet should check columns match Key: SPARK-17694 URL: https://issues.apache.org/jira/browse/SPARK-17694 Project: Spark Issue

[jira] [Updated] (SPARK-17618) Dataframe except returns incorrect results when combined with coalesce

[ https://issues.apache.org/jira/browse/SPARK-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Rosen updated SPARK-17618: --- Fix Version/s: 2.1.0 2.0.2 > Dataframe except returns incorrect results when combi

[jira] [Commented] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

[ https://issues.apache.org/jira/browse/SPARK-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527327#comment-15527327 ] Reynold Xin commented on SPARK-17673: - I'm upgrading this to a blocker level issue.

[jira] [Commented] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

[ https://issues.apache.org/jira/browse/SPARK-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527339#comment-15527339 ] Eric Liang commented on SPARK-17673: I'm looking at this now. > Reused Exchange Aggr

[jira] [Updated] (SPARK-17673) Reused Exchange Aggregations Produce Incorrect Results

[ https://issues.apache.org/jira/browse/SPARK-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin updated SPARK-17673: Priority: Blocker (was: Critical) > Reused Exchange Aggregations Produce Incorrect Results > -

[jira] [Updated] (SPARK-17663) SchedulableBuilder should handle invalid data access via scheduler.allocation.file

[ https://issues.apache.org/jira/browse/SPARK-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eren Avsarogullari updated SPARK-17663: --- Affects Version/s: (was: 2.0.1) 2.1.0 > SchedulableBuilder

[jira] [Resolved] (SPARK-17677) Break WindowExec.scala into multiple files

[ https://issues.apache.org/jira/browse/SPARK-17677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herman van Hovell resolved SPARK-17677. --- Resolution: Fixed Fix Version/s: 2.1.0 Resolved per Reynold's PR. > Break Win

[jira] [Assigned] (SPARK-17598) User-friendly name for Spark Thrift Server in web UI

[ https://issues.apache.org/jira/browse/SPARK-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17598: Assignee: (was: Apache Spark) > User-friendly name for Spark Thrift Server in web UI >

[jira] [Commented] (SPARK-17598) User-friendly name for Spark Thrift Server in web UI

[ https://issues.apache.org/jira/browse/SPARK-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527167#comment-15527167 ] Apache Spark commented on SPARK-17598: -- User 'ajbozarth' has created a pull request

[jira] [Assigned] (SPARK-17598) User-friendly name for Spark Thrift Server in web UI

[ https://issues.apache.org/jira/browse/SPARK-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17598: Assignee: Apache Spark > User-friendly name for Spark Thrift Server in web UI > --

[jira] [Commented] (SPARK-17667) Make locking fine grained in YarnAllocator#enqueueGetLossReasonRequest

[ https://issues.apache.org/jira/browse/SPARK-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527128#comment-15527128 ] Apache Spark commented on SPARK-17667: -- User 'ashwinshankar77' has created a pull re

[jira] [Updated] (SPARK-17154) Wrong result can be returned or AnalysisException can be thrown after self-join or similar operations

[ https://issues.apache.org/jira/browse/SPARK-17154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nattavut Sutyanyong updated SPARK-17154: Attachment: Name-conflicts-2.pdf @nsyca's alternative proposal to the solution > W

[jira] [Assigned] (SPARK-17667) Make locking fine grained in YarnAllocator#enqueueGetLossReasonRequest

[ https://issues.apache.org/jira/browse/SPARK-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17667: Assignee: Apache Spark > Make locking fine grained in YarnAllocator#enqueueGetLossReasonRe

[jira] [Assigned] (SPARK-17667) Make locking fine grained in YarnAllocator#enqueueGetLossReasonRequest

[ https://issues.apache.org/jira/browse/SPARK-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17667: Assignee: (was: Apache Spark) > Make locking fine grained in YarnAllocator#enqueueGetL

[jira] [Commented] (SPARK-17598) User-friendly name for Spark Thrift Server in web UI

[ https://issues.apache.org/jira/browse/SPARK-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527110#comment-15527110 ] Alex Bozarth commented on SPARK-17598: -- I have a quick easy fix for this, but you ca

[jira] [Assigned] (SPARK-17693) Fixed Insert Failure To Data Source Tables when the Schema has the Comment Field

[ https://issues.apache.org/jira/browse/SPARK-17693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17693: Assignee: Apache Spark > Fixed Insert Failure To Data Source Tables when the Schema has th

[jira] [Assigned] (SPARK-17693) Fixed Insert Failure To Data Source Tables when the Schema has the Comment Field

[ https://issues.apache.org/jira/browse/SPARK-17693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17693: Assignee: (was: Apache Spark) > Fixed Insert Failure To Data Source Tables when the Sc

[jira] [Commented] (SPARK-17693) Fixed Insert Failure To Data Source Tables when the Schema has the Comment Field

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

[jira] [Updated] (SPARK-17693) Fixed Insert Failure To Data Source Tables when the Schema has the Comment Field

[ https://issues.apache.org/jira/browse/SPARK-17693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17693: Summary: Fixed Insert Failure To Data Source Tables when the Schema has the Comment Field (was: Fixed Inse

[jira] [Commented] (SPARK-17618) Dataframe except returns incorrect results when combined with coalesce

[ https://issues.apache.org/jira/browse/SPARK-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527038#comment-15527038 ] Apache Spark commented on SPARK-17618: -- User 'JoshRosen' has created a pull request

[jira] [Updated] (SPARK-17693) Fixed Insert Failure when Table Schema has the Comment Field

[ https://issues.apache.org/jira/browse/SPARK-17693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17693: Description: {noformat} CREATE TABLE tab1(col1 int COMMENT 'a', col2 int) USING parquet INSERT INTO TABLE t

[jira] [Created] (SPARK-17693) Fixed Insert Failure when Table Schema has the Comment Field

Xiao Li created SPARK-17693: --- Summary: Fixed Insert Failure when Table Schema has the Comment Field Key: SPARK-17693 URL: https://issues.apache.org/jira/browse/SPARK-17693 Project: Spark Issue Typ

[jira] [Commented] (SPARK-17477) SparkSQL cannot handle schema evolution from Int -> Long when parquet files have Int as its type while hive metastore has Long as its type

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

[jira] [Resolved] (SPARK-17618) Dataframe except returns incorrect results when combined with coalesce

[ https://issues.apache.org/jira/browse/SPARK-17618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herman van Hovell resolved SPARK-17618. --- Resolution: Fixed Fix Version/s: 1.6.3 Resolved per Josh's PR. Follow-up for

[jira] [Resolved] (SPARK-17660) DESC FORMATTED for VIEW Lacks View Definition

[ https://issues.apache.org/jira/browse/SPARK-17660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herman van Hovell resolved SPARK-17660. --- Resolution: Fixed Assignee: Xiao Li Fix Version/s: 2.1.0 > DESC FORMA

[jira] [Commented] (SPARK-17681) Empty DataFrame with non-zero rows after using drop

[ https://issues.apache.org/jira/browse/SPARK-17681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526929#comment-15526929 ] Josh Rosen commented on SPARK-17681: I don't think that the current behavior is wrong

[jira] [Updated] (SPARK-17161) Add PySpark-ML JavaWrapper convenience function to create py4j JavaArrays

[ https://issues.apache.org/jira/browse/SPARK-17161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Cutler updated SPARK-17161: - Description: Often in Spark ML, there are classes that use a Scala Array in a constructor. In o

[jira] [Resolved] (SPARK-17682) nit: Mark children as final for Unary, Binary, Leaf expression and plan nodes

[ https://issues.apache.org/jira/browse/SPARK-17682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herman van Hovell resolved SPARK-17682. --- Resolution: Fixed Fix Version/s: 2.1.0 Resolved per Reynold's PR. > nit: Mark

[jira] [Closed] (SPARK-15717) Cannot perform RDD operations on a checkpointed VertexRDD.

[ https://issues.apache.org/jira/browse/SPARK-15717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph K. Bradley closed SPARK-15717. - Resolution: Duplicate > Cannot perform RDD operations on a checkpointed VertexRDD. >

[jira] [Commented] (SPARK-15717) Cannot perform RDD operations on a checkpointed VertexRDD.

[ https://issues.apache.org/jira/browse/SPARK-15717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526798#comment-15526798 ] Joseph K. Bradley commented on SPARK-15717: --- To confirm, this is a duplicate of

[jira] [Resolved] (SPARK-16516) Support for pushing down filters for decimal and timestamp types in ORC

[ https://issues.apache.org/jira/browse/SPARK-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian resolved SPARK-16516. Resolution: Fixed Issue resolved by pull request 14172 [https://github.com/apache/spark/pull/14172]

[jira] [Updated] (SPARK-16777) Parquet schema converter depends on deprecated APIs

[ https://issues.apache.org/jira/browse/SPARK-16777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian updated SPARK-16777: --- Fix Version/s: (was: 2.2.0) 2.1.0 > Parquet schema converter depends on deprec

[jira] [Updated] (SPARK-16516) Support for pushing down filters for decimal and timestamp types in ORC

[ https://issues.apache.org/jira/browse/SPARK-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian updated SPARK-16516: --- Fix Version/s: 2.1.0 > Support for pushing down filters for decimal and timestamp types in ORC >

[jira] [Updated] (SPARK-16516) Support for pushing down filters for decimal and timestamp types in ORC

[ https://issues.apache.org/jira/browse/SPARK-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian updated SPARK-16516: --- Assignee: Hyukjin Kwon > Support for pushing down filters for decimal and timestamp types in ORC > --

[jira] [Updated] (SPARK-16777) Parquet schema converter depends on deprecated APIs

[ https://issues.apache.org/jira/browse/SPARK-16777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian updated SPARK-16777: --- Fix Version/s: 2.1.0 2.0.2 > Parquet schema converter depends on deprecated APIs >

[jira] [Resolved] (SPARK-16777) Parquet schema converter depends on deprecated APIs

[ https://issues.apache.org/jira/browse/SPARK-16777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian resolved SPARK-16777. Resolution: Fixed Fix Version/s: (was: 2.0.2) (was: 2.1.0)

[jira] [Updated] (SPARK-16777) Parquet schema converter depends on deprecated APIs

[ https://issues.apache.org/jira/browse/SPARK-16777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian updated SPARK-16777: --- Assignee: Hyukjin Kwon > Parquet schema converter depends on deprecated APIs > --

[jira] [Updated] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

[ https://issues.apache.org/jira/browse/SPARK-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang updated SPARK-17692: Labels: 2.1.0 (was: ) > Document ML/MLlib behavior changes in Spark 2.1 >

[jira] [Commented] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

[ https://issues.apache.org/jira/browse/SPARK-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15526510#comment-15526510 ] Yanbo Liang commented on SPARK-17692: - cc [~mengxr] [~josephkb] [~dbtsai] [~mlnick] [

[jira] [Updated] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

[ https://issues.apache.org/jira/browse/SPARK-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang updated SPARK-17692: Description: This JIRA records behavior changes of ML/MLlib between 2.0 and 2.1, so we can note th

[jira] [Updated] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

[ https://issues.apache.org/jira/browse/SPARK-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang updated SPARK-17692: Description: This JIRA records behavior changes of ML/MLlib between 2.0 and 2.1, so we can note th

[jira] [Updated] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

[ https://issues.apache.org/jira/browse/SPARK-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang updated SPARK-17692: Description: This JIRA records behavior changes of ML/MLlib between 2.0 and 2.1, so we can note th

[jira] [Created] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

Yanbo Liang created SPARK-17692: --- Summary: Document ML/MLlib behavior changes in Spark 2.1 Key: SPARK-17692 URL: https://issues.apache.org/jira/browse/SPARK-17692 Project: Spark Issue Type: Doc

[jira] [Updated] (SPARK-17692) Document ML/MLlib behavior changes in Spark 2.1

[ https://issues.apache.org/jira/browse/SPARK-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yanbo Liang updated SPARK-17692: Description: This JIRA keeps a list of MLlib behavior changes in Spark 2.1. So we can remember to a

  1   2   >