We didn’t really consider this when we designed Storm - Calcite integration. But the good news is that SqlFunctions is a smallish class with almost no dependencies. It, along with the rest of the org.apache.calcite.runtime package, could in principle be copied into Storm. (I’m not keen on creating a new calcite-runtime.jar but I could be persuaded if someone made a strong case.)
> On Aug 5, 2016, at 12:34 AM, Jungtaek Lim <[email protected]> wrote: > > Hi devs, > > I'm newbie of Calcite so I'd first say sorry for the ignorance if it's > newbie question. > > I'm working on Storm SQL which uses Calcite to compile SQL to topology. > Current implementation uses SqlFunctions to cover some operators so > calcite-core and transitive dependencies are needed even though compiled > topology in runtime. > > So I'd like to see what's preferred way of handling this. Is it common to > add calcite-core to dependency in runtime, or is it common for individual > projects to have their own similar classes? > > Thanks in advance, > Jungtaek Lim (HeartSaVioR)
