[
https://issues.apache.org/jira/browse/SAMZA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Riccomini updated SAMZA-40:
---------------------------------
Description:
Samza's configuration system has several problems that we need to resolved.
* Want to auto-generate documentation based off of configuration.
* Should support global defaults for a config property. Right now, we do
config.getFoo.getOrElse() everywhere.
* Should validate config up front, rather than thrown runtime exceptions
randomly throughout the code.
* We are mixing wiring and configuration together. How do other systems handle
this?
* We have fragmented configuration (anybody can define configuration). How do
other systems handle this?
* How to handle undefined configuration? How to make this interoperable with
both Java and Scala (i.e. should we support Option in Scala)?
* Should remain immutable.
* Should remove implicits. It's just confusing.
* Do we want to support complex types (list, map) for values, not just String?
We need a design proposal for this.
was:
Samza's configuration system has several problems that we need to resolve.
* Want to auto-generate documentation based off of configuration.
* Should support global defaults for a config property. Right now, we do
config.getFoo.getOrElse() everywhere.
* Should validate config up front, rather than thrown runtime exceptions
randomly throughout the code.
* We are mixing wiring and configuration together. How do other systems handle
this?
* We have fragmented configuration (anybody can define configuration). How do
other systems handle this?
* How to handle undefined configuration? How to make this interoperable with
both Java and Scala (i.e. should we support Option in Scala)?
* Should remain immutable.
* Should remove implicits. It's just confusing.
* Do we want to support complex types (list, map) for values, not just String?
We need a design proposal for this.
> Refactor Samza configuration
> ----------------------------
>
> Key: SAMZA-40
> URL: https://issues.apache.org/jira/browse/SAMZA-40
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
> Labels: project
>
> Samza's configuration system has several problems that we need to resolved.
> * Want to auto-generate documentation based off of configuration.
> * Should support global defaults for a config property. Right now, we do
> config.getFoo.getOrElse() everywhere.
> * Should validate config up front, rather than thrown runtime exceptions
> randomly throughout the code.
> * We are mixing wiring and configuration together. How do other systems
> handle this?
> * We have fragmented configuration (anybody can define configuration). How do
> other systems handle this?
> * How to handle undefined configuration? How to make this interoperable with
> both Java and Scala (i.e. should we support Option in Scala)?
> * Should remain immutable.
> * Should remove implicits. It's just confusing.
> * Do we want to support complex types (list, map) for values, not just String?
> We need a design proposal for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
