[jira] [Comment Edited] (SPARK-27638) date format yyyy-M-dd string comparison not handled properly

2019-05-07 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834322#comment-16834322 ] peng bo edited comment on SPARK-27638 at 5/7/19 9:21 AM: - [~maxg

[jira] [Comment Edited] (SPARK-27638) date format yyyy-M-dd string comparison not handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834322#comment-16834322 ] peng bo edited comment on SPARK-27638 at 5/7/19 5:47 AM: - [~maxg

[jira] [Updated] (SPARK-27638) date format yyyy-M-dd string comparison not handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27638: Description: The below example works with both Mysql and Hive, however not with spark. {code:java} mysql>

[jira] [Commented] (SPARK-27638) date format yyyy-M-dd string comparison not handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834322#comment-16834322 ] peng bo commented on SPARK-27638: - [~maxgekk] I'd love propose a PR for this. However

[jira] [Updated] (SPARK-27638) date format yyyy-M-dd string comparison not handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27638: Summary: date format -M-dd string comparison not handled properly (was: date format -M-dd compar

[jira] [Updated] (SPARK-27638) date format yyyy-M-dd comparison not handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27638: Summary: date format -M-dd comparison not handled properly (was: date format -M-dd comparison is

[jira] [Commented] (SPARK-27638) date format yyyy-M-dd comparison isn't handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833584#comment-16833584 ] peng bo commented on SPARK-27638: - [~cloud_fan] [~srowen] Your opinion will be appreciat

[jira] [Updated] (SPARK-27638) date format yyyy-M-dd comparison isn't handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27638: Description: The below example works with both Mysql and Hive, however not with spark. {code:java} mysql>

[jira] [Updated] (SPARK-27638) date format yyyy-M-dd comparison isn't handled properly

2019-05-06 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27638: Description: The below example works with both Mysql and Hive, however not with spark. {code:java} mysql>

[jira] [Created] (SPARK-27638) date format yyyy-M-dd comparison isn't handled properly

2019-05-06 Thread peng bo (JIRA)
peng bo created SPARK-27638: --- Summary: date format -M-dd comparison isn't handled properly Key: SPARK-27638 URL: https://issues.apache.org/jira/browse/SPARK-27638 Project: Spark Issue Type: Bu

[jira] [Updated] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27565: Description: Currently it's really hard to link SQL plan to Spark jobs on SparkSQL UI page. When one job

[jira] [Updated] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27565: Description: Currently it's really hard to link SQL plan to Spark jobs on SparkSQL UI page. When one job

[jira] [Updated] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27565: Attachment: SPARK-27565.jpg > Show job info of WholeStageCodegen node on SparkSQL UI page > --

[jira] [Updated] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27565: Attachment: (was: SPARK-27565.jpg) > Show job info of WholeStageCodegen node on SparkSQL UI page > ---

[jira] [Updated] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27565: Description: Currently it's really hard to link SQL plan to Spark jobs on {{SparkSQL}} page. When one job

[jira] [Updated] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27565: Attachment: SPARK-27565.jpg > Show job info of WholeStageCodegen node on SparkSQL UI page > --

[jira] [Created] (SPARK-27565) Show job info of WholeStageCodegen node on SparkSQL UI page

2019-04-25 Thread peng bo (JIRA)
peng bo created SPARK-27565: --- Summary: Show job info of WholeStageCodegen node on SparkSQL UI page Key: SPARK-27565 URL: https://issues.apache.org/jira/browse/SPARK-27565 Project: Spark Issue Type

[jira] [Updated] (SPARK-27539) Inaccurate aggregate outputRows estimation with column contains null value

2019-04-22 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27539: Summary: Inaccurate aggregate outputRows estimation with column contains null value (was: Inaccurate aggr

[jira] [Updated] (SPARK-27539) Inaccurate aggregate outputRows estimation with null value column

2019-04-22 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27539: Description: This issue is follow up of [https://github.com/apache/spark/pull/24286]. As [~smilegator] po

[jira] [Created] (SPARK-27539) Inaccurate aggregate outputRows estimation with null value column

2019-04-22 Thread peng bo (JIRA)
peng bo created SPARK-27539: --- Summary: Inaccurate aggregate outputRows estimation with null value column Key: SPARK-27539 URL: https://issues.apache.org/jira/browse/SPARK-27539 Project: Spark Issu

[jira] [Updated] (SPARK-27518) Show statistics in Optimized Logical Plan in the "Details" On SparkSQL ui page when CBO is enabled

2019-04-18 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27518: Attachment: SPARK-27518-1.jpg > Show statistics in Optimized Logical Plan in the "Details" On SparkSQL ui

[jira] [Created] (SPARK-27518) Show statistics in Optimized Logical Plan in the "Details" On SparkSQL ui page when CBO is enabled

2019-04-18 Thread peng bo (JIRA)
peng bo created SPARK-27518: --- Summary: Show statistics in Optimized Logical Plan in the "Details" On SparkSQL ui page when CBO is enabled Key: SPARK-27518 URL: https://issues.apache.org/jira/browse/SPARK-27518

[jira] [Updated] (SPARK-27482) Show BroadcastHashJoinExec numOutputRows statistics info on SparkSQL UI page

2019-04-16 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27482: Description: Currently, the {{SparkSQL}} UI page shows only actual {{metric}} info in each {{SparkPlan}} 

[jira] [Updated] (SPARK-27482) Show BroadcastHashJoinExec numOutputRows statistics info on SparkSQL UI page

2019-04-16 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27482: Summary: Show BroadcastHashJoinExec numOutputRows statistics info on SparkSQL UI page (was: Show Broadcas

[jira] [Updated] (SPARK-27482) Show BroadcastHashJoinExec numOutputRows statistic info on SparkSQL UI page

2019-04-16 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27482: Attachment: SPARK-27482-1.png > Show BroadcastHashJoinExec numOutputRows statistic info on SparkSQL UI pag

[jira] [Created] (SPARK-27482) Show BroadcastHashJoinExec numOutputRows statistic info on SparkSQL UI page

2019-04-16 Thread peng bo (JIRA)
peng bo created SPARK-27482: --- Summary: Show BroadcastHashJoinExec numOutputRows statistic info on SparkSQL UI page Key: SPARK-27482 URL: https://issues.apache.org/jira/browse/SPARK-27482 Project: Spark

[jira] [Closed] (SPARK-27415) UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size

2019-04-09 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo closed SPARK-27415. --- > UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines > have different Oops size >

[jira] [Resolved] (SPARK-27415) UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size

2019-04-09 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo resolved SPARK-27415. - Resolution: Invalid duplicate one due to network issue.. > UnsafeMapData & UnsafeArrayData Kryo seriali

[jira] [Created] (SPARK-27416) UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size

2019-04-09 Thread peng bo (JIRA)
peng bo created SPARK-27416: --- Summary: UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size Key: SPARK-27416 URL: https://issues.apache.org/jira/browse/SPARK-27416

[jira] [Created] (SPARK-27415) UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size

2019-04-09 Thread peng bo (JIRA)
peng bo created SPARK-27415: --- Summary: UnsafeMapData & UnsafeArrayData Kryo serialization breaks when two machines have different Oops size Key: SPARK-27415 URL: https://issues.apache.org/jira/browse/SPARK-27415

[jira] [Commented] (SPARK-27406) UnsafeArrayData serialization breaks when two machines have different Oops size

2019-04-08 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812376#comment-16812376 ] peng bo commented on SPARK-27406: - [~sandeep.katta2007]  Actually, I have already submi

[jira] [Updated] (SPARK-27406) UnsafeArrayData serialization breaks when two machines have different Oops size

2019-04-07 Thread peng bo (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng bo updated SPARK-27406: Description: ApproxCountDistinctForIntervals holds the UnsafeArrayData data to initialize endpoints. When

[jira] [Created] (SPARK-27406) UnsafeArrayData serialization breaks when two machines have different Oops size

2019-04-07 Thread peng bo (JIRA)
peng bo created SPARK-27406: --- Summary: UnsafeArrayData serialization breaks when two machines have different Oops size Key: SPARK-27406 URL: https://issues.apache.org/jira/browse/SPARK-27406 Project: Spark

[jira] [Created] (SPARK-27351) Wrong outputRows estimation after AggregateEstimation with only null value column

2019-04-02 Thread peng bo (JIRA)
peng bo created SPARK-27351: --- Summary: Wrong outputRows estimation after AggregateEstimation with only null value column Key: SPARK-27351 URL: https://issues.apache.org/jira/browse/SPARK-27351 Project: Spar