Agree with Suneel and Ted; Let’s rise! Hmm, but that doesn’t seem to be the question. Still I agree
Ok I’ll read between the lines and assume you are voting for #1. Can we see if there is further agreement on ground rules because it’ll be hard to rise if we create a mess. 1) every change to the DSL should be implemented either in core-math or in _both_ engines, right? So every committer will have to be willing to take this on when changing the DSL, right? We don’t want divergence in DSL implementation. 2) are we going to allow the build to be broken for extended periods (hopefully only a day or two) until one or the other expert gets time to help with a DSL implementation? This is for cases where #1 is not possible. This will happen with both tests and abstract defs in core-math that are carried through other engine specific classes. The way to get things to compile may not be immediately obvious so to keep things going a profile or target for each engine might help. 3) This will create an instant split in what algos are implemented on h2o and spark. We should clearly mark these and ideally minimize them. 4) Users are going to be confused. Do they need to install Spark or not, what runs on what, what are the differences? The ideal is to say it all runs on both so all users have to do is choose their engine. But that may never happen. How do we handle this? There is coming confusion over Hadoop mr vs Spark, we don’t want to add to this. 5) Can we agree on file level formats and/or other ways to pass a parallelized drm from one engine to the other? This will allow us to create hybrid pipelines, potentially easing user confusion. On Jul 13, 2014, at 3:18 PM, Suneel Marthi <[email protected]> wrote: Agree with Ted. Let's rise. On Sun, Jul 13, 2014 at 6:10 PM, Ted Dunning <[email protected]> wrote: > On Sun, Jul 13, 2014 at 1:42 PM, Anand Avati <[email protected]> wrote: > >> I will accept the verdict of the vote no matter what it is. It is your >> project after all. >> > > I think we need to take Anand's words to heart here. > > We will rise together or fall apart. > > Let's rise. >
