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

Figure out serial representations of Engine Models #43

Open
kyprifog opened this issue Sep 11, 2020 · 1 comment
Open

Figure out serial representations of Engine Models #43

kyprifog opened this issue Sep 11, 2020 · 1 comment
Milestone

Comments

@kyprifog
Copy link
Collaborator

kyprifog commented Sep 11, 2020

I want a way for engine models to be serialized and passed between various programming languages (python -> scala for example) or libraries without having to depend on transpiling (like Jython).

Something like an avro or protobuf representation with client interpreters in each language.

python->python is easy (just libs with pypi), but handicaps the ability to scale beyond python ecosystem later on.

@kyprifog kyprifog added this to the Backlog milestone Sep 14, 2020
@kyprifog kyprifog changed the title Figure out serial representations of engines Figure out serial representations of Engine Models May 6, 2021
@kyprifog
Copy link
Collaborator Author

kyprifog commented May 6, 2021

In particular, this is important for job serialization . Right now things like credentials, table_name, etc are serialized and validated a second time in mason-spark which is not very graceful: https://github.com/samtecspg/mason-spark/blob/master/src/main/scala/configs/MergeConfig.scala

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