[
https://issues.apache.org/jira/browse/FLINK-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549333#comment-16549333
]
François Lacombe commented on FLINK-9813:
-----------------------------------------
Hi Fabian,
Nice we agree on that :)
I think the Builder class, or at least the InputFormat class to which the
Schema is provided could check if the schema provide compatible elements and thr
Il s'inspire déjà de quelques projets passés, mais il peut toujours y avoir des
manques. Si vous identifiez une situation que nous avons eu à modéliser qui ne
rentre pas dans le cadre, ce serait intéressant de l'étudier.
ow Exception if not to prevent the SourceTable to be built.
Nested Avro types may be supported, if a particular column contains JSON
string. But it may be out of the scope of csv format specification.
I'm totally ok with Csv.avroSchema to build a Csv format descriptor.
Do you know the release number which will deliver this rework of Sources ?
> Build xTableSource from Avro schemas
> ------------------------------------
>
> Key: FLINK-9813
> URL: https://issues.apache.org/jira/browse/FLINK-9813
> Project: Flink
> Issue Type: Wish
> Components: Table API & SQL
> Affects Versions: 1.5.0
> Reporter: François Lacombe
> Priority: Trivial
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> As Avro provide efficient data schemas formalism, it may be great to be able
> to build Flink Tables Sources with such files.
> More info about Avro schemas
> :[https://avro.apache.org/docs/1.8.1/spec.html#schemas]
> For instance, with CsvTableSource :
> Parser schemaParser = new Schema.Parser();
> Schema tableSchema = schemaParser.parse("avro.json");
> Builder bld = CsvTableSource.builder().schema(tableSchema);
>
> This would give me a fully available CsvTableSource with columns defined in
> avro.json
> It may be possible to do so for every TableSources since avro format is
> really common and versatile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
