tWritePositionalFields 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

tWritePositionalFields properties for Apache Spark Structured Streaming

Last updated: 9/30/2026
Feature in preview

Use these properties to configure tWritePositionalFields running in the Spark Structured Streaming Job framework.

The Spark Structured Streaming tWritePositionalFields 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.
Output type Select the type of serialized positional record from the drop-down list:
  • byte[]: outputs the record as a binary byte array.
  • String: outputs the record as a string.
Schema and Edit schema Use the schema to define the output column that stores the serialized positional record. Click Edit schema to modify the output schema.
Use data column as partition key Select this check box to use a data column as the partition key when writing to a downstream component such as tKinesisOutput.
Include Header Select this check box to include a header row in the output. When selected, specify the following separators:
  • Row separator: enter the character that separates rows in the output record. The default value is \n.
  • Field separator (header): enter the character that separates fields in the header row.
Custom encoding Select this check box to specify the character encoding for the output record. When selected, choose the encoding from the Encoding drop-down list.
Field formats Configure the format of each input column. The field formats are applied in schema order to create the output record:
  • Size: enter the fixed width of the field. A value less than or equal to zero does not enforce a width.
  • Padding char: enter the character to add when the value is shorter than the specified size.
  • Alignment: select Left, Center, or Right to control where padding is added.
  • Keep: select the portion of a value to retain when it exceeds the specified size.

Advanced settings

Properties Description
Advanced separator (for number) Select this check box to define the separators used when serializing number values. Then specify the following characters:
  • Thousands separator: enter the character used to separate groups of thousands.
  • Decimal separator: enter the character used to separate the integer and fractional parts of a number.

Usage

Usage guidance Description
Usage rule

This component is used as an intermediate step.

This component serializes input rows as fixed-width positional records.

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