[
https://issues.apache.org/jira/browse/PHOENIX-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040539#comment-17040539
]
Bharath Vissapragada commented on PHOENIX-5443:
-----------------------------------------------
Another issue with the Confluence schema registry is that it depends on the
Kafka connect from Confluent's data platform and not the Apache versions. While
the page[1] lists the mapping to Apache versions, there might be more work to
get it working with actual apache versions of Kafka bits incase the delta
between them is problematic (which isn't clear).
[1]
https://docs.confluent.io/current/installation/versions-interoperability.html#interoperability-versions
> API to Generate Avro Schema of Phoenix Object
> ---------------------------------------------
>
> Key: PHOENIX-5443
> URL: https://issues.apache.org/jira/browse/PHOENIX-5443
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
>
> Based on an object name (such as a table or view) and an optional tenant_id
> and timestamp, we should be able to construct all the explicitly defined
> columns and data types of an object. (Obviously, we can't do this for dynamic
> columns.)
> From these fields, we should be able to construct a schema for the object and
> return it to the user. While this JIRA will focus on Avro, the output format
> should be pluggable so that other implementations could output to Thrift or
> Protobuf, and PHOENIX-4286 could use it to output as SQL CREATE statements.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
