tWindow properties for Apache Spark Structured Streaming | Talend Components for Jobs Help
Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

tWindow properties for Apache Spark Structured Streaming

Last updated: 9/30/2026
Feature in preview

These properties are used to configure tWindow running in the Spark Structured Streaming Job framework.

The Spark Structured Streaming tWindow component belongs to the Processing family.

The streaming version of this component is available in Talend Real-Time Big Data Platform and in Talend Data Fabric.

Basic settings

Properties Description
Schema and Edit schema

A schema is a row description. It defines the fields (columns) processed by the component. When you create a Spark Job, avoid the reserved word line when naming fields.

  • Built-In: create and store the schema locally for this component only.

  • Repository: reuse a schema created and stored in the Repository across projects and Job designs.

Click Edit schema to modify the schema. If you modify a Repository schema, the available options include:

  • View schema: view the schema without modifying it.

  • Change to built-in property: change the schema to Built-in for local changes.

  • Update repository connection: modify the Repository schema and choose whether to propagate the changes to other Jobs.
Window Type Select the type of window to apply from the drop-down list:
  • Tumbling Window (Fixed-size, non-overlapping): divides the stream into fixed-size, non-overlapping time windows. Each event belongs to exactly one window.
  • Sliding Window (Fixed-size, overlapping): applies fixed-size windows that slide forward at a defined interval. Events can belong to multiple windows.
  • Session Window: groups events separated by periods of inactivity. A new window starts when the gap between events exceeds the defined gap duration.
Time Column Select the timestamp column from the schema to use as the basis for windowing.
Window Duration Enter the length of each window as a time string, for example "10 minutes" or "1 hour".

This property is available for Tumbling Window and Sliding Window.
Slide Duration Enter the interval at which the window advances as a time string, for example "5 minutes". The slide duration must be less than or equal to the window duration.

This property is available for Sliding Window only.
Session Gap Duration Enter the inactivity gap that closes a session window as a time string, for example "5 minutes". A new window opens when the next event arrives after the gap.

This property is available for Session Window only.
Start Time (optional) Enter an offset to align window boundaries to a specific time, for example "15 minutes". Defaults to "0 seconds" when not set.

This property is available for Tumbling Window and Sliding Window.

Advanced settings

Properties Description
Return window expression for group by (performance optimization) Select this check box to return the window as a column expression instead of applying it directly to the dataset. Use this option when passing the window expression to a groupBy operation to avoid recomputing the window column.

Usage

Usage guidance Description
Usage rule

This component is used as an intermediate step.

This component adds a window column to the dataset based on the selected window type and timestamp column.

This component, along with the Spark Structured Streaming component Palette it belongs to, appears only when you are creating a Spark Structured Streaming Job.

Spark Connection

You need to use the Structured Streaming Configuration tab in the Run view to define the connection to a Spark cluster for the whole Job.

This connection is effective on a per-Job basis.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here