You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an Odinson API user, I would like the configuration YAML structure to be standardized so that I can use it in my projects without having to go back to the code to find out where in the config tree a property is.
Also, as an Odinson API user, I would like the Odinson config structure to be represented as a POJO or case class to make it easier to use with distributed systems like Apache Flink and Apache Spark
Details:
I am thinking something similar to what we have done here. Even up to the point of just copying the classes out of that repository into this one.
Let me know what you think.
The text was updated successfully, but these errors were encountered:
As an Odinson API user, I would like the configuration YAML structure to be standardized so that I can use it in my projects without having to go back to the code to find out where in the config tree a property is.
Also, as an Odinson API user, I would like the Odinson config structure to be represented as a POJO or case class to make it easier to use with distributed systems like Apache Flink and Apache Spark
Details:
I am thinking something similar to what we have done here. Even up to the point of just copying the classes out of that repository into this one.
Let me know what you think.
The text was updated successfully, but these errors were encountered: