Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/12958#issuecomment-218225663
Trigger clock is an internal details for testing that should not be exposed
to users. Also, this isn't really what the output mode is for. Try reading
the design
Github user agsachin commented on the pull request:
https://github.com/apache/spark/pull/12958#issuecomment-217718480
@tdas , @marmbrus any inputs on this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user agsachin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12958#discussion_r62431170
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -25,13 +25,13 @@ import org.apache.hadoop.fs.Path
import
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/12958#discussion_r62417617
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -25,13 +25,13 @@ import org.apache.hadoop.fs.Path
import
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12958#issuecomment-217482035
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
