[jira] [Commented] (SPARK-21478) Unpersist a DF also unpersists related DFs

[ https://issues.apache.org/jira/browse/SPARK-21478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106203#comment-16106203 ] Vinod KC commented on SPARK-21478: -- https://github.com/apache/spark/pull/18771 > Unpers

[jira] [Commented] (SPARK-21588) SQLContext.getConf(key, null) should return null, but it throws NPE

[ https://issues.apache.org/jira/browse/SPARK-21588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108622#comment-16108622 ] Vinod KC commented on SPARK-21588: -- [~brkyvz] Can you share sample code and NPE stack tr

[jira] [Commented] (SPARK-21390) Dataset filter api inconsistency

[ https://issues.apache.org/jira/browse/SPARK-21390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108880#comment-16108880 ] Vinod KC commented on SPARK-21390: -- [~kiszk]case class is compiled differently in the sp

[jira] [Commented] (SPARK-25177) When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific notation

[ https://issues.apache.org/jira/browse/SPARK-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528877#comment-17528877 ] Vinod KC commented on SPARK-25177: -- In case, if anyone looking for a workaround to conv

[jira] [Comment Edited] (SPARK-25177) When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific notation

[ https://issues.apache.org/jira/browse/SPARK-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528877#comment-17528877 ] Vinod KC edited comment on SPARK-25177 at 4/27/22 4:29 PM: --- In

[jira] [Created] (SPARK-35488) Upgrade ASM to 7.3.1

Vinod KC created SPARK-35488: Summary: Upgrade ASM to 7.3.1 Key: SPARK-35488 URL: https://issues.apache.org/jira/browse/SPARK-35488 Project: Spark Issue Type: Improvement Components: Bu

[jira] [Updated] (SPARK-35488) Upgrade ASM to 7.3.1

[ https://issues.apache.org/jira/browse/SPARK-35488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-35488: - Priority: Minor (was: Major) > Upgrade ASM to 7.3.1 > > > Key: SPA

[jira] [Created] (SPARK-35490) Update json4s to 3.7.0-M16

Vinod KC created SPARK-35490: Summary: Update json4s to 3.7.0-M16 Key: SPARK-35490 URL: https://issues.apache.org/jira/browse/SPARK-35490 Project: Spark Issue Type: Improvement Componen

[jira] [Created] (SPARK-35492) Upgrade Apache HttpCore from 4.4.12 to 4.4.14

Vinod KC created SPARK-35492: Summary: Upgrade Apache HttpCore from 4.4.12 to 4.4.14 Key: SPARK-35492 URL: https://issues.apache.org/jira/browse/SPARK-35492 Project: Spark Issue Type: Improvement

[jira] [Updated] (SPARK-35490) Update json4s to 3.7.0-M11

[ https://issues.apache.org/jira/browse/SPARK-35490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-35490: - Summary: Update json4s to 3.7.0-M11 (was: Update json4s to 3.7.0-M16) > Update json4s to 3.7.0-M11 > --

[jira] [Created] (SPARK-35513) Upgrade joda-time to 2.10.10

Vinod KC created SPARK-35513: Summary: Upgrade joda-time to 2.10.10 Key: SPARK-35513 URL: https://issues.apache.org/jira/browse/SPARK-35513 Project: Spark Issue Type: Improvement Compon

[jira] [Commented] (SPARK-35517) Critical Vulnerabilities: jackson-databind 2.4.0 shipped with htrace-core4-4.1.0-incubating.jar

[ https://issues.apache.org/jira/browse/SPARK-35517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351134#comment-17351134 ] Vinod KC commented on SPARK-35517: -- [~ldeflandre], In Spark 3.2.0, SPARK-34784 upgraded

[jira] [Created] (SPARK-35747) Avoid printing full Exception stack trace, if HBase service is not running in a secure cluster

Vinod KC created SPARK-35747: Summary: Avoid printing full Exception stack trace, if HBase service is not running in a secure cluster Key: SPARK-35747 URL: https://issues.apache.org/jira/browse/SPARK-35747

[jira] [Updated] (SPARK-35747) Avoid printing full Exception stack trace, if HBase service is not running in a secure cluster

[ https://issues.apache.org/jira/browse/SPARK-35747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-35747: - Description: In a secure Yarn cluster where HBase service is down, even if the spark application is not

[jira] [Updated] (SPARK-35747) Avoid printing full Exception stack trace, if HBase/Kafka/Hive services are not running in a secure cluster

[ https://issues.apache.org/jira/browse/SPARK-35747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-35747: - Summary: Avoid printing full Exception stack trace, if HBase/Kafka/Hive services are not running in a se

[jira] [Updated] (SPARK-35747) Avoid printing full Exception stack trace, if HBase/Kafka/Hive services are not running in a secure cluster

[ https://issues.apache.org/jira/browse/SPARK-35747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-35747: - Description: In a secure Yarn cluster, even though HBase or Kafka, or Hive services are not used in the

[jira] [Updated] (SPARK-35747) Avoid printing full Exception stack trace, if HBase/Kafka/Hive services are not running in a secure cluster

[ https://issues.apache.org/jira/browse/SPARK-35747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-35747: - Description: In a secure Yarn cluster, even though HBase or Kafka, or Hive services are not used in the

[jira] [Created] (SPARK-25137) NumberFormatException` when starting spark-shell from Mac terminal

Vinod KC created SPARK-25137: Summary: NumberFormatException` when starting spark-shell from Mac terminal Key: SPARK-25137 URL: https://issues.apache.org/jira/browse/SPARK-25137 Project: Spark

[jira] [Created] (SPARK-25177) When dataframe decimal type column having a scale higher than 6, 0 values are shown in scientific notation

Vinod KC created SPARK-25177: Summary: When dataframe decimal type column having a scale higher than 6, 0 values are shown in scientific notation Key: SPARK-25177 URL: https://issues.apache.org/jira/browse/SPARK-25177

[jira] [Updated] (SPARK-25177) When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific notation

[ https://issues.apache.org/jira/browse/SPARK-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25177: - Summary: When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific

[jira] [Updated] (SPARK-25177) When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific notation

[ https://issues.apache.org/jira/browse/SPARK-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25177: - Description: If scale of decimal type is > 6 , 0 value will be shown in scientific notation and hence,

[jira] [Updated] (SPARK-25177) When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific notation

[ https://issues.apache.org/jira/browse/SPARK-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25177: - Description: If scale of decimal type is > 6 , 0 value will be shown in scientific notation and hence,

[jira] [Updated] (SPARK-25177) When dataframe decimal type column having scale higher than 6, 0 values are shown in scientific notation

[ https://issues.apache.org/jira/browse/SPARK-25177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25177: - Description: If scale of decimal type is > 6 , 0 value will be shown in scientific notation and hence,

[jira] [Created] (SPARK-25301) When a view uses an UDF from a non default database, Spark analyser throws AnalysisException

Vinod KC created SPARK-25301: Summary: When a view uses an UDF from a non default database, Spark analyser throws AnalysisException Key: SPARK-25301 URL: https://issues.apache.org/jira/browse/SPARK-25301

[jira] [Updated] (SPARK-25301) When a view uses an UDF from a non default database, Spark analyser throws AnalysisException

[ https://issues.apache.org/jira/browse/SPARK-25301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25301: - Description: When a hive view uses an UDF from a non default database, Spark analyser throws AnalysisEx

[jira] [Updated] (SPARK-25301) When a view uses an UDF from a non default database, Spark analyser throws AnalysisException

[ https://issues.apache.org/jira/browse/SPARK-25301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25301: - Description: When a hive view uses an UDF from a non default database, Spark analyser throws AnalysisEx

[jira] [Updated] (SPARK-25301) When a view uses an UDF from a non default database, Spark analyser throws AnalysisException

[ https://issues.apache.org/jira/browse/SPARK-25301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-25301: - Description: When a hive view uses an UDF from a non default database, Spark analyser throws AnalysisEx

[jira] [Commented] (SPARK-8628) Race condition in AbstractSparkSQLParser.parse

[ https://issues.apache.org/jira/browse/SPARK-8628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609477#comment-14609477 ] Vinod KC commented on SPARK-8628: - Can you please assign this to me > Race condition in A

[jira] [Created] (SPARK-8787) Change the parameter order of @deprecated in package object sql

Vinod KC created SPARK-8787: --- Summary: Change the parameter order of @deprecated in package object sql Key: SPARK-8787 URL: https://issues.apache.org/jira/browse/SPARK-8787 Project: Spark Issue T

[jira] [Commented] (SPARK-10200) Specify schema during GLMRegressionModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712454#comment-14712454 ] Vinod KC commented on SPARK-10200: -- I'm working on this > Specify schema during GLMRegr

[jira] [Commented] (SPARK-10201) Specify schema during GaussianMixtureModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712455#comment-14712455 ] Vinod KC commented on SPARK-10201: -- I'm working on this > Specify schema during Gaussia

[jira] [Commented] (SPARK-10202) Specify schema during KMeansModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712456#comment-14712456 ] Vinod KC commented on SPARK-10202: -- I'm working on this > Specify schema during KMeansM

[jira] [Commented] (SPARK-10203) Specify schema during GLMClassificationModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712458#comment-14712458 ] Vinod KC commented on SPARK-10203: -- I'm working on this > Specify schema during GLMClas

[jira] [Commented] (SPARK-10204) Specify schema during NaiveBayes.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712459#comment-14712459 ] Vinod KC commented on SPARK-10204: -- I'm working on this > Specify schema during NaiveBa

[jira] [Commented] (SPARK-10206) Specify schema during IsotonicRegression.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712462#comment-14712462 ] Vinod KC commented on SPARK-10206: -- I'm working on this > Specify schema during Isotoni

[jira] [Commented] (SPARK-10205) Specify schema during PowerIterationClustering.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712461#comment-14712461 ] Vinod KC commented on SPARK-10205: -- I'm working on this > Specify schema during PowerIt

[jira] [Commented] (SPARK-10208) Specify schema during LocalLDAModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712464#comment-14712464 ] Vinod KC commented on SPARK-10208: -- I'm working on this > Specify schema during LocalLD

[jira] [Commented] (SPARK-10209) Specify schema during DistributedLDAModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712465#comment-14712465 ] Vinod KC commented on SPARK-10209: -- I'm working on this > Specify schema during Distrib

[jira] [Commented] (SPARK-10207) Specify schema during Word2Vec.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712463#comment-14712463 ] Vinod KC commented on SPARK-10207: -- I'm working on this > Specify schema during Word2Ve

[jira] [Commented] (SPARK-10211) Specify schema during MatrixFactorizationModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712466#comment-14712466 ] Vinod KC commented on SPARK-10211: -- I'm working on this > Specify schema during MatrixF

[jira] [Commented] (SPARK-10212) Specify schema during TreeEnsembleModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712467#comment-14712467 ] Vinod KC commented on SPARK-10212: -- I'm working on this > Specify schema during TreeEns

[jira] [Commented] (SPARK-10213) Specify schema during DecisionTreeModel.save to avoid reflection

[ https://issues.apache.org/jira/browse/SPARK-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712469#comment-14712469 ] Vinod KC commented on SPARK-10213: -- I'm working on this > Specify schema during Decisio

[jira] [Commented] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712496#comment-14712496 ] Vinod KC commented on SPARK-10199: -- Sure, I'll group all the changes into single PR > A

[jira] [Commented] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14721491#comment-14721491 ] Vinod KC commented on SPARK-10199: -- [~fliang] , As you suggested, 1) I've made micro-

[jira] [Commented] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724459#comment-14724459 ] Vinod KC commented on SPARK-10199: -- [~mengxr] 1) I measured only schema inference part.

[jira] [Comment Edited] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724459#comment-14724459 ] Vinod KC edited comment on SPARK-10199 at 9/1/15 6:57 AM: -- [~men

[jira] [Commented] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725211#comment-14725211 ] Vinod KC commented on SPARK-10199: -- [~mengxr] I've measured the overhead of reflexion in

[jira] [Comment Edited] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725211#comment-14725211 ] Vinod KC edited comment on SPARK-10199 at 9/1/15 2:15 PM: -- [~men

[jira] [Created] (SPARK-10414) DenseMatrix gives different hashcode even though equals returns true

Vinod KC created SPARK-10414: Summary: DenseMatrix gives different hashcode even though equals returns true Key: SPARK-10414 URL: https://issues.apache.org/jira/browse/SPARK-10414 Project: Spark

[jira] [Commented] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728427#comment-14728427 ] Vinod KC commented on SPARK-10199: -- [~mengxr] could you please check the above micro-ben

[jira] [Created] (SPARK-10430) AccumulableInfo and RDDOperationScope violates hashCode + equals contract

Vinod KC created SPARK-10430: Summary: AccumulableInfo and RDDOperationScope violates hashCode + equals contract Key: SPARK-10430 URL: https://issues.apache.org/jira/browse/SPARK-10430 Project: Spark

[jira] [Commented] (SPARK-10414) DenseMatrix gives different hashcode even though equals returns true

[ https://issues.apache.org/jira/browse/SPARK-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731745#comment-14731745 ] Vinod KC commented on SPARK-10414: -- [~josephkb] Could you please share me that existing

[jira] [Commented] (SPARK-10199) Avoid using reflections for parquet model save

[ https://issues.apache.org/jira/browse/SPARK-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731753#comment-14731753 ] Vinod KC commented on SPARK-10199: -- [~mengxr] Thanks for the suggestion. Shall I close

[jira] [Commented] (SPARK-10414) DenseMatrix gives different hashcode even though equals returns true

[ https://issues.apache.org/jira/browse/SPARK-10414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731757#comment-14731757 ] Vinod KC commented on SPARK-10414: -- Thanks Got the JIRA id https://issues.apache.org/jir

[jira] [Created] (SPARK-10468) Verify schema before Dataframe select API call

Vinod KC created SPARK-10468: Summary: Verify schema before Dataframe select API call Key: SPARK-10468 URL: https://issues.apache.org/jira/browse/SPARK-10468 Project: Spark Issue Type: Improvemen

[jira] [Created] (SPARK-10575) Wrap RDD.takeSample with scope

Vinod KC created SPARK-10575: Summary: Wrap RDD.takeSample with scope Key: SPARK-10575 URL: https://issues.apache.org/jira/browse/SPARK-10575 Project: Spark Issue Type: Improvement Comp

[jira] [Commented] (SPARK-10631) Add missing API doc in pyspark.mllib.linalg.Vector

[ https://issues.apache.org/jira/browse/SPARK-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746994#comment-14746994 ] Vinod KC commented on SPARK-10631: -- I'm working on this > Add missing API doc in pyspar

[jira] [Created] (SPARK-32635) When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong result

Vinod KC created SPARK-32635: Summary: When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong result Key: SPARK-32635 URL: https://issues.apache.org/jira/browse/SPARK-32635

[jira] [Updated] (SPARK-32635) When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong result

[ https://issues.apache.org/jira/browse/SPARK-32635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-32635: - Description: When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong r

[jira] [Updated] (SPARK-20880) When spark SQL is used with Avro-backed HIVE tables, NPE from org.apache.hadoop.hive.serde2.avro.AvroObjectInspectorGenerator.supportedCategories.

[ https://issues.apache.org/jira/browse/SPARK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-20880: - Description: When spark SQL is used with Avro-backed HIVE tables, intermittently getting NPE from org.

[jira] [Updated] (SPARK-20880) When spark SQL is used with Avro-backed HIVE tables, NPE from org.apache.hadoop.hive.serde2.avro.AvroObjectInspectorGenerator.supportedCategories.

[ https://issues.apache.org/jira/browse/SPARK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-20880: - Description: When spark SQL is used with Avro-backed HIVE tables, intermittently getting NPE from org.

[jira] [Commented] (SPARK-20880) When spark SQL is used with Avro-backed HIVE tables, NPE from org.apache.hadoop.hive.serde2.avro.AvroObjectInspectorGenerator.supportedCategories.

[ https://issues.apache.org/jira/browse/SPARK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180307#comment-17180307 ] Vinod KC commented on SPARK-20880: -- SPARK-29981 has added support to use hive-2.3 in Sp

[jira] [Comment Edited] (SPARK-20880) When spark SQL is used with Avro-backed HIVE tables, NPE from org.apache.hadoop.hive.serde2.avro.AvroObjectInspectorGenerator.supportedCategories.

[ https://issues.apache.org/jira/browse/SPARK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180307#comment-17180307 ] Vinod KC edited comment on SPARK-20880 at 8/19/20, 6:53 AM:

[jira] [Comment Edited] (SPARK-20880) When spark SQL is used with Avro-backed HIVE tables, NPE from org.apache.hadoop.hive.serde2.avro.AvroObjectInspectorGenerator.supportedCategories.

[ https://issues.apache.org/jira/browse/SPARK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180307#comment-17180307 ] Vinod KC edited comment on SPARK-20880 at 8/19/20, 6:54 AM:

[jira] [Comment Edited] (SPARK-20880) When spark SQL is used with Avro-backed HIVE tables, NPE from org.apache.hadoop.hive.serde2.avro.AvroObjectInspectorGenerator.supportedCategories.

[ https://issues.apache.org/jira/browse/SPARK-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180307#comment-17180307 ] Vinod KC edited comment on SPARK-20880 at 8/19/20, 6:55 AM:

[jira] [Commented] (SPARK-26825) Spark Structure Streaming job failing when submitted in cluster mode

[ https://issues.apache.org/jira/browse/SPARK-26825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229719#comment-17229719 ] Vinod KC commented on SPARK-26825: -- As a workaround, we can set a {{checkpointLocation

[jira] [Commented] (SPARK-28287) Convert and port 'udaf.sql' into UDF test base

[ https://issues.apache.org/jira/browse/SPARK-28287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882743#comment-16882743 ] Vinod KC commented on SPARK-28287: -- [~skonto]I'm sorry, without checking your comment I

[jira] [Comment Edited] (SPARK-28287) Convert and port 'udaf.sql' into UDF test base

[ https://issues.apache.org/jira/browse/SPARK-28287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882743#comment-16882743 ] Vinod KC edited comment on SPARK-28287 at 7/11/19 8:31 AM: --- [~

[jira] [Updated] (SPARK-32635) When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong result

[ https://issues.apache.org/jira/browse/SPARK-32635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-32635: - Description: When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong r

[jira] [Commented] (SPARK-32635) When pyspark.sql.functions.lit() function is used with dataframe cache, it returns wrong result

[ https://issues.apache.org/jira/browse/SPARK-32635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181800#comment-17181800 ] Vinod KC commented on SPARK-32635: -- [~sascha.baumanns], updated code section. Thanks >

[jira] [Commented] (SPARK-32938) Spark can not cast long value from Kafka

[ https://issues.apache.org/jira/browse/SPARK-32938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200028#comment-17200028 ] Vinod KC commented on SPARK-32938: -- [~maseiler],  Can you please test with this exampl

[jira] [Commented] (SPARK-6733) Suppression of usage of Scala existential code should be done

[ https://issues.apache.org/jira/browse/SPARK-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484841#comment-14484841 ] Vinod KC commented on SPARK-6733: - Can you please assign this to me? > Suppression of usa

[jira] [Created] (SPARK-7055) getContextOrSparkClassLoader is not used while loading JDBC driver class

Vinod KC created SPARK-7055: --- Summary: getContextOrSparkClassLoader is not used while loading JDBC driver class Key: SPARK-7055 URL: https://issues.apache.org/jira/browse/SPARK-7055 Project: Spark

[jira] [Commented] (SPARK-7103) SparkContext.union crashed when some RDDs have no partitioner

[ https://issues.apache.org/jira/browse/SPARK-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510621#comment-14510621 ] Vinod KC commented on SPARK-7103: - I closed PR #5678.. thanks > SparkContext.union crashe

[jira] [Created] (SPARK-7438) Validation Error while running countApproxDistinct with relative accuracy >= 0.38

Vinod KC created SPARK-7438: --- Summary: Validation Error while running countApproxDistinct with relative accuracy >= 0.38 Key: SPARK-7438 URL: https://issues.apache.org/jira/browse/SPARK-7438 Project: S

[jira] [Updated] (SPARK-7438) Validation Error while running countApproxDistinct with relative accuracy >= 0.38

[ https://issues.apache.org/jira/browse/SPARK-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-7438: Description: Eg Code: val a = sc.parallelize(1 to 1, 20) val b = a ++ a ++ a ++ a ++ a b.countApproxDis

[jira] [Created] (SPARK-7489) Spark shell crashes when compiled with scala 2.11 and SPARK_PREPEND_CLASSES=true

Vinod KC created SPARK-7489: --- Summary: Spark shell crashes when compiled with scala 2.11 and SPARK_PREPEND_CLASSES=true Key: SPARK-7489 URL: https://issues.apache.org/jira/browse/SPARK-7489 Project: Spark

[jira] [Commented] (SPARK-8919) Add @since tags to mllib.recommendation

[ https://issues.apache.org/jira/browse/SPARK-8919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644572#comment-14644572 ] Vinod KC commented on SPARK-8919: - Please assign this issue to me > Add @since tags to ml

[jira] [Created] (SPARK-44325) Define the computing logic through PartitionEvaluator API and use it in SortMergeJoinExec

Vinod KC created SPARK-44325: Summary: Define the computing logic through PartitionEvaluator API and use it in SortMergeJoinExec Key: SPARK-44325 URL: https://issues.apache.org/jira/browse/SPARK-44325 Pro

[jira] [Created] (SPARK-44330) Define the computing logic through PartitionEvaluator API and use it in BroadcastNestedLoopJoinExec & BroadcastHashJoinExec

Vinod KC created SPARK-44330: Summary: Define the computing logic through PartitionEvaluator API and use it in BroadcastNestedLoopJoinExec & BroadcastHashJoinExec Key: SPARK-44330 URL: https://issues.apache.org/jira/b

[jira] [Commented] (SPARK-44330) Define the computing logic through PartitionEvaluator API and use it in BroadcastNestedLoopJoinExec & BroadcastHashJoinExec

[ https://issues.apache.org/jira/browse/SPARK-44330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741734#comment-17741734 ] Vinod KC commented on SPARK-44330: -- PR raised : https://github.com/apache/spark/pull/41

[jira] [Commented] (SPARK-44359) Define the computing logic through PartitionEvaluator API and use it in SQL aggregate operators

[ https://issues.apache.org/jira/browse/SPARK-44359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741736#comment-17741736 ] Vinod KC commented on SPARK-44359: -- Im working on this > Define the computing logic th

[jira] [Created] (SPARK-44359) Define the computing logic through PartitionEvaluator API and use it in SQL aggregate operators

Vinod KC created SPARK-44359: Summary: Define the computing logic through PartitionEvaluator API and use it in SQL aggregate operators Key: SPARK-44359 URL: https://issues.apache.org/jira/browse/SPARK-44359

[jira] [Created] (SPARK-44361) Use PartitionEvaluator API in BatchEvalPythonUDTFExec, FlatMapGroupsInPandasExec, MapInBatchExec, FlatMapCoGroupsInPandasExec

Vinod KC created SPARK-44361: Summary: Use PartitionEvaluator API in BatchEvalPythonUDTFExec, FlatMapGroupsInPandasExec, MapInBatchExec, FlatMapCoGroupsInPandasExec Key: SPARK-44361 URL: https://issues.apache.org/jir

[jira] [Created] (SPARK-44362) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

Vinod KC created SPARK-44362: Summary: Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec Key: SPARK-44362 URL: https://issues.apache.org/jira/browse/

[jira] [Created] (SPARK-44365) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

Vinod KC created SPARK-44365: Summary: Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec Key: SPARK-44365 URL: https://issues.apache.org/jira/browse/

[jira] [Updated] (SPARK-44365) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

[ https://issues.apache.org/jira/browse/SPARK-44365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44365: - Description: InMemoryTableScanExec (was: `BatchEvalPythonUDTFExec` `FlatMapGroupsInPandasExec` `MapInBat

[jira] [Updated] (SPARK-44365) Define the computing logic through PartitionEvaluator API and use it in SQL operators InMemoryTableScanExec

[ https://issues.apache.org/jira/browse/SPARK-44365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44365: - Summary: Define the computing logic through PartitionEvaluator API and use it in SQL operators InMemoryT

[jira] [Updated] (SPARK-44365) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

[ https://issues.apache.org/jira/browse/SPARK-44365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44365: - Description: Define the computing logic through PartitionEvaluator API and use it in SQL operators `InMe

[jira] [Commented] (SPARK-44361) Use PartitionEvaluator API in BatchEvalPythonUDTFExec, FlatMapGroupsInPandasExec, MapInBatchExec, FlatMapCoGroupsInPandasExec

[ https://issues.apache.org/jira/browse/SPARK-44361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741836#comment-17741836 ] Vinod KC commented on SPARK-44361: -- Im working on it > Use PartitionEvaluator API in

[jira] [Commented] (SPARK-44365) Define the computing logic through PartitionEvaluator API and use it in SQL operators InMemoryTableScanExec

[ https://issues.apache.org/jira/browse/SPARK-44365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741837#comment-17741837 ] Vinod KC commented on SPARK-44365: -- Im working on it > Define the computing logic thro

[jira] [Commented] (SPARK-44362) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

[ https://issues.apache.org/jira/browse/SPARK-44362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741838#comment-17741838 ] Vinod KC commented on SPARK-44362: -- Im working on it > Use PartitionEvaluator API in

[jira] [Created] (SPARK-44369) Use PartitionEvaluator API in CollectMetricsExec, GenerateExec, ExpandExec, DebugExec, HiveTableScanExec, DataSourceScanExec

Vinod KC created SPARK-44369: Summary: Use PartitionEvaluator API in CollectMetricsExec, GenerateExec, ExpandExec, DebugExec, HiveTableScanExec, DataSourceScanExec Key: SPARK-44369 URL: https://issues.apache.org/jira/

[jira] [Commented] (SPARK-44369) Use PartitionEvaluator API in CollectMetricsExec, GenerateExec, ExpandExec, DebugExec, HiveTableScanExec, DataSourceScanExec

[ https://issues.apache.org/jira/browse/SPARK-44369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741839#comment-17741839 ] Vinod KC commented on SPARK-44369: -- I'm working on it > Use PartitionEvaluator API in

[jira] [Updated] (SPARK-44369) Use PartitionEvaluator API in CollectMetricsExec, GenerateExec, ExpandExec, DebugExec, HiveTableScanExec, DataSourceScanExec

[ https://issues.apache.org/jira/browse/SPARK-44369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44369: - Description: Use PartitionEvaluator API in  CollectMetricsExec GenerateExec ExpandExec DebugExec HiveTa

[jira] [Updated] (SPARK-44369) Use PartitionEvaluator API in CollectMetricsExec, GenerateExec, ExpandExec, DebugExec, HiveTableScanExec, DataSourceScanExec, SortExec

[ https://issues.apache.org/jira/browse/SPARK-44369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44369: - Summary: Use PartitionEvaluator API in CollectMetricsExec, GenerateExec, ExpandExec, DebugExec, HiveTabl

[jira] [Updated] (SPARK-44365) Define the computing logic through PartitionEvaluator API and use it in SQL operators InMemoryTableScanExec, DataSourceScanExec, MergeRowsExec , ReferenceSort

[ https://issues.apache.org/jira/browse/SPARK-44365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44365: - Description: Define the computing logic through PartitionEvaluator API and use it in SQL operators  In

[jira] [Updated] (SPARK-44365) Define the computing logic through PartitionEvaluator API and use it in SQL operators InMemoryTableScanExec, DataSourceScanExec, MergeRowsExec , ReferenceSort

[ https://issues.apache.org/jira/browse/SPARK-44365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44365: - Summary: Define the computing logic through PartitionEvaluator API and use it in SQL operators InMemoryT

[jira] [Commented] (SPARK-44362) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

[ https://issues.apache.org/jira/browse/SPARK-44362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742099#comment-17742099 ] Vinod KC commented on SPARK-44362: -- yes, please go ahead > Use PartitionEvaluator API

[jira] [Updated] (SPARK-44362) Use PartitionEvaluator API in AggregateInPandasExec, WindowInPandasExec,EvalPythonExec,AttachDistributedSequenceExec

[ https://issues.apache.org/jira/browse/SPARK-44362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod KC updated SPARK-44362: - Description: Use  PartitionEvaluator API in AggregateInPandasExec EvalPythonExec AttachDistributedSeq

  1   2   3   >