[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-660441720 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-660422348 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-660415514 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-657005559 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-656990616 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-656277611 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-655293059 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-655124035 retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-654009122 Retest this please This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [spark] imback82 commented on pull request #28676: [SPARK-31869][SQL] BroadcastHashJoinExec can utilize the build side for its output partitioning

imback82 commented on pull request #28676: URL: https://github.com/apache/spark/pull/28676#issuecomment-653710418 > It's kind of replacing one or more columns from the streaming side partitioning with the corresponding join keys, and get all the combinations. Makes sense. Thanks for