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

Support aliases for schema and field names #2

Open
machristie opened this issue Feb 1, 2023 · 1 comment
Open

Support aliases for schema and field names #2

machristie opened this issue Feb 1, 2023 · 1 comment

Comments

@machristie
Copy link
Contributor

To allow schema and field names to evolve without breaking API level SQL queries, the API should support adding aliases for schema and field names.

@machristie
Copy link
Contributor Author

Another idea that came up recently, we might want to support linking metadata schema fields. So for example, there might be two schemas that each define a field slightly differently but they both represent the same thing. One use for this would be to create a common metadata schema that links together the fields across more specific metadata schemas. Queries against the common metadata schema could then return results when matching fields in those more specific metadata schemas.

Essentially this comes down to a question of whether API users should define their own common metadata schema when metadata comes from multiple sources and then pre-process metadata to adhere to their common metadata schema. Or, they could leave the metadata as it is from each source and link together fields.

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