szehon-ho commented on code in PR #57481:
URL: https://github.com/apache/spark/pull/57481#discussion_r3648663533
##########
sql/catalyst/src/main/java/org/apache/spark/sql/connector/catalog/TableCapability.java:
##########
@@ -106,5 +106,23 @@ public enum TableCapability {
* write modes, like {@link #TRUNCATE}, and {@link #OVERWRITE_BY_FILTER},
but cannot support
* {@link #OVERWRITE_DYNAMIC}.
*/
- V1_BATCH_WRITE
+ V1_BATCH_WRITE,
+
+ /**
+ * Signals that the table wants Spark to auto-fill generated column values
and enforce generated
+ * column constraints during writes.
+ * <p>
+ * When this capability is present, Spark will:
+ * <ul>
+ * <li>Auto-compute missing generated column values using the generation
expression.</li>
Review Comment:
Fixed in e2e66ee4a07. The capability documentation now scopes auto-filling
to by-name writes and says in plain language that ordinary by-position writes
must provide a value for every table column. I also clarified this distinction
in the PR description.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
