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: make vendor behavior consistent #325

Open
4 tasks
chuwy opened this issue Jan 26, 2018 · 1 comment
Open
4 tasks

Common: make vendor behavior consistent #325

chuwy opened this issue Jan 26, 2018 · 1 comment

Comments

@chuwy
Copy link
Contributor

chuwy commented Jan 26, 2018

Several applications group schemas by vendor field, but there's two different behaviours.

  1. com.acme.marketing-schemas are subset of com.acme
  2. com.acme.marketing is independent of com.acme

I believe first behavior is correct. The whole point of vendor is to provide proper namespacing and namespacing assumes hierarchy.

  • Documentation
  • Scala Iglu Client
  • Scala Repo Server
  • (probably) Schema DDL
@alexanderdean
Copy link
Member

Can you be specific about what you mean by "behaviours" - what is done differently within these 3-4 applications based on differing treatments of the vendor field?

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

2 participants