[GitHub] [spark] dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks

2019-10-01 Thread GitBox
dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks URL: https://github.com/apache/spark/pull/25988#issuecomment-537325767 Thank you, @MaxGekk , @cloud-fan , @srowen .

[GitHub] [spark] dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks

2019-10-01 Thread GitBox
dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks URL: https://github.com/apache/spark/pull/25988#issuecomment-537325531 Thanks. Then, I'll merge this. This will unblock the benchmarks.

[GitHub] [spark] dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks

2019-10-01 Thread GitBox
dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks URL: https://github.com/apache/spark/pull/25988#issuecomment-537325559 Merged to master. This is an automated message

[GitHub] [spark] dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks

2019-10-01 Thread GitBox
dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks URL: https://github.com/apache/spark/pull/25988#issuecomment-537321407 @brkyvz and @cloud-fan . Is this change intentional?

[GitHub] [spark] dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks

2019-10-01 Thread GitBox
dongjoon-hyun commented on issue #25988: [SPARK-29313][SQL] Fix failure on writing to `noop` in benchmarks URL: https://github.com/apache/spark/pull/25988#issuecomment-537321016 I'm not sure about this. For me, we need to fix the root cause inside DSv2.