Package org.apache.beam.sdk.schemas.transforms

Class TypedSchemaTransformProvider<ConfigT>

java.lang.Object
org.apache.beam.sdk.schemas.transforms.TypedSchemaTransformProvider<ConfigT>
All Implemented Interfaces:
SchemaTransformProvider
Direct Known Subclasses:
BigQueryDirectReadSchemaTransformProvider, BigQueryExportReadSchemaTransformProvider, BigQueryFileLoadsSchemaTransformProvider, BigQueryStorageWriteApiSchemaTransformProvider, BigQueryWriteSchemaTransformProvider, BigtableReadSchemaTransformProvider, BigtableWriteSchemaTransformProvider, CsvWriteTransformProvider, DebeziumReadSchemaTransformProvider, FileReadSchemaTransformProvider, FileWriteSchemaTransformProvider, FlattenTransformProvider, GenerateSequenceSchemaTransformProvider, IcebergCdcReadSchemaTransformProvider, IcebergReadSchemaTransformProvider, IcebergWriteSchemaTransformProvider, JavaExplodeTransformProvider, JavaFilterTransformProvider, JavaMapToFieldsTransformProvider, JdbcReadSchemaTransformProvider, JdbcWriteSchemaTransformProvider, JsonWriteTransformProvider, KafkaReadSchemaTransformProvider, KafkaWriteSchemaTransformProvider, LoggingTransformProvider, ManagedSchemaTransformProvider, PubsubLiteReadSchemaTransformProvider, PubsubLiteWriteSchemaTransformProvider, PubsubReadSchemaTransformProvider, PubsubWriteSchemaTransformProvider, SingleStoreSchemaTransformReadProvider, SingleStoreSchemaTransformWriteProvider, SpannerChangestreamsReadSchemaTransformProvider, SpannerReadSchemaTransformProvider, SpannerWriteSchemaTransformProvider, SqsReadSchemaTransformProvider, TestSchemaTransformProvider, TFRecordReadSchemaTransformProvider, TFRecordWriteSchemaTransformProvider, WindowIntoTransformProvider
@Internal public abstract class TypedSchemaTransformProvider<ConfigT> extends Object implements SchemaTransformProvider
Like SchemaTransformProvider except uses a configuration object instead of Schema and Row.

ConfigT should be available in the SchemaRegistry.

configurationSchema() produces a configuration Schema that is inferred from ConfigT using the SchemaRegistry. A Beam Row can still be used to produce a SchemaTransform using from(Row), as long as the Row fits the configuration Schema.

NOTE: The inferred field names in the configuration Schema and Row follow the snake_case naming convention.

Internal only: This interface is actively being worked on and it will likely change as we provide implementations for more standard Beam transforms. We provide no backwards compatibility guarantees and it should not be implemented outside of the Beam repository.