[
https://issues.apache.org/jira/browse/PHOENIX-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924623#comment-16924623
]
Geoffrey Jacoby commented on PHOENIX-5443:
------------------------------------------
Some other logistical issues:
1. The Confluent libraries are Apache-licensed but they are not Apache-owned.
That means that any improvement / bug fix we would need to contribute upstream
to them would require signing their CLA, which may be a minor thing or might
not depending on its terms. (Haven't found their actual CLA doc yet -- seems to
be hidden behind a GitHub bot.)
2. The interfaces and REST APIs don't seem to have versioning guarantees
similar to our IA's. For example a recent change added a method to
SchemaRegistryClient, which required changing all existing implementations.
(See [here|https://github.com/confluentinc/schema-registry/pull/1196/files]).
If I'm reading it right, it also doesn't seem to have changed any version on
the REST API where a client could check if a server supported the new method,
unless I missed something.
3. Of course, if we ever need to change an interface, and convinced the
Confluent committers it was necessary, we would need to change their non-OSI
code server-side implementation as well as the Apache licensed interface and
our own Apache-licensed impls.
> 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.2#803003)
