[
https://issues.apache.org/jira/browse/FLINK-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550884#comment-16550884
]
François Lacombe commented on FLINK-9813:
-----------------------------------------
Hi [~twalthr]
I've no problem to deal with {{AvroSchemaConverter}} until it's actually
possible to build CsvTableSource from fields defined in Avro. Thank you to let
me know this.
I'll move to this approach if it's the official and documented one.
But I don't get why Csv should be a dependency of Avro and not the opposite.
Avro should be a dependency of Csv since we can make the CsvTableSource or the
InputFormat to get their fields from Avro schema, can't you ?
> 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)
