[
https://issues.apache.org/jira/browse/SAMZA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318855#comment-14318855
]
Jay Kreps commented on SAMZA-390:
---------------------------------
WRT to the schema registry. Yeah we built and are about to open source a system
that we hope will be the default for this kind of thing. I think it is a bit
better than the existing github project which dates back to that AVRO patch
that has been floating around forever. The things that may be a bit better
include:
1. Can use Kafka for schema storage so no external database dependency
2. Support multi-dc operation
3. Has a single global id space so a message can be linked back to the registry
irrespective of the topic. This is required to support mixed schemas.
4. A better notion of compatibility
We intend to add a UI for this to browse your schemas and diff them between
versions to see what changed and really try to build out the full workflow for
people to interact with it.
We'd be interested in really making it work well for the Samza use case--I
think there may be a fair amount of metadata that is needed to really be an
effective catalog for streaming. We'd be happy to take on the related tickets
to help integrate it here. The plan is to release this middle of next week.
> High-Level Language for Samza
> -----------------------------
>
> Key: SAMZA-390
> URL: https://issues.apache.org/jira/browse/SAMZA-390
> Project: Samza
> Issue Type: New Feature
> Components: sql
> Reporter: Raul Castro Fernandez
> Priority: Minor
> Labels: project
> Attachments: StreamSQLforSAMZA-v0.1.docx.docx
>
>
> Discussion about high-level languages to define Samza queries. Queries are
> defined in this language and transformed to a dataflow graph where the nodes
> are Samza jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
