Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Pattern for more detailed types #437

Closed
2 tasks
rufuspollock opened this issue May 26, 2017 · 0 comments
Closed
2 tasks

Pattern for more detailed types #437

rufuspollock opened this issue May 26, 2017 · 0 comments

Comments

@rufuspollock
Copy link
Contributor

Many platforms/tools including SQL have a more detailed set of types (e.g. long integer) than Table Schema. This may be relevant for serialization and deserialization reliably. We have intentionally not included lots of types into Table Schema as it quickly gets complex (and you still don't support everyone).

What is proposed here is some standard pattern for adding additional information on types to Table Schema, esp a model of subtypes e.g. that something is a long integer cf #277 .

Tasks

  • Review existing important tools and their type lists e.g. SQL, Spark, BigQuery, ...
  • Develop the pattern

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants