flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timo Walther (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-8240) Create unified interfaces to configure and instatiate TableSources
Date Mon, 11 Dec 2017 17:22:00 GMT
Timo Walther created FLINK-8240:
-----------------------------------

             Summary: Create unified interfaces to configure and instatiate TableSources
                 Key: FLINK-8240
                 URL: https://issues.apache.org/jira/browse/FLINK-8240
             Project: Flink
          Issue Type: New Feature
          Components: Table API & SQL
            Reporter: Timo Walther
            Assignee: Timo Walther


At the moment every table source has different ways for configuration and instantiation. Some
table source are tailored to a specific encoding (e.g., {{KafkaAvroTableSource}}, {{KafkaJsonTableSource}})
or only support one encoding for reading (e.g., {{CsvTableSource}}). Each of them might implement
a builder or support table source converters for external catalogs.

The table sources should have a unified interface for discovery, defining common properties,
and instantiation. The {{TableSourceConverters}} provide a similar functionality but use a
external catalog. We might generialize this interface.

In general a table source declaration depends on the following parts:

- Source
  - Type (e.g. Kafka, Custom)
  - Properties (e.g. topic, connection info)
- Encoding
  - Type (e.g. Avro, JSON, CSV)
  - Schema (e.g. Avro class, JSON field names/types)
- Rowtime descriptor/Proctime
  - Watermark strategy and Watermark properties
  - Time attribute info
- Bucketization

This issue needs a design document before implementation. Any discussion is very welcome.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message