[jira] [Created] (SPARK-16946) saveAsTable[append] with different number of columns should throw Exception

Huaxin Gao created SPARK-16946: -- Summary: saveAsTable[append] with different number of columns should throw Exception Key: SPARK-16946 URL: https://issues.apache.org/jira/browse/SPARK-16946 Project:

[jira] [Commented] (SPARK-16606) Misleading warning for SparkContext.getOrCreate "WARN SparkContext: Use an existing SparkContext, some configuration may not take effect."

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

[jira] [Assigned] (SPARK-16606) Misleading warning for SparkContext.getOrCreate "WARN SparkContext: Use an existing SparkContext, some configuration may not take effect."

[ https://issues.apache.org/jira/browse/SPARK-16606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16606: Assignee: Apache Spark > Misleading warning for SparkContext.getOrCreate "WARN

[jira] [Assigned] (SPARK-16606) Misleading warning for SparkContext.getOrCreate "WARN SparkContext: Use an existing SparkContext, some configuration may not take effect."

[ https://issues.apache.org/jira/browse/SPARK-16606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16606: Assignee: (was: Apache Spark) > Misleading warning for SparkContext.getOrCreate "WARN

[jira] [Comment Edited] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411319#comment-15411319 ] Sun Rui edited comment on SPARK-16944 at 8/8/16 5:29 AM: - I don't think it can be

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411320#comment-15411320 ] Sun Rui commented on SPARK-16944: - I don't think it can be improved without dynamic allocation. because

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411319#comment-15411319 ] Sun Rui commented on SPARK-16944: - I don't think it can be improved without dynamic allocation. because

[jira] [Issue Comment Deleted] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sun Rui updated SPARK-16944: Comment: was deleted (was: I don't think it can be improved without dynamic allocation. because without

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411315#comment-15411315 ] Michael Gummelt commented on SPARK-16944: - Yea, we typically call it "delay scheduling". It was

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411313#comment-15411313 ] Sun Rui commented on SPARK-16944: - Not quite sure. I think the Mesos scheduler backend can get the

[jira] [Resolved] (SPARK-16919) Configurable update interval for console progress bar

[ https://issues.apache.org/jira/browse/SPARK-16919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16919. --- Resolution: Fixed Assignee: Tejas Patil Fix Version/s: 2.1.0 Resolved by

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411309#comment-15411309 ] Michael Gummelt commented on SPARK-16944: - Since Mesos is offer based, it's up to the Spark

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411307#comment-15411307 ] Michael Gummelt commented on SPARK-16944: - I think we can improve both with and without dynamic

[jira] [Commented] (SPARK-16945) Fix Java Lint errors

[ https://issues.apache.org/jira/browse/SPARK-16945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411305#comment-15411305 ] Sean Owen commented on SPARK-16945: --- Probably does not need a JIRA. We have to do this periodically and

[jira] [Updated] (SPARK-16945) Fix Java Lint errors

[ https://issues.apache.org/jira/browse/SPARK-16945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-16945: -- Assignee: Weiqing Yang Priority: Trivial (was: Minor) > Fix Java Lint errors >

[jira] [Assigned] (SPARK-16945) Fix Java Lint errors

[ https://issues.apache.org/jira/browse/SPARK-16945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16945: Assignee: (was: Apache Spark) > Fix Java Lint errors > > >

[jira] [Commented] (SPARK-16945) Fix Java Lint errors

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

[jira] [Assigned] (SPARK-16945) Fix Java Lint errors

[ https://issues.apache.org/jira/browse/SPARK-16945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16945: Assignee: Apache Spark > Fix Java Lint errors > > >

[jira] [Comment Edited] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411282#comment-15411282 ] Hyukjin Kwon edited comment on SPARK-16918 at 8/8/16 5:14 AM: -- FYI, it seems

[jira] [Commented] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411300#comment-15411300 ] Hyukjin Kwon commented on SPARK-16918: -- Oh, thanks for pointing this out. I just did this with 101.

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411299#comment-15411299 ] Saisai Shao commented on SPARK-16944: - Does Mesos have the similar concept like Yarn container, also

[jira] [Updated] (SPARK-16945) Fix Java Lint errors

[ https://issues.apache.org/jira/browse/SPARK-16945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiqing Yang updated SPARK-16945: - Component/s: Build > Fix Java Lint errors > > > Key:

[jira] [Created] (SPARK-16945) Fix Java Lint errors

Weiqing Yang created SPARK-16945: Summary: Fix Java Lint errors Key: SPARK-16945 URL: https://issues.apache.org/jira/browse/SPARK-16945 Project: Spark Issue Type: Task Reporter:

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411297#comment-15411297 ] Sun Rui commented on SPARK-16944: - [~jerryshao] [~mgummelt] > [MESOS] Improve data locality when

[jira] [Issue Comment Deleted] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sun Rui updated SPARK-16944: Comment: was deleted (was: [~jerryshao] [~mgummelt]) > [MESOS] Improve data locality when launching new

[jira] [Commented] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

[ https://issues.apache.org/jira/browse/SPARK-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411295#comment-15411295 ] Sun Rui commented on SPARK-16944: - [~jerryshao] [~mgummelt] > [MESOS] Improve data locality when

[jira] [Commented] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411292#comment-15411292 ] Dongjoon Hyun commented on SPARK-16918: --- By the way, you need to test with N=101 . :) > Weird

[jira] [Created] (SPARK-16944) [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled

Sun Rui created SPARK-16944: --- Summary: [MESOS] Improve data locality when launching new executors when dynamic allocation is enabled Key: SPARK-16944 URL: https://issues.apache.org/jira/browse/SPARK-16944

[jira] [Resolved] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16918. --- Resolution: Not A Problem OK, it's probably a duplicate of something else then but I don't know

[jira] [Commented] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411289#comment-15411289 ] Dongjoon Hyun commented on SPARK-16918: --- Oh, fast [~hyukjin.kwon]! :) > Weird error when selecting

[jira] [Commented] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411287#comment-15411287 ] Dongjoon Hyun commented on SPARK-16918: --- Hi, [~phihungle]. I met the same error in bot 1.6.1 and

[jira] [Comment Edited] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411287#comment-15411287 ] Dongjoon Hyun edited comment on SPARK-16918 at 8/8/16 5:03 AM: --- Hi,

[jira] [Commented] (SPARK-16918) Weird error when selecting more than 100 spark udf columns

[ https://issues.apache.org/jira/browse/SPARK-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411282#comment-15411282 ] Hyukjin Kwon commented on SPARK-16918: -- FYI, it seems fine in current master fortunately. {code}

[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=15411277#comment-15411277 ] Michael Gummelt commented on SPARK-11638: - This JIRA is complex and a lot of it is out of date.

[jira] [Assigned] (SPARK-16942) CREATE TABLE LIKE generates External table when source table is an External Hive Serde table

[ https://issues.apache.org/jira/browse/SPARK-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16942: Assignee: (was: Apache Spark) > CREATE TABLE LIKE generates External table when

[jira] [Commented] (SPARK-16942) CREATE TABLE LIKE generates External table when source table is an External Hive Serde table

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

[jira] [Assigned] (SPARK-16942) CREATE TABLE LIKE generates External table when source table is an External Hive Serde table

[ https://issues.apache.org/jira/browse/SPARK-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16942: Assignee: Apache Spark > CREATE TABLE LIKE generates External table when source table is

[jira] [Assigned] (SPARK-16943) CREATE TABLE LIKE generates a non-empty table when source is a data source table

[ https://issues.apache.org/jira/browse/SPARK-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16943: Assignee: Apache Spark > CREATE TABLE LIKE generates a non-empty table when source is a

[jira] [Commented] (SPARK-16943) CREATE TABLE LIKE generates a non-empty table when source is a data source table

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

[jira] [Assigned] (SPARK-16943) CREATE TABLE LIKE generates a non-empty table when source is a data source table

[ https://issues.apache.org/jira/browse/SPARK-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16943: Assignee: (was: Apache Spark) > CREATE TABLE LIKE generates a non-empty table when

[jira] [Updated] (SPARK-16942) CREATE TABLE LIKE generates External table when source table is External

[ https://issues.apache.org/jira/browse/SPARK-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-16942: Summary: CREATE TABLE LIKE generates External table when source table is External (was: CREATE TABLE LIKE

[jira] [Updated] (SPARK-16942) CREATE TABLE LIKE generates External table when source table is an External Hive Serde table

[ https://issues.apache.org/jira/browse/SPARK-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-16942: Summary: CREATE TABLE LIKE generates External table when source table is an External Hive Serde table

[jira] [Created] (SPARK-16943) CREATE TABLE LIKE generates a non-empty table when source is a data source table

Xiao Li created SPARK-16943: --- Summary: CREATE TABLE LIKE generates a non-empty table when source is a data source table Key: SPARK-16943 URL: https://issues.apache.org/jira/browse/SPARK-16943 Project:

[jira] [Created] (SPARK-16942) CREATE TABLE LIKE generates External table when Source table is External

Xiao Li created SPARK-16942: --- Summary: CREATE TABLE LIKE generates External table when Source table is External Key: SPARK-16942 URL: https://issues.apache.org/jira/browse/SPARK-16942 Project: Spark

[jira] [Created] (SPARK-16941) SparkSQLOperationManager shuold use synchronization map to store SessionHandle

carlmartin created SPARK-16941: -- Summary: SparkSQLOperationManager shuold use synchronization map to store SessionHandle Key: SPARK-16941 URL: https://issues.apache.org/jira/browse/SPARK-16941 Project:

[jira] [Commented] (SPARK-16666) Kryo encoder for custom complex classes

[ https://issues.apache.org/jira/browse/SPARK-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411207#comment-15411207 ] Wenchen Fan commented on SPARK-1: - [~samehraban] , in your stack trace, `Queryable.scala`

[jira] [Commented] (SPARK-15899) file scheme should be used correctly

[ https://issues.apache.org/jira/browse/SPARK-15899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411190#comment-15411190 ] xuyifei commented on SPARK-15899: - really appreciate, it works,( sorry reply too late > file scheme

[jira] [Commented] (SPARK-16868) Executor will be both dead and alive when this executor reregister itself to driver.

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

[jira] [Assigned] (SPARK-16868) Executor will be both dead and alive when this executor reregister itself to driver.

[ https://issues.apache.org/jira/browse/SPARK-16868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16868: Assignee: (was: Apache Spark) > Executor will be both dead and alive when this

[jira] [Assigned] (SPARK-16868) Executor will be both dead and alive when this executor reregister itself to driver.

[ https://issues.apache.org/jira/browse/SPARK-16868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16868: Assignee: Apache Spark > Executor will be both dead and alive when this executor

[jira] [Comment Edited] (SPARK-16914) NodeManager crash when spark are registering executor infomartion into leveldb

[ https://issues.apache.org/jira/browse/SPARK-16914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411159#comment-15411159 ] Saisai Shao edited comment on SPARK-16914 at 8/8/16 1:48 AM: - So from your

[jira] [Commented] (SPARK-16914) NodeManager crash when spark are registering executor infomartion into leveldb

[ https://issues.apache.org/jira/browse/SPARK-16914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411159#comment-15411159 ] Saisai Shao commented on SPARK-16914: - So from your description, is this exception mainly due to the

[jira] [Commented] (SPARK-16940) `checkAnswer` should raise `TestFailedException` for wrong results

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

[jira] [Assigned] (SPARK-16940) `checkAnswer` should raise `TestFailedException` for wrong results

[ https://issues.apache.org/jira/browse/SPARK-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16940: Assignee: (was: Apache Spark) > `checkAnswer` should raise `TestFailedException` for

[jira] [Assigned] (SPARK-16940) `checkAnswer` should raise `TestFailedException` for wrong results

[ https://issues.apache.org/jira/browse/SPARK-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16940: Assignee: Apache Spark > `checkAnswer` should raise `TestFailedException` for wrong

[jira] [Created] (SPARK-16940) `checkAnswer` should raise `TestFailedException` for wrong results

Dongjoon Hyun created SPARK-16940: - Summary: `checkAnswer` should raise `TestFailedException` for wrong results Key: SPARK-16940 URL: https://issues.apache.org/jira/browse/SPARK-16940 Project: Spark

[jira] [Commented] (SPARK-16937) Confusing behaviors when View and Temp View sharing the same names

[ https://issues.apache.org/jira/browse/SPARK-16937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411137#comment-15411137 ] Xiao Li commented on SPARK-16937: - Sure, will do it. Thanks! > Confusing behaviors when View and Temp

[jira] [Commented] (SPARK-16937) Confusing behaviors when View and Temp View sharing the same names

[ https://issues.apache.org/jira/browse/SPARK-16937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411134#comment-15411134 ] Wenchen Fan commented on SPARK-16937: - For the problem described in the JIRA, yea, seems our rule is

[jira] [Commented] (SPARK-16508) Fix documentation warnings found by R CMD check

[ https://issues.apache.org/jira/browse/SPARK-16508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411132#comment-15411132 ] Junyang Qian commented on SPARK-16508: -- Sounds good. I'll be working on the undocumented/duplicated

[jira] [Assigned] (SPARK-16938) Cannot resolve column name after a join

[ https://issues.apache.org/jira/browse/SPARK-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16938: Assignee: Apache Spark > Cannot resolve column name after a join >

[jira] [Assigned] (SPARK-16938) Cannot resolve column name after a join

[ https://issues.apache.org/jira/browse/SPARK-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16938: Assignee: (was: Apache Spark) > Cannot resolve column name after a join >

[jira] [Commented] (SPARK-16938) Cannot resolve column name after a join

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

[jira] [Updated] (SPARK-12920) Fix high CPU usage in spark thrift server with concurrent users

[ https://issues.apache.org/jira/browse/SPARK-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Balamohan updated SPARK-12920: - Summary: Fix high CPU usage in spark thrift server with concurrent users (was: Spark

[jira] [Commented] (SPARK-16938) Cannot resolve column name after a join

[ https://issues.apache.org/jira/browse/SPARK-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411106#comment-15411106 ] Dongjoon Hyun commented on SPARK-16938: --- Hi, [~mathieude]. This bug seems to be introduced at

[jira] [Commented] (SPARK-15899) file scheme should be used correctly

[ https://issues.apache.org/jira/browse/SPARK-15899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411052#comment-15411052 ] Bruno C Faria commented on SPARK-15899: --- I have used

[jira] [Resolved] (SPARK-16939) Fix build error by using `Tuple1` explicitly in StringFunctionSuite

[ https://issues.apache.org/jira/browse/SPARK-16939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16939. --- Resolution: Fixed Assignee: Dongjoon Hyun Fix Version/s: 1.6.3 Resolved by

[jira] [Commented] (SPARK-6932) A Prototype of Parameter Server

[ https://issues.apache.org/jira/browse/SPARK-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411023#comment-15411023 ] Debasish Das commented on SPARK-6932: - [~rxin] [~sowen] Do we have any other active parameter server

[jira] [Commented] (SPARK-16937) Confusing behaviors when View and Temp View sharing the same names

[ https://issues.apache.org/jira/browse/SPARK-16937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410991#comment-15410991 ] Xiao Li commented on SPARK-16937: - We are using different name resolution rules, should we make them

[jira] [Commented] (SPARK-16937) Confusing behaviors when View and Temp View sharing the same names

[ https://issues.apache.org/jira/browse/SPARK-16937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410989#comment-15410989 ] Xiao Li commented on SPARK-16937: - Currently, the existing DDL behaviors for views when users do not

[jira] [Assigned] (SPARK-16939) Fix build error by using `Tuple1` explicitly in StringFunctionSuite

[ https://issues.apache.org/jira/browse/SPARK-16939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16939: Assignee: Apache Spark > Fix build error by using `Tuple1` explicitly in

[jira] [Assigned] (SPARK-16939) Fix build error by using `Tuple1` explicitly in StringFunctionSuite

[ https://issues.apache.org/jira/browse/SPARK-16939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16939: Assignee: (was: Apache Spark) > Fix build error by using `Tuple1` explicitly in

[jira] [Created] (SPARK-16939) Fix build error by using `Tuple1` explicitly in StringFunctionSuite

Dongjoon Hyun created SPARK-16939: - Summary: Fix build error by using `Tuple1` explicitly in StringFunctionSuite Key: SPARK-16939 URL: https://issues.apache.org/jira/browse/SPARK-16939 Project: Spark

[jira] [Commented] (SPARK-12436) If all values of a JSON field is null, JSON's inferSchema should return NullType instead of StringType

[ https://issues.apache.org/jira/browse/SPARK-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410946#comment-15410946 ] Hasil Sharma commented on SPARK-12436: -- Is this issue solved ? If not, would like to contribute >

[jira] [Created] (SPARK-16938) Cannot resolve column name after a join

Mathieu D created SPARK-16938: - Summary: Cannot resolve column name after a join Key: SPARK-16938 URL: https://issues.apache.org/jira/browse/SPARK-16938 Project: Spark Issue Type: Bug

[jira] [Commented] (SPARK-16324) regexp_extract should doc that it returns empty string when match fails

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

[jira] [Assigned] (SPARK-16324) regexp_extract should doc that it returns empty string when match fails

[ https://issues.apache.org/jira/browse/SPARK-16324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16324: Assignee: Apache Spark > regexp_extract should doc that it returns empty string when

[jira] [Assigned] (SPARK-16324) regexp_extract should doc that it returns empty string when match fails

[ https://issues.apache.org/jira/browse/SPARK-16324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16324: Assignee: (was: Apache Spark) > regexp_extract should doc that it returns empty

[jira] [Commented] (SPARK-15575) Remove breeze from dependencies?

[ https://issues.apache.org/jira/browse/SPARK-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410923#comment-15410923 ] xubo245 commented on SPARK-15575: - If remove breeze dependency,we need rewrite similar project? I think

[jira] [Assigned] (SPARK-16409) regexp_extract with optional groups causes NPE

[ https://issues.apache.org/jira/browse/SPARK-16409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen reassigned SPARK-16409: - Assignee: Sean Owen > regexp_extract with optional groups causes NPE >

[jira] [Resolved] (SPARK-16409) regexp_extract with optional groups causes NPE

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

[jira] [Updated] (SPARK-16909) Streaming for postgreSQL JDBC driver

[ https://issues.apache.org/jira/browse/SPARK-16909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-16909: -- Assignee: prince john wesley Priority: Minor (was: Major) Issue Type: Improvement (was:

[jira] [Resolved] (SPARK-16909) Streaming for postgreSQL JDBC driver

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

[jira] [Assigned] (SPARK-16832) CrossValidator and TrainValidationSplit are not random without seed

[ https://issues.apache.org/jira/browse/SPARK-16832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16832: Assignee: (was: Apache Spark) > CrossValidator and TrainValidationSplit are not

[jira] [Commented] (SPARK-16832) CrossValidator and TrainValidationSplit are not random without seed

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

[jira] [Assigned] (SPARK-16832) CrossValidator and TrainValidationSplit are not random without seed

[ https://issues.apache.org/jira/browse/SPARK-16832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-16832: Assignee: Apache Spark > CrossValidator and TrainValidationSplit are not random without

[jira] [Commented] (SPARK-10063) Remove DirectParquetOutputCommitter

[ https://issues.apache.org/jira/browse/SPARK-10063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410870#comment-15410870 ] Steve Loughran commented on SPARK-10063: The solution for this is going to be s3guard,

[jira] [Resolved] (SPARK-16769) httpclient classic dependency - potentially a patch required?

[ https://issues.apache.org/jira/browse/SPARK-16769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16769. --- Resolution: Not A Problem I think this doesn't end up being a vulnerability AFAICT and would partly

[jira] [Resolved] (SPARK-16326) Evaluate sparklyr package from RStudio

[ https://issues.apache.org/jira/browse/SPARK-16326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-16326. --- Resolution: Not A Problem > Evaluate sparklyr package from RStudio >

[jira] [Updated] (SPARK-16911) Remove migrating to a Spark 1.x version in programming guide documentation

[ https://issues.apache.org/jira/browse/SPARK-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-16911: -- Assignee: Shivansh > Remove migrating to a Spark 1.x version in programming guide documentation >

[jira] [Resolved] (SPARK-16911) Remove migrating to a Spark 1.x version in programming guide documentation

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

[jira] [Updated] (SPARK-16870) add "spark.sql.broadcastTimeout" into docs/sql-programming-guide.md to help people to how to fix this timeout error when it happenned

[ https://issues.apache.org/jira/browse/SPARK-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-16870: -- Assignee: Liang Ke > add "spark.sql.broadcastTimeout" into docs/sql-programming-guide.md to help >

[jira] [Resolved] (SPARK-16870) add "spark.sql.broadcastTimeout" into docs/sql-programming-guide.md to help people to how to fix this timeout error when it happenned

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

[jira] [Commented] (SPARK-16864) Comprehensive version info

[ https://issues.apache.org/jira/browse/SPARK-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410856#comment-15410856 ] Sean Owen commented on SPARK-16864: --- Yeah you've hit it on the head: git hash is really only relevant

[jira] [Updated] (SPARK-16932) Programming-guide Accumulator section should be more clear w.r.t new API

[ https://issues.apache.org/jira/browse/SPARK-16932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-16932: -- Assignee: Bryan Cutler > Programming-guide Accumulator section should be more clear w.r.t new API >

[jira] [Resolved] (SPARK-16932) Programming-guide Accumulator section should be more clear w.r.t new API

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

[jira] [Commented] (SPARK-16937) Confusing behaviors when View and Temp View sharing the same names

[ https://issues.apache.org/jira/browse/SPARK-16937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410848#comment-15410848 ] Xiao Li commented on SPARK-16937: - [~rxin] [~yhuai] [~cloud_fan] Do you think the above behaviors are

[jira] [Created] (SPARK-16937) Confusing behaviors when View and Temp View sharing the same names

Xiao Li created SPARK-16937: --- Summary: Confusing behaviors when View and Temp View sharing the same names Key: SPARK-16937 URL: https://issues.apache.org/jira/browse/SPARK-16937 Project: Spark

[jira] [Commented] (SPARK-16913) [SQL] Better codegen where querying nested struct

[ https://issues.apache.org/jira/browse/SPARK-16913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410840#comment-15410840 ] Kazuaki Ishizaki commented on SPARK-16913: -- It seems to copy each elements in a struct. Since

[jira] [Commented] (SPARK-8904) When using LDA DAGScheduler throws exception

[ https://issues.apache.org/jira/browse/SPARK-8904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410835#comment-15410835 ] Nabarun commented on SPARK-8904: This seem to be related to something which I am seeing at my end to. I