Sets the output of the streaming query to be processed using the provided writer object. object. See org.apache.spark.sql.ForeachWriter for more details on the lifecycle and semantics.

:: Experimental ::

(Java-specific) Sets the output of the streaming query to be processed using the provided function. This is supported only in the micro-batch execution modes (that is, when the trigger is not continuous). In every micro-batch, the provided function will be called in every micro-batch with (i) the output rows as a Dataset and (ii) the batch identifier. The batchId can be used to deduplicate and transactionally write the output (that is, the provided Dataset) to external systems. The output Dataset is guaranteed to be exactly the same for the same batchId (assuming all operations are deterministic in the query).

:: Experimental ::

(Scala-specific) Sets the output of the streaming query to be processed using the provided function. This is supported only in the micro-batch execution modes (that is, when the trigger is not continuous). In every micro-batch, the provided function will be called in every micro-batch with (i) the output rows as a Dataset and (ii) the batch identifier. The batchId can be used to deduplicate and transactionally write the output (that is, the provided Dataset) to external systems. The output Dataset is guaranteed to be exactly the same for the same batchId (assuming all operations are deterministic in the query).

Specifies the underlying output data source.

Adds an output option for the underlying data source.

Adds an output option for the underlying data source.

Adds an output option for the underlying data source.

Adds an output option for the underlying data source.

Adds output options for the underlying data source.

(Scala-specific) Adds output options for the underlying data source.

Specifies how data of a streaming DataFrame/Dataset is written to a streaming sink.

• append: only the new rows in the streaming DataFrame/Dataset will be written to the sink.
• complete: all the rows in the streaming DataFrame/Dataset will be written to the sink every time there are some updates.
• update: only the rows that were updated in the streaming DataFrame/Dataset will be written to the sink every time there are some updates. If the query doesn't contain aggregations, it will be equivalent to append mode.

Specifies how data of a streaming DataFrame/Dataset is written to a streaming sink.

• OutputMode.Append(): only the new rows in the streaming DataFrame/Dataset will be written to the sink.
• OutputMode.Complete(): all the rows in the streaming DataFrame/Dataset will be written to the sink every time there are some updates.
• OutputMode.Update(): only the rows that were updated in the streaming DataFrame/Dataset will be written to the sink every time there are some updates. If the query doesn't contain aggregations, it will be equivalent to OutputMode.Append() mode.

Partitions the output by the given columns on the file system. If specified, the output is laid out on the file system similar to Hive's partitioning scheme. As an example, when we partition a dataset by year and then month, the directory layout would look like:

• year=2016/month=01/
• year=2016/month=02/

Partitioning is one of the most widely used techniques to optimize physical data layout. It provides a coarse-grained index for skipping unnecessary data reads when queries have predicates on the partitioned columns. In order for partitioning to work well, the number of distinct values in each column should typically be less than tens of thousands.

Specifies the name of the StreamingQuery that can be started with start(). This name must be unique among all the currently active queries in the associated SQLContext.

Starts the execution of the streaming query, which will continually output results to the given path as new data arrives. The returned StreamingQuery object can be used to interact with the stream. Throws a TimeoutException if the following conditions are met:

• Another run of the same streaming query, that is a streaming query sharing the same checkpoint location, is already active on the same Spark Driver
• The SQL configuration spark.sql.streaming.stopActiveRunOnRestart is enabled
• The active run cannot be stopped within the timeout controlled by the SQL configuration spark.sql.streaming.stopTimeout

Starts the execution of the streaming query, which will continually output results to the given path as new data arrives. The returned StreamingQuery object can be used to interact with the stream.

Starts the execution of the streaming query, which will continually output results to the given table as new data arrives. The returned StreamingQuery object can be used to interact with the stream.

For v1 table, partitioning columns provided by partitionBy will be respected no matter the table exists or not. A new table will be created if the table not exists.

For v2 table, partitionBy will be ignored if the table already exists. partitionBy will be respected only if the v2 table does not exist. Besides, the v2 table created by this API lacks some functionalities (e.g., customized properties, options, and serde info). If you need them, please create the v2 table manually before the execution to avoid creating a table with incomplete information.

Set the trigger for the stream query. The default value is ProcessingTime(0) and it will run the query as fast as possible.

Scala Example:

df.writeStream.trigger(ProcessingTime("10 seconds"))

import scala.concurrent.duration._
df.writeStream.trigger(ProcessingTime(10.seconds))

Java Example:

df.writeStream().trigger(ProcessingTime.create("10 seconds"))

import java.util.concurrent.TimeUnit
df.writeStream().trigger(ProcessingTime.create(10, TimeUnit.SECONDS))