Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Common: introduce the concept of an "origin" schema format to Iglu #181

Open
chuwy opened this issue Jul 28, 2016 · 0 comments
Open

Common: introduce the concept of an "origin" schema format to Iglu #181

chuwy opened this issue Jul 28, 2016 · 0 comments

Comments

@chuwy
Copy link
Contributor

chuwy commented Jul 28, 2016

What should be considered as master copy of Iglu registry?

We have two possible options:

  • Iglu registry is just original Schemas, all derived assets (like Redshift DDLs not derived from JSON Schemas) are secondary, thus can be generated automatically
  • Iglu registry is set of all Schemas it contains, no matter whether they're original or derived from other.

This question is really boils down to what we expect from derivation tools like igluctl static generate. If we expect them to be ideal, them we need to stick with first option, otherwise if human-interaction is unavoidable then we need to chose second option.

@alexanderdean alexanderdean changed the title Common: decide about master-copy of Iglu Common: introduce the concept of an "origin" schema format to Iglu Sep 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant