Closed bbrownz closed 8 years ago
@rkanter @rdblue This is the branch with the Kite specific oozie configuration alternative to #399
It looks like the Flume tests bombed out on an OOM on the Travis build, it looks like #398 hit something similar, maybe the travis setup needs some adjustments?
Yeah, don't worry about the Flume test failure. I'll restart it but I doubt it's related.
I made a few minor comments. Otherwise, that looks good to me. +1 after addressing them.
Updates for Roberts comments are covered in 7061b11. Thanks @rkanter!
@rdblue Did we have anything else we wanted to look at with this PR before it gets merged in?
@bbrownz, I think we're ready to go. I've just been a bit swamped lately.
@rdblue no worries, just checking in to make sure I wasn't missing anything
+1 for merging.
@rdblue or @tomwhite any objections to me merging this?
Nope, go for it!
https://issues.cloudera.org/browse/KITE-1035
Alternative implementation of the concept introduced first in pull #399
Sets the default configuration for kite to a list of configuration sources set at the property "oozie.service.KiteConfigurationService.kite.configuration"
(A consumer would also need to add the configuration service to the list of configurations specified for oozie under "oozie.services")