Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/8441#discussion_r38056282
--- Diff: docs/sql-programming-guide.md ---
@@ -870,12 +886,11 @@ saveDF(select(df, "name", "age"),
"namesAndAges.parquet", "parquet")
Save operations can optionally take a `SaveMode`, that specifies how to
handle existing data if
present. It is important to realize that these save modes do not utilize
any locking and are not
-atomic. Thus, it is not safe to have multiple writers attempting to write
to the same location.
-Additionally, when performing a `Overwrite`, the data will be deleted
before writing out the
+atomic. Additionally, when performing a `Overwrite`, the data will be
deleted before writing out the
new data.
<table class="table">
-<tr><th>Scala/Java</th><th>Python</th><th>Meaning</th></tr>
+<tr><th>Scala/Java</th><th>Any Language</th><th>Meaning</th></tr>
--- End diff --
It works in scala too though? I wasn't really sure what to do here. We
could also just delete the other column?
---
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 does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
