Michael Armbrust created SPARK-18234:
----------------------------------------
Summary: Update mode
Key: SPARK-18234
URL: https://issues.apache.org/jira/browse/SPARK-18234
Project: Spark
Issue Type: New Feature
Components: Structured Streaming
Reporter: Michael Armbrust
Priority: Critical
We have this internal, but we should nail down the semantics and expose it to
users. The idea of update mode is that any tuple that changes will be emitted.
Open questions:
- do we need to reason about the {{keys}} for a given stream? For things like
the {{foreach}} sink its up to the user. However, for more end to end use
cases such as a JDBC sink, we need to know which row downstream is being
updated.
- okay to not support files?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
