[
https://issues.apache.org/jira/browse/PHOENIX-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938610#comment-16938610
]
Josh Elser commented on PHOENIX-5443:
-------------------------------------
If you're thinking about hooking this up to other systems, I suspect you're
planning on making some API and providing some utility which can read that API
and serialize the object to Avro?
(if not, could I make levy the request to try to keep serialization libraries
out of external-facing API ;))
> 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)
