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

Extensible type system to support decimal, binary, JSON, and other custom types #121

Closed
frsyuki opened this Issue Mar 6, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@frsyuki
Contributor

frsyuki commented Mar 6, 2015

Just an idea for now. Necessary APIs for a custom type are:

  • Pass-through: a filter plugin should be able to pass-through input values to output plugins even if the filter plugin doesn't know the type.
  • to string: output plugins should be able to at least convert the value to string to store the value without loosing information even if the output plugin doesn't know the type.
  • parsing from a string: input plugins should be able to create the value from a string when user specify the type at config.yml file but input plugin doesn't specifically know how to create the type.
@frsyuki

This comment has been minimized.

Show comment
Hide comment
@frsyuki

frsyuki Mar 6, 2015

Contributor

Related: #120

Contributor

frsyuki commented Mar 6, 2015

Related: #120

@frsyuki

This comment has been minimized.

Show comment
Hide comment
@frsyuki

frsyuki Sep 15, 2015

Contributor

This is redesigned by #306.

Contributor

frsyuki commented Sep 15, 2015

This is redesigned by #306.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment