Class DataStreamWriter<T>
- All Implemented Interfaces:
- WriteConfigMethods<DataStreamWriter<T>>
Dataset to external storage systems (e.g. file systems,
 key-value stores, etc). Use Dataset.writeStream to access this.
 - Since:
- 2.0.0
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionClusters the output by the given columns.abstract DataStreamWriter<T>Clusters the output by the given columns.abstract DataStreamWriter<T>foreach(ForeachWriter<T> writer) Sets the output of the streaming query to be processed using the provided writer object.foreachBatch(VoidFunction2<Dataset<T>, Long> function) :: Experimental ::abstract DataStreamWriter<T>foreachBatch(scala.Function2<Dataset<T>, Object, scala.runtime.BoxedUnit> function) :: Experimental ::abstract DataStreamWriter<T>Specifies the underlying output data source.Add a boolean output option.Add a double output option.Add a long output option.abstract DataStreamWriter<T>outputMode(String outputMode) Specifies how data of a streaming DataFrame/Dataset is written to a streaming sink.abstract DataStreamWriter<T>outputMode(OutputMode outputMode) Specifies how data of a streaming DataFrame/Dataset is written to a streaming sink.partitionBy(String... colNames) Partitions the output by the given columns on the file system.abstract DataStreamWriter<T>partitionBy(scala.collection.immutable.Seq<String> colNames) Partitions the output by the given columns on the file system.abstract DataStreamWriter<T>Specifies the name of theStreamingQuerythat can be started withstart().abstract StreamingQuerystart()Starts the execution of the streaming query, which will continually output results to the given path as new data arrives.abstract StreamingQueryStarts the execution of the streaming query, which will continually output results to the given path as new data arrives.abstract StreamingQueryStarts the execution of the streaming query, which will continually output results to the given table as new data arrives.abstract DataStreamWriter<T>Set the trigger for the stream query.Methods inherited from class java.lang.Objectequals, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.apache.spark.sql.WriteConfigMethodsoption, options, options
- 
Constructor Details- 
DataStreamWriterpublic DataStreamWriter()
 
- 
- 
Method Details- 
clusterByClusters the output by the given columns. If specified, the output is laid out such that records with similar values on the clustering column are grouped together in the same file.Clustering improves query efficiency by allowing queries with predicates on the clustering columns to skip unnecessary data. Unlike partitioning, clustering can be used on very high cardinality columns. - Parameters:
- colNames- (undocumented)
- Returns:
- (undocumented)
- Since:
- 4.0.0
 
- 
clusterByClusters the output by the given columns. If specified, the output is laid out such that records with similar values on the clustering column are grouped together in the same file.Clustering improves query efficiency by allowing queries with predicates on the clustering columns to skip unnecessary data. Unlike partitioning, clustering can be used on very high cardinality columns. - Parameters:
- colNames- (undocumented)
- Returns:
- (undocumented)
- Since:
- 4.0.0
 
- 
foreachSets the output of the streaming query to be processed using the provided writer object. object. SeeForeachWriterfor more details on the lifecycle and semantics.- Parameters:
- writer- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
foreachBatchpublic abstract DataStreamWriter<T> foreachBatch(scala.Function2<Dataset<T>, Object, scala.runtime.BoxedUnit> function) :: 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). - Parameters:
- function- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.4.0
 
- 
foreachBatch:: 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). - Parameters:
- function- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.4.0
 
- 
formatSpecifies the underlying output data source.- Parameters:
- source- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
optionDescription copied from interface:WriteConfigMethodsAdd a boolean output option.- Specified by:
- optionin interface- WriteConfigMethods<T>
- Parameters:
- key- (undocumented)
- value- (undocumented)
- Returns:
- (undocumented)
 
- 
optionDescription copied from interface:WriteConfigMethodsAdd a long output option.- Specified by:
- optionin interface- WriteConfigMethods<T>
- Parameters:
- key- (undocumented)
- value- (undocumented)
- Returns:
- (undocumented)
 
- 
optionDescription copied from interface:WriteConfigMethodsAdd a double output option.- Specified by:
- optionin interface- WriteConfigMethods<T>
- Parameters:
- key- (undocumented)
- value- (undocumented)
- Returns:
- (undocumented)
 
- 
outputModeSpecifies 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 toOutputMode.Append()mode.
 - Parameters:
- outputMode- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
 
- 
outputModeSpecifies 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 toappendmode.
 - Parameters:
- outputMode- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
 
- 
partitionByPartitions 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. - Parameters:
- colNames- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
partitionByPartitions 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. - Parameters:
- colNames- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
queryNameSpecifies the name of theStreamingQuerythat can be started withstart(). This name must be unique among all the currently active queries in the associated SparkSession.- Parameters:
- queryName- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
startStarts the execution of the streaming query, which will continually output results to the given path as new data arrives. The returnedStreamingQueryobject can be used to interact with the stream.- Parameters:
- path- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
- 
startStarts the execution of the streaming query, which will continually output results to the given path as new data arrives. The returnedStreamingQueryobject can be used to interact with the stream. Throws aTimeoutExceptionif 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 configurationspark.sql.streaming.stopActiveRunOnRestartis enabled - The active run cannot be stopped within the timeout controlled by the SQL configurationspark.sql.streaming.stopTimeout- Returns:
- (undocumented)
- Throws:
- TimeoutException
- Since:
- 2.0.0
 
- 
toTableStarts the execution of the streaming query, which will continually output results to the given table as new data arrives. The returnedStreamingQueryobject can be used to interact with the stream.For v1 table, partitioning columns provided by partitionBywill be respected no matter the table exists or not. A new table will be created if the table not exists.For v2 table, partitionBywill be ignored if the table already exists.partitionBywill 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.- Parameters:
- tableName- (undocumented)
- Returns:
- (undocumented)
- Throws:
- TimeoutException
- Since:
- 3.1.0
 
- 
triggerSet the trigger for the stream query. The default value isProcessingTime(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))- Parameters:
- trigger- (undocumented)
- Returns:
- (undocumented)
- Since:
- 2.0.0
 
 
-