[jira] [Commented] (SPARK-22074) Task killed by other attempt task should not be resubmitted

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

[jira] [Assigned] (SPARK-22074) Task killed by other attempt task should not be resubmitted

[ https://issues.apache.org/jira/browse/SPARK-22074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22074: Assignee: (was: Apache Spark) > Task killed by other attempt task should not be

[jira] [Assigned] (SPARK-22074) Task killed by other attempt task should not be resubmitted

[ https://issues.apache.org/jira/browse/SPARK-22074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22074: Assignee: Apache Spark > Task killed by other attempt task should not be resubmitted >

[jira] [Assigned] (SPARK-18838) High latency of event processing for large jobs

[ https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-18838: --- Assignee: Marcelo Vanzin > High latency of event processing for large jobs >

[jira] [Resolved] (SPARK-18838) High latency of event processing for large jobs

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

[jira] [Updated] (SPARK-22074) Task killed by other attempt task should not be resubmitted

[ https://issues.apache.org/jira/browse/SPARK-22074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Yuanjian updated SPARK-22074: Description: When a task killed by other task attempt, the task still resubmitted while its

[jira] [Created] (SPARK-22074) Task killed by other attempt task should not be resubmitted

Li Yuanjian created SPARK-22074: --- Summary: Task killed by other attempt task should not be resubmitted Key: SPARK-22074 URL: https://issues.apache.org/jira/browse/SPARK-22074 Project: Spark

[jira] [Created] (SPARK-22073) Add workaround for HIVE-15653 to avoid stats being accidentally wiped

Alexander Behm created SPARK-22073: -- Summary: Add workaround for HIVE-15653 to avoid stats being accidentally wiped Key: SPARK-22073 URL: https://issues.apache.org/jira/browse/SPARK-22073 Project:

[jira] [Created] (SPARK-22072) Automatically rewrite the version string for publish-release

holdenk created SPARK-22072: --- Summary: Automatically rewrite the version string for publish-release Key: SPARK-22072 URL: https://issues.apache.org/jira/browse/SPARK-22072 Project: Spark Issue

[jira] [Created] (SPARK-22071) Improve release build scripts to check correct JAVA version is being used for build

holdenk created SPARK-22071: --- Summary: Improve release build scripts to check correct JAVA version is being used for build Key: SPARK-22071 URL: https://issues.apache.org/jira/browse/SPARK-22071 Project:

[jira] [Commented] (SPARK-21338) AggregatedDialect doesn't override isCascadingTruncateTable() method

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

[jira] [Commented] (SPARK-20466) HadoopRDD#addLocalConfiguration throws NPE

[ https://issues.apache.org/jira/browse/SPARK-20466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172747#comment-16172747 ] Sahil Takiar commented on SPARK-20466: -- I can't remember exactly which query, I was running a chain

[jira] [Created] (SPARK-22070) Spark SQL filter comparisons failing with timestamps and ISO-8601 strings

Vishal Doshi created SPARK-22070: Summary: Spark SQL filter comparisons failing with timestamps and ISO-8601 strings Key: SPARK-22070 URL: https://issues.apache.org/jira/browse/SPARK-22070 Project:

[jira] [Resolved] (SPARK-22069) Web access java.lang.OutOfMemoryError: Java heap space

[ https://issues.apache.org/jira/browse/SPARK-22069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyukjin Kwon resolved SPARK-22069. -- Resolution: Cannot Reproduce I think no one is able to reproduce this or makes sure that the

[jira] [Commented] (SPARK-20973) insert table fail caused by unable to fetch data definition file from remote hdfs

[ https://issues.apache.org/jira/browse/SPARK-20973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172627#comment-16172627 ] Lantao Jin commented on SPARK-20973: Please file a PR, refer to [How to contribute to

[jira] [Created] (SPARK-22069) Web access java.lang.OutOfMemoryError: Java heap space

hoangle created SPARK-22069: --- Summary: Web access java.lang.OutOfMemoryError: Java heap space Key: SPARK-22069 URL: https://issues.apache.org/jira/browse/SPARK-22069 Project: Spark Issue Type: Bug

[jira] [Resolved] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

[ https://issues.apache.org/jira/browse/SPARK-22067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuya Ueshin resolved SPARK-22067. --- Resolution: Fixed Fix Version/s: 2.3.0 Issue resolved by pull request 19284

[jira] [Assigned] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

[ https://issues.apache.org/jira/browse/SPARK-22067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Takuya Ueshin reassigned SPARK-22067: - Assignee: Bryan Cutler > ArrowWriter StringWriter not using position of ByteBuffer

[jira] [Commented] (SPARK-22068) Reduce the duplicate code between putIteratorAsValues and putIteratorAsBytes

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

[jira] [Assigned] (SPARK-22068) Reduce the duplicate code between putIteratorAsValues and putIteratorAsBytes

[ https://issues.apache.org/jira/browse/SPARK-22068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22068: Assignee: Apache Spark > Reduce the duplicate code between putIteratorAsValues and

[jira] [Assigned] (SPARK-22068) Reduce the duplicate code between putIteratorAsValues and putIteratorAsBytes

[ https://issues.apache.org/jira/browse/SPARK-22068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22068: Assignee: (was: Apache Spark) > Reduce the duplicate code between putIteratorAsValues

[jira] [Created] (SPARK-22068) Reduce the duplicate code between putIteratorAsValues and putIteratorAsBytes

Xianyang Liu created SPARK-22068: Summary: Reduce the duplicate code between putIteratorAsValues and putIteratorAsBytes Key: SPARK-22068 URL: https://issues.apache.org/jira/browse/SPARK-22068

[jira] [Resolved] (SPARK-22041) Docker test case failure: `SPARK-16625: General data types to be mapped to Oracle`

[ https://issues.apache.org/jira/browse/SPARK-22041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-22041. - Resolution: Duplicate Fix Version/s: 2.1.2 > Docker test case failure: `SPARK-16625: General data

[jira] [Updated] (SPARK-19318) Docker test case failure: `SPARK-16625: General data types to be mapped to Oracle`

[ https://issues.apache.org/jira/browse/SPARK-19318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-19318: Fix Version/s: 2.1.2 > Docker test case failure: `SPARK-16625: General data types to be mapped to >

[jira] [Updated] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

[ https://issues.apache.org/jira/browse/SPARK-22067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Cutler updated SPARK-22067: - Description: When ArrowWriter is copying a StringType column to ArrowData, then StringWriter

[jira] [Assigned] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

[ https://issues.apache.org/jira/browse/SPARK-22067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22067: Assignee: Apache Spark > ArrowWriter StringWriter not using position of ByteBuffer

[jira] [Assigned] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

[ https://issues.apache.org/jira/browse/SPARK-22067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22067: Assignee: (was: Apache Spark) > ArrowWriter StringWriter not using position of

[jira] [Commented] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

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

[jira] [Commented] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

[ https://issues.apache.org/jira/browse/SPARK-22067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172399#comment-16172399 ] Bryan Cutler commented on SPARK-22067: -- I'll submit a PR for this > ArrowWriter StringWriter not

[jira] [Created] (SPARK-22067) ArrowWriter StringWriter not using position of ByteBuffer holding data

Bryan Cutler created SPARK-22067: Summary: ArrowWriter StringWriter not using position of ByteBuffer holding data Key: SPARK-22067 URL: https://issues.apache.org/jira/browse/SPARK-22067 Project:

[jira] [Commented] (SPARK-14228) Lost executor of RPC disassociated, and occurs exception: Could not find CoarseGrainedScheduler or it has been stopped

[ https://issues.apache.org/jira/browse/SPARK-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172362#comment-16172362 ] anand commented on SPARK-14228: --- I had similar issue running while spark in multithread spark context code.

[jira] [Assigned] (SPARK-21969) CommandUtils.updateTableStats should call refreshTable

[ https://issues.apache.org/jira/browse/SPARK-21969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li reassigned SPARK-21969: --- Assignee: Anton Okolnychyi > CommandUtils.updateTableStats should call refreshTable >

[jira] [Resolved] (SPARK-21969) CommandUtils.updateTableStats should call refreshTable

[ https://issues.apache.org/jira/browse/SPARK-21969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-21969. - Resolution: Fixed Fix Version/s: 2.3.0 > CommandUtils.updateTableStats should call refreshTable >

[jira] [Assigned] (SPARK-22066) Update checkstyle to 8.2, enable it, fix violations

[ https://issues.apache.org/jira/browse/SPARK-22066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22066: Assignee: Apache Spark (was: Sean Owen) > Update checkstyle to 8.2, enable it, fix

[jira] [Commented] (SPARK-22066) Update checkstyle to 8.2, enable it, fix violations

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

[jira] [Assigned] (SPARK-22066) Update checkstyle to 8.2, enable it, fix violations

[ https://issues.apache.org/jira/browse/SPARK-22066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22066: Assignee: Sean Owen (was: Apache Spark) > Update checkstyle to 8.2, enable it, fix

[jira] [Created] (SPARK-22066) Update checkstyle to 8.2, enable it, fix violations

Sean Owen created SPARK-22066: - Summary: Update checkstyle to 8.2, enable it, fix violations Key: SPARK-22066 URL: https://issues.apache.org/jira/browse/SPARK-22066 Project: Spark Issue Type:

[jira] [Commented] (SPARK-22065) Add DDL support to modify constraint state for a given constraint

[ https://issues.apache.org/jira/browse/SPARK-22065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172233#comment-16172233 ] Sunitha Kambhampati commented on SPARK-22065: - I'm working on the implementation for this

[jira] [Created] (SPARK-22065) Add DDL support to modify constraint state for a given constraint

Sunitha Kambhampati created SPARK-22065: --- Summary: Add DDL support to modify constraint state for a given constraint Key: SPARK-22065 URL: https://issues.apache.org/jira/browse/SPARK-22065

[jira] [Commented] (SPARK-22064) Add support for VALIDATE option to ALTER TABLE ADD CONSTRAINT command

[ https://issues.apache.org/jira/browse/SPARK-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1617#comment-1617 ] Sunitha Kambhampati commented on SPARK-22064: - I'm working on this issue. Please note, this

[jira] [Updated] (SPARK-22064) Add support for VALIDATE option to ALTER TABLE ADD CONSTRAINT command

[ https://issues.apache.org/jira/browse/SPARK-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunitha Kambhampati updated SPARK-22064: Description: As part of the Informational Referential Integrity constraints

[jira] [Created] (SPARK-22064) Add support for VALIDATE option to ALTER TABLE ADD CONSTRAINT command

Sunitha Kambhampati created SPARK-22064: --- Summary: Add support for VALIDATE option to ALTER TABLE ADD CONSTRAINT command Key: SPARK-22064 URL: https://issues.apache.org/jira/browse/SPARK-22064

[jira] [Commented] (SPARK-21694) Support Mesos CNI network labels

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

[jira] [Commented] (SPARK-21998) SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

[ https://issues.apache.org/jira/browse/SPARK-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172169#comment-16172169 ] Maryann Xue commented on SPARK-21998: - Thanks again for your comment, [~maropu]! I changed the title

[jira] [Commented] (SPARK-21998) SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

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

[jira] [Assigned] (SPARK-21998) SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

[ https://issues.apache.org/jira/browse/SPARK-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-21998: Assignee: Apache Spark > SortMergeJoinExec did not calculate its outputOrdering correctly

[jira] [Assigned] (SPARK-21998) SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

[ https://issues.apache.org/jira/browse/SPARK-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-21998: Assignee: (was: Apache Spark) > SortMergeJoinExec did not calculate its

[jira] [Commented] (SPARK-21961) Filter out BlockStatuses Accumulators during replaying history logs in Spark History Server

[ https://issues.apache.org/jira/browse/SPARK-21961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172162#comment-16172162 ] Ye Zhou commented on SPARK-21961: - [~zsxwing] Can you help to take a look? Thanks. > Filter out

[jira] [Updated] (SPARK-21998) SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

[ https://issues.apache.org/jira/browse/SPARK-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated SPARK-21998: Description: Right now the calculation of SortMergeJoinExec's outputOrdering relies on the fact

[jira] [Comment Edited] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172123#comment-16172123 ] John Brock edited comment on SPARK-21928 at 9/19/17 6:26 PM: - [~irashid],

[jira] [Commented] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172123#comment-16172123 ] John Brock commented on SPARK-21928: [~irashid], thanks for taking a look. I see the same thing as

[jira] [Updated] (SPARK-21998) SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

[ https://issues.apache.org/jira/browse/SPARK-21998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maryann Xue updated SPARK-21998: Summary: SortMergeJoinExec did not calculate its outputOrdering correctly during physical planning

[jira] [Assigned] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-21928: Assignee: (was: Apache Spark) > ML LogisticRegression training occasionally produces

[jira] [Assigned] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-21928: Assignee: Apache Spark > ML LogisticRegression training occasionally produces >

[jira] [Commented] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

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

[jira] [Resolved] (SPARK-21338) AggregatedDialect doesn't override isCascadingTruncateTable() method

[ https://issues.apache.org/jira/browse/SPARK-21338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li resolved SPARK-21338. - Resolution: Fixed Assignee: Huaxin Gao Fix Version/s: 2.3.0 > AggregatedDialect doesn't

[jira] [Commented] (SPARK-22063) Upgrade lintr to latest commit sha1 ID

[ https://issues.apache.org/jira/browse/SPARK-22063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171987#comment-16171987 ] Hyukjin Kwon commented on SPARK-22063: -- Will open a PR within few days. > Upgrade lintr to latest

[jira] [Created] (SPARK-22063) Upgrade lintr to latest commit sha1 ID

Hyukjin Kwon created SPARK-22063: Summary: Upgrade lintr to latest commit sha1 ID Key: SPARK-22063 URL: https://issues.apache.org/jira/browse/SPARK-22063 Project: Spark Issue Type:

[jira] [Created] (SPARK-22062) BlockManager does not account for memory consumed by remote fetches

Sergei Lebedev created SPARK-22062: -- Summary: BlockManager does not account for memory consumed by remote fetches Key: SPARK-22062 URL: https://issues.apache.org/jira/browse/SPARK-22062 Project:

[jira] [Commented] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171870#comment-16171870 ] Takeshi Yamamuro commented on SPARK-12823: -- what do u think when is the good timing to take on

[jira] [Commented] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171825#comment-16171825 ] Wenchen Fan commented on SPARK-12823: - Ah now I understand what you want. Even though the data is

[jira] [Resolved] (SPARK-21917) Remote http(s) resources is not supported in YARN mode

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

[jira] [Assigned] (SPARK-21917) Remote http(s) resources is not supported in YARN mode

[ https://issues.apache.org/jira/browse/SPARK-21917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan reassigned SPARK-21917: --- Assignee: Saisai Shao > Remote http(s) resources is not supported in YARN mode >

[jira] [Commented] (SPARK-21972) Allow users to control input data persistence in ML Estimators via a handlePersistence ml.Param

[ https://issues.apache.org/jira/browse/SPARK-21972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171773#comment-16171773 ] Weichen Xu commented on SPARK-21972: [~podongfeng] [~Siddharth Murching] I have a simpler proposal:

[jira] [Commented] (SPARK-22061) Add pipeline model of SVM

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

[jira] [Assigned] (SPARK-22061) Add pipeline model of SVM

[ https://issues.apache.org/jira/browse/SPARK-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22061: Assignee: Apache Spark > Add pipeline model of SVM > - > >

[jira] [Assigned] (SPARK-22061) Add pipeline model of SVM

[ https://issues.apache.org/jira/browse/SPARK-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22061: Assignee: (was: Apache Spark) > Add pipeline model of SVM > -

[jira] [Commented] (SPARK-22061) Add pipeline model of SVM

[ https://issues.apache.org/jira/browse/SPARK-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171754#comment-16171754 ] Sean Owen commented on SPARK-22061: --- What does this mean? > Add pipeline model of SVM >

[jira] [Commented] (SPARK-22059) SVD computation limit

[ https://issues.apache.org/jira/browse/SPARK-22059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171740#comment-16171740 ] Aleksandr Ovcharenko commented on SPARK-22059: -- Thank you! How big then the arrays can be?

[jira] [Created] (SPARK-22061) Add pipeline model of SVM

Jiaming Shu created SPARK-22061: --- Summary: Add pipeline model of SVM Key: SPARK-22061 URL: https://issues.apache.org/jira/browse/SPARK-22061 Project: Spark Issue Type: New Feature

[jira] [Commented] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171735#comment-16171735 ] Simeon H.K. Fitch commented on SPARK-12823: --- [~cloud_fan] If the intent is to *not* support

[jira] [Commented] (SPARK-22060) CrossValidator/TrainValidationSplit parallelism param persist/load bug

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

[jira] [Assigned] (SPARK-22060) CrossValidator/TrainValidationSplit parallelism param persist/load bug

[ https://issues.apache.org/jira/browse/SPARK-22060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22060: Assignee: Apache Spark > CrossValidator/TrainValidationSplit parallelism param

[jira] [Assigned] (SPARK-22060) CrossValidator/TrainValidationSplit parallelism param persist/load bug

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

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171668#comment-16171668 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 1:47 PM:

[jira] [Created] (SPARK-22060) CrossValidator/TrainValidationSplit parallelism param persist/load bug

Weichen Xu created SPARK-22060: -- Summary: CrossValidator/TrainValidationSplit parallelism param persist/load bug Key: SPARK-22060 URL: https://issues.apache.org/jira/browse/SPARK-22060 Project: Spark

[jira] [Updated] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imran Rashid updated SPARK-21928: - Component/s: (was: ML) Spark Core > ML LogisticRegression training

[jira] [Updated] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imran Rashid updated SPARK-21928: - Affects Version/s: 2.1.1 > ML LogisticRegression training occasionally produces >

[jira] [Commented] (SPARK-21928) ML LogisticRegression training occasionally produces java.lang.ClassNotFoundException when attempting to load custom Kryo registrator class

[ https://issues.apache.org/jira/browse/SPARK-21928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171715#comment-16171715 ] Imran Rashid commented on SPARK-21928: -- Hi [~jbrock], thanks for reporting this. I have another

[jira] [Commented] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171679#comment-16171679 ] Wenchen Fan commented on SPARK-12823: - UDF is kind of a SQL terminology so it only works with Spark

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171668#comment-16171668 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 1:30 PM:

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171668#comment-16171668 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 1:24 PM:

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171668#comment-16171668 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 1:22 PM:

[jira] [Commented] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171668#comment-16171668 ] Simeon H.K. Fitch commented on SPARK-12823: --- Here is a combined, runnable example:

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171668#comment-16171668 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 1:21 PM:

[jira] [Resolved] (SPARK-22059) SVD computation limit

[ https://issues.apache.org/jira/browse/SPARK-22059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen resolved SPARK-22059. --- Resolution: Invalid Questions should go to the mailing list. No, it's a limit of how big arrays can

[jira] [Created] (SPARK-22059) SVD computation limit

Aleksandr Ovcharenko created SPARK-22059: Summary: SVD computation limit Key: SPARK-22059 URL: https://issues.apache.org/jira/browse/SPARK-22059 Project: Spark Issue Type: Question

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171627#comment-16171627 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 12:53 PM: -

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171627#comment-16171627 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 12:52 PM: -

[jira] [Comment Edited] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171627#comment-16171627 ] Simeon H.K. Fitch edited comment on SPARK-12823 at 9/19/17 12:52 PM: -

[jira] [Commented] (SPARK-12823) Cannot create UDF with StructType input

[ https://issues.apache.org/jira/browse/SPARK-12823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171627#comment-16171627 ] Simeon H.K. Fitch commented on SPARK-12823: --- When you say "Row", do you mean

[jira] [Resolved] (SPARK-21428) CliSessionState never be recognized because of IsolatedClientLoader

[ https://issues.apache.org/jira/browse/SPARK-21428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wenchen Fan resolved SPARK-21428. - Resolution: Fixed Assignee: Kent Yao (was: Apache Spark) > CliSessionState never be

[jira] [Assigned] (SPARK-22058) the BufferedInputStream will not be closed if an exception occurs

[ https://issues.apache.org/jira/browse/SPARK-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22058: Assignee: Apache Spark > the BufferedInputStream will not be closed if an exception

[jira] [Commented] (SPARK-22058) the BufferedInputStream will not be closed if an exception occurs

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

[jira] [Assigned] (SPARK-22058) the BufferedInputStream will not be closed if an exception occurs

[ https://issues.apache.org/jira/browse/SPARK-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22058: Assignee: (was: Apache Spark) > the BufferedInputStream will not be closed if an

[jira] [Updated] (SPARK-22058) the BufferedInputStream will not be closed if an exception occurs

[ https://issues.apache.org/jira/browse/SPARK-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-22058: -- Issue Type: Improvement (was: Bug) Fine, but not sure that's a bug. Can you look for similar

[jira] [Updated] (SPARK-22058) the BufferedInputStream will not be closed if an exception occurs

[ https://issues.apache.org/jira/browse/SPARK-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-22058: Priority: Minor (was: Major) > the BufferedInputStream will not be closed if an exception occurs

[jira] [Updated] (SPARK-22058) the BufferedInputStream will not be closed if an exception occurs

[ https://issues.apache.org/jira/browse/SPARK-22058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-22058: Description: EventLoggingListener use {code:java} val in = new BufferedInputStream(fs.open(log))

[jira] [Commented] (SPARK-22049) Confusing behavior of from_utc_timestamp and to_utc_timestamp

[ https://issues.apache.org/jira/browse/SPARK-22049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16171523#comment-16171523 ] Felipe Olmos commented on SPARK-22049: -- I think it is much more clearer with the patches. Thanks

[jira] [Assigned] (SPARK-22049) Confusing behavior of from_utc_timestamp and to_utc_timestamp

[ https://issues.apache.org/jira/browse/SPARK-22049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-22049: Assignee: (was: Apache Spark) > Confusing behavior of from_utc_timestamp and

  1   2   >