[jira] [Updated] (SPARK-17851) Make sure all test sqls in catalyst pass checkAnalyze

[ https://issues.apache.org/jira/browse/SPARK-17851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiang Xingbo updated SPARK-17851: - Description: Currently we have several tens of test sqls in catalyst will fail at

[jira] [Commented] (SPARK-16002) Sleep when no new data arrives to avoid 100% CPU usage

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

[jira] [Resolved] (SPARK-16980) Load only catalog table partition metadata required to answer a query

[ https://issues.apache.org/jira/browse/SPARK-16980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin resolved SPARK-16980. - Resolution: Fixed Fix Version/s: 2.1.0 > Load only catalog table partition metadata

[jira] [Resolved] (SPARK-17946) Python crossJoin API similar to Scala

[ https://issues.apache.org/jira/browse/SPARK-17946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin resolved SPARK-17946. - Resolution: Fixed Assignee: Srinath Fix Version/s: 2.1.0 > Python crossJoin API

[jira] [Updated] (SPARK-17951) BlockFetch with multiple threads slows down after spark 1.6

[ https://issues.apache.org/jira/browse/SPARK-17951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ding updated SPARK-17951: - Description: The following code demonstrates the issue: def main(args: Array[String]): Unit = { val conf =

[jira] [Commented] (SPARK-17813) Maximum data per trigger

[ https://issues.apache.org/jira/browse/SPARK-17813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577037#comment-15577037 ] Cody Koeninger commented on SPARK-17813: To be clear, the current direct stream (and as a result

[jira] [Created] (SPARK-17951) BlockFetch with multiple threads slows down after spark 1.6

ding created SPARK-17951: Summary: BlockFetch with multiple threads slows down after spark 1.6 Key: SPARK-17951 URL: https://issues.apache.org/jira/browse/SPARK-17951 Project: Spark Issue Type: Bug

[jira] [Updated] (SPARK-17812) More granular control of starting offsets (assign)

[ https://issues.apache.org/jira/browse/SPARK-17812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Koeninger updated SPARK-17812: --- Description: Right now you can only run a Streaming Query starting from either the earliest

[jira] [Commented] (SPARK-17812) More granular control of starting offsets (assign)

[ https://issues.apache.org/jira/browse/SPARK-17812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15577022#comment-15577022 ] Cody Koeninger commented on SPARK-17812: Assign is useful, otherwise you have no way of consuming

[jira] [Assigned] (SPARK-17950) Match SparseVector behavior with DenseVector

[ https://issues.apache.org/jira/browse/SPARK-17950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17950: Assignee: Apache Spark > Match SparseVector behavior with DenseVector >

[jira] [Commented] (SPARK-17950) Match SparseVector behavior with DenseVector

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

[jira] [Assigned] (SPARK-17950) Match SparseVector behavior with DenseVector

[ https://issues.apache.org/jira/browse/SPARK-17950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17950: Assignee: (was: Apache Spark) > Match SparseVector behavior with DenseVector >

[jira] [Created] (SPARK-17950) Match SparseVector behavior with DenseVector

AbderRahman Sobh created SPARK-17950: Summary: Match SparseVector behavior with DenseVector Key: SPARK-17950 URL: https://issues.apache.org/jira/browse/SPARK-17950 Project: Spark Issue

[jira] [Assigned] (SPARK-17949) Introduce a JVM object based aggregate operator

[ https://issues.apache.org/jira/browse/SPARK-17949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian reassigned SPARK-17949: -- Assignee: Cheng Lian > Introduce a JVM object based aggregate operator >

[jira] [Created] (SPARK-17949) Introduce a JVM object based aggregate operator

Reynold Xin created SPARK-17949: --- Summary: Introduce a JVM object based aggregate operator Key: SPARK-17949 URL: https://issues.apache.org/jira/browse/SPARK-17949 Project: Spark Issue Type:

[jira] [Resolved] (SPARK-17948) WARN CodeGenerator: Error calculating stats of compiled class

[ https://issues.apache.org/jira/browse/SPARK-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-17948. Resolution: Duplicate > WARN CodeGenerator: Error calculating stats of compiled class >

[jira] [Created] (SPARK-17948) WARN CodeGenerator: Error calculating stats of compiled class

Harish created SPARK-17948: -- Summary: WARN CodeGenerator: Error calculating stats of compiled class Key: SPARK-17948 URL: https://issues.apache.org/jira/browse/SPARK-17948 Project: Spark Issue

[jira] [Resolved] (SPARK-17900) Mark the following Spark SQL APIs as stable

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

[jira] [Commented] (SPARK-17812) More granular control of starting offsets (assign)

[ https://issues.apache.org/jira/browse/SPARK-17812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576840#comment-15576840 ] Michael Armbrust commented on SPARK-17812: -- That sounds pretty good to me, with one question:

[jira] [Resolved] (SPARK-17942) OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

[ https://issues.apache.org/jira/browse/SPARK-17942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish resolved SPARK-17942. Resolution: Works for Me > OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using >

[jira] [Commented] (SPARK-17813) Maximum data per trigger

[ https://issues.apache.org/jira/browse/SPARK-17813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576826#comment-15576826 ] Michael Armbrust commented on SPARK-17813: -- I think its okay to ignore compacted topics, at

[jira] [Resolved] (SPARK-11775) Allow PySpark to register Java UDF

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

[jira] [Commented] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

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

[jira] [Assigned] (SPARK-17748) One-pass algorithm for linear regression with L1 and elastic-net penalties

[ https://issues.apache.org/jira/browse/SPARK-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17748: Assignee: Apache Spark (was: Seth Hendrickson) > One-pass algorithm for linear

[jira] [Commented] (SPARK-17748) One-pass algorithm for linear regression with L1 and elastic-net penalties

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

[jira] [Assigned] (SPARK-17748) One-pass algorithm for linear regression with L1 and elastic-net penalties

[ https://issues.apache.org/jira/browse/SPARK-17748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17748: Assignee: Seth Hendrickson (was: Apache Spark) > One-pass algorithm for linear

[jira] [Commented] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576763#comment-15576763 ] Xiao Li commented on SPARK-17709: - That is what I said above. The deduplication is not triggered. It

[jira] [Commented] (SPARK-12776) Implement Python API for Datasets

[ https://issues.apache.org/jira/browse/SPARK-12776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576739#comment-15576739 ] Michael Armbrust commented on SPARK-12776: -- I would love to see better support here, but I don't

[jira] [Resolved] (SPARK-16063) Add storageLevel to Dataset

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

[jira] [Commented] (SPARK-10954) Parquet version in the "created_by" metadata field of Parquet files written by Spark 1.5 and 1.6 is wrong

[ https://issues.apache.org/jira/browse/SPARK-10954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576623#comment-15576623 ] Cheng Lian commented on SPARK-10954: [~hyukjin.kwon], yes, confirmed. Thanks! > Parquet version in

[jira] [Updated] (SPARK-17863) SELECT distinct does not work if there is a order by clause

[ https://issues.apache.org/jira/browse/SPARK-17863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai updated SPARK-17863: - Assignee: Davies Liu > SELECT distinct does not work if there is a order by clause >

[jira] [Resolved] (SPARK-17863) SELECT distinct does not work if there is a order by clause

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

[jira] [Assigned] (SPARK-17947) Document the impact of `spark.sql.debug`

[ https://issues.apache.org/jira/browse/SPARK-17947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17947: Assignee: (was: Apache Spark) > Document the impact of `spark.sql.debug` >

[jira] [Assigned] (SPARK-17947) Document the impact of `spark.sql.debug`

[ https://issues.apache.org/jira/browse/SPARK-17947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17947: Assignee: Apache Spark > Document the impact of `spark.sql.debug` >

[jira] [Commented] (SPARK-17947) Document the impact of `spark.sql.debug`

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

[jira] [Created] (SPARK-17947) Just document the impact of `spark.sql.debug`

Xiao Li created SPARK-17947: --- Summary: Just document the impact of `spark.sql.debug` Key: SPARK-17947 URL: https://issues.apache.org/jira/browse/SPARK-17947 Project: Spark Issue Type:

[jira] [Updated] (SPARK-17947) Document the impact of `spark.sql.debug`

[ https://issues.apache.org/jira/browse/SPARK-17947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17947: Summary: Document the impact of `spark.sql.debug` (was: Just document the impact of `spark.sql.debug`) >

[jira] [Updated] (SPARK-17944) sbin/start-* scripts use of `hostname -f` fail with Solaris

[ https://issues.apache.org/jira/browse/SPARK-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik O'Shaughnessy updated SPARK-17944: --- Summary: sbin/start-* scripts use of `hostname -f` fail with Solaris (was:

[jira] [Closed] (SPARK-9783) Use SqlNewHadoopRDD in JSONRelation to eliminate extra refresh() call

[ https://issues.apache.org/jira/browse/SPARK-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian closed SPARK-9783. - Resolution: Not A Problem This issue is no longer a problem since we re-implemented the JSON data source

[jira] [Commented] (SPARK-9783) Use SqlNewHadoopRDD in JSONRelation to eliminate extra refresh() call

[ https://issues.apache.org/jira/browse/SPARK-9783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576523#comment-15576523 ] Cheng Lian commented on SPARK-9783: --- Yes, I'm closing this. Thanks! > Use SqlNewHadoopRDD in

[jira] [Commented] (SPARK-17636) Parquet filter push down doesn't handle struct fields

[ https://issues.apache.org/jira/browse/SPARK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576513#comment-15576513 ] Cheng Lian commented on SPARK-17636: [~MasterDDT], yes, just as what [~hyukjin.kwon] explained

[jira] [Updated] (SPARK-17636) Parquet filter push down doesn't handle struct fields

[ https://issues.apache.org/jira/browse/SPARK-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cheng Lian updated SPARK-17636: --- Description: There's a *PushedFilters* for a simple numeric field, but not for a numeric field

[jira] [Commented] (SPARK-17946) Python crossJoin API similar to Scala

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

[jira] [Assigned] (SPARK-17946) Python crossJoin API similar to Scala

[ https://issues.apache.org/jira/browse/SPARK-17946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17946: Assignee: Apache Spark > Python crossJoin API similar to Scala >

[jira] [Assigned] (SPARK-17946) Python crossJoin API similar to Scala

[ https://issues.apache.org/jira/browse/SPARK-17946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17946: Assignee: (was: Apache Spark) > Python crossJoin API similar to Scala >

[jira] [Assigned] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

[ https://issues.apache.org/jira/browse/SPARK-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17620: Assignee: Dilip Biswal (was: Apache Spark) > hive.default.fileformat=orc does not set

[jira] [Updated] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

[ https://issues.apache.org/jira/browse/SPARK-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai updated SPARK-17620: - Fix Version/s: (was: 2.1.0) > hive.default.fileformat=orc does not set OrcSerde >

[jira] [Reopened] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

[ https://issues.apache.org/jira/browse/SPARK-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai reopened SPARK-17620: -- > hive.default.fileformat=orc does not set OrcSerde > - >

[jira] [Commented] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

[ https://issues.apache.org/jira/browse/SPARK-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576492#comment-15576492 ] Yin Huai commented on SPARK-17620: -- The PR somehow breaks the build and it has been reverted. >

[jira] [Assigned] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

[ https://issues.apache.org/jira/browse/SPARK-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17620: Assignee: Apache Spark (was: Dilip Biswal) > hive.default.fileformat=orc does not set

[jira] [Created] (SPARK-17946) Python crossJoin API similar to Scala

Srinath created SPARK-17946: --- Summary: Python crossJoin API similar to Scala Key: SPARK-17946 URL: https://issues.apache.org/jira/browse/SPARK-17946 Project: Spark Issue Type: Bug

[jira] [Created] (SPARK-17945) Writing to S3 should allow setting object metadata

Jeff Schobelock created SPARK-17945: --- Summary: Writing to S3 should allow setting object metadata Key: SPARK-17945 URL: https://issues.apache.org/jira/browse/SPARK-17945 Project: Spark

[jira] [Closed] (SPARK-17941) Logistic regression test suites should use weights when comparing to glmnet

[ https://issues.apache.org/jira/browse/SPARK-17941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DB Tsai closed SPARK-17941. --- Resolution: Fixed Fix Version/s: 2.1.0 > Logistic regression test suites should use weights when

[jira] [Updated] (SPARK-17941) Logistic regression test suites should use weights when comparing to glmnet

[ https://issues.apache.org/jira/browse/SPARK-17941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] DB Tsai updated SPARK-17941: Assignee: Seth Hendrickson > Logistic regression test suites should use weights when comparing to glmnet >

[jira] [Updated] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

[ https://issues.apache.org/jira/browse/SPARK-17620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17620: Assignee: Dilip Biswal > hive.default.fileformat=orc does not set OrcSerde >

[jira] [Resolved] (SPARK-17620) hive.default.fileformat=orc does not set OrcSerde

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

[jira] [Comment Edited] (SPARK-17942) OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

[ https://issues.apache.org/jira/browse/SPARK-17942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576375#comment-15576375 ] Harish edited comment on SPARK-17942 at 10/14/16 8:20 PM: -- --conf

[jira] [Commented] (SPARK-17942) OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

[ https://issues.apache.org/jira/browse/SPARK-17942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576375#comment-15576375 ] Harish commented on SPARK-17942: --conf "spark.executor.extraJavaOptions=-XX:ReservedCodeCacheSize=600m"

[jira] [Commented] (SPARK-17944) sbin/start-* scripts use of `hostname -f` fail for Solaris

[ https://issues.apache.org/jira/browse/SPARK-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576367#comment-15576367 ] Erik O'Shaughnessy commented on SPARK-17944: I'm sure there are situations where Linux and OS

[jira] [Commented] (SPARK-17944) sbin/start-* scripts use of `hostname -f` fail for Solaris

[ https://issues.apache.org/jira/browse/SPARK-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576323#comment-15576323 ] Sean Owen commented on SPARK-17944: --- Yeah, I think Solaris is the odd man out here then. Linux and OS X

[jira] [Updated] (SPARK-17937) Clarify Kafka offset semantics for Structured Streaming

[ https://issues.apache.org/jira/browse/SPARK-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Koeninger updated SPARK-17937: --- Description: Possible events for which offsets are needed: # New partition is discovered #

[jira] [Updated] (SPARK-17937) Clarify Kafka offset semantics for Structured Streaming

[ https://issues.apache.org/jira/browse/SPARK-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Koeninger updated SPARK-17937: --- Description: Possible events for which offsets are needed: # New partition is discovered #

[jira] [Created] (SPARK-17944) sbin/start-* scripts use of `hostname -f` fail for Solaris

Erik O'Shaughnessy created SPARK-17944: -- Summary: sbin/start-* scripts use of `hostname -f` fail for Solaris Key: SPARK-17944 URL: https://issues.apache.org/jira/browse/SPARK-17944 Project:

[jira] [Assigned] (SPARK-10541) Allow ApplicationHistoryProviders to provide their own text when there aren't any complete apps

[ https://issues.apache.org/jira/browse/SPARK-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-10541: Assignee: Apache Spark > Allow ApplicationHistoryProviders to provide their own text when

[jira] [Commented] (SPARK-10541) Allow ApplicationHistoryProviders to provide their own text when there aren't any complete apps

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

[jira] [Assigned] (SPARK-10541) Allow ApplicationHistoryProviders to provide their own text when there aren't any complete apps

[ https://issues.apache.org/jira/browse/SPARK-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-10541: Assignee: (was: Apache Spark) > Allow ApplicationHistoryProviders to provide their

[jira] [Updated] (SPARK-17937) Clarify Kafka offset semantics for Structured Streaming

[ https://issues.apache.org/jira/browse/SPARK-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Koeninger updated SPARK-17937: --- Description: Possible events for which offsets are needed: # New partition is discovered #

[jira] [Assigned] (SPARK-17863) SELECT distinct does not work if there is a order by clause

[ https://issues.apache.org/jira/browse/SPARK-17863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17863: Assignee: Apache Spark > SELECT distinct does not work if there is a order by clause >

[jira] [Assigned] (SPARK-17863) SELECT distinct does not work if there is a order by clause

[ https://issues.apache.org/jira/browse/SPARK-17863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17863: Assignee: (was: Apache Spark) > SELECT distinct does not work if there is a order by

[jira] [Commented] (SPARK-17863) SELECT distinct does not work if there is a order by clause

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

[jira] [Resolved] (SPARK-17943) Change Memoized to Memorized

[ https://issues.apache.org/jira/browse/SPARK-17943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcelo Vanzin resolved SPARK-17943. Resolution: Not A Problem https://en.wikipedia.org/wiki/Memoization > Change Memoized to

[jira] [Updated] (SPARK-17943) Change Memoized to Memorized

[ https://issues.apache.org/jira/browse/SPARK-17943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Sabat updated SPARK-17943: Priority: Minor (was: Major) > Change Memoized to Memorized > > >

[jira] [Created] (SPARK-17943) Change Memoized to Memorized

Sunil Sabat created SPARK-17943: --- Summary: Change Memoized to Memorized Key: SPARK-17943 URL: https://issues.apache.org/jira/browse/SPARK-17943 Project: Spark Issue Type: Documentation

[jira] [Updated] (SPARK-17937) Clarify Kafka offset semantics for Structured Streaming

[ https://issues.apache.org/jira/browse/SPARK-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cody Koeninger updated SPARK-17937: --- Description: Possible events for which offsets are needed: # New partition is discovered #

[jira] [Comment Edited] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576141#comment-15576141 ] Ashish Shrowty edited comment on SPARK-17709 at 10/14/16 6:41 PM: -- There

[jira] [Issue Comment Deleted] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Shrowty updated SPARK-17709: --- Comment: was deleted (was: There is a slight difference .. in my case its companyid#121 in

[jira] [Commented] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576143#comment-15576143 ] Ashish Shrowty commented on SPARK-17709: There is a slight difference .. in my case its

[jira] [Commented] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576141#comment-15576141 ] Ashish Shrowty commented on SPARK-17709: There is a slight difference, in my case the IDs

[jira] [Commented] (SPARK-17863) SELECT distinct does not work if there is a order by clause

[ https://issues.apache.org/jira/browse/SPARK-17863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576133#comment-15576133 ] Yin Huai commented on SPARK-17863: -- Seems it is introduced by

[jira] [Commented] (SPARK-17863) SELECT distinct does not work if there is a order by clause

[ https://issues.apache.org/jira/browse/SPARK-17863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576135#comment-15576135 ] Yin Huai commented on SPARK-17863: -- cc [~davies] > SELECT distinct does not work if there is a order by

[jira] [Updated] (SPARK-17863) SELECT distinct does not work if there is a order by clause

[ https://issues.apache.org/jira/browse/SPARK-17863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Huai updated SPARK-17863: - Description: {code} select distinct struct.a, struct.b from ( select named_struct('a', 1, 'b', 2, 'c',

[jira] [Updated] (SPARK-17884) In the cast expression, casting from empty string to interval type throws NullPointerException

[ https://issues.apache.org/jira/browse/SPARK-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynold Xin updated SPARK-17884: Fix Version/s: 1.6.3 > In the cast expression, casting from empty string to interval type throws

[jira] [Updated] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17709: Priority: Critical (was: Major) > spark 2.0 join - column resolution error >

[jira] [Updated] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17709: Component/s: SQL > spark 2.0 join - column resolution error > > >

[jira] [Updated] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-17709: Labels: (was: easyfix) > spark 2.0 join - column resolution error >

[jira] [Commented] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575999#comment-15575999 ] Xiao Li commented on SPARK-17709: - Below is the statements I used to recreate the problem {noformat}

[jira] [Commented] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575995#comment-15575995 ] Xiao Li commented on SPARK-17709: - Still works well in 2.0.1 > spark 2.0 join - column resolution error

[jira] [Commented] (SPARK-17936) "CodeGenerator - failed to compile: org.codehaus.janino.JaninoRuntimeException: Code of" method Error

[ https://issues.apache.org/jira/browse/SPARK-17936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575945#comment-15575945 ] Justin Miller commented on SPARK-17936: --- Hey Sean, I did a bit more digging this morning looking

[jira] [Commented] (SPARK-17709) spark 2.0 join - column resolution error

[ https://issues.apache.org/jira/browse/SPARK-17709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575938#comment-15575938 ] Xiao Li commented on SPARK-17709: - I can get an exactly same plan in the master branch, but my job can

[jira] [Commented] (SPARK-17606) New batches are not created when there are 1000 created after restarting streaming from checkpoint.

[ https://issues.apache.org/jira/browse/SPARK-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575927#comment-15575927 ] etienne commented on SPARK-17606: - I'm not able to reproduce in local mode. either because the

[jira] [Commented] (SPARK-12664) Expose raw prediction scores in MultilayerPerceptronClassificationModel

[ https://issues.apache.org/jira/browse/SPARK-12664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575865#comment-15575865 ] Guo-Xun Yuan commented on SPARK-12664: -- Thank you, [~yanboliang]! So, just to confirm, will your PR

[jira] [Comment Edited] (SPARK-13802) Fields order in Row(**kwargs) is not consistent with Schema.toInternal method

[ https://issues.apache.org/jira/browse/SPARK-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575825#comment-15575825 ] Thomas Dunne edited comment on SPARK-13802 at 10/14/16 4:45 PM: This is

[jira] [Commented] (SPARK-13802) Fields order in Row(**kwargs) is not consistent with Schema.toInternal method

[ https://issues.apache.org/jira/browse/SPARK-13802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575825#comment-15575825 ] Thomas Dunne commented on SPARK-13802: -- This is especially troublesome when combined with creating a

[jira] [Updated] (SPARK-17940) Typo in LAST function error message

[ https://issues.apache.org/jira/browse/SPARK-17940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-17940: -- Priority: Trivial (was: Minor) > Typo in LAST function error message >

[jira] [Commented] (SPARK-17942) OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

[ https://issues.apache.org/jira/browse/SPARK-17942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575759#comment-15575759 ] Sean Owen commented on SPARK-17942: --- You probably need to increase this value -- is there more to it?

[jira] [Updated] (SPARK-17942) OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

[ https://issues.apache.org/jira/browse/SPARK-17942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harish updated SPARK-17942: --- Priority: Minor (was: Major) > OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using

[jira] [Created] (SPARK-17942) OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

Harish created SPARK-17942: -- Summary: OpenJDK 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize= Key: SPARK-17942 URL: https://issues.apache.org/jira/browse/SPARK-17942

[jira] [Assigned] (SPARK-17941) Logistic regression test suites should use weights when comparing to glmnet

[ https://issues.apache.org/jira/browse/SPARK-17941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17941: Assignee: (was: Apache Spark) > Logistic regression test suites should use weights

[jira] [Commented] (SPARK-17941) Logistic regression test suites should use weights when comparing to glmnet

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

[jira] [Assigned] (SPARK-17941) Logistic regression test suites should use weights when comparing to glmnet

[ https://issues.apache.org/jira/browse/SPARK-17941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apache Spark reassigned SPARK-17941: Assignee: Apache Spark > Logistic regression test suites should use weights when

  1   2   >