Re: Release Today/Tomorrow

It's a little more involved then i thought. We could do a release and then follow up with another one soon. On Mon, Feb 26, 2018 at 8:50 PM, Karthik Ramasamy wrote: > We can do a release. Chris wanted to get a PR in. Chris - any update? > > On Mon, Feb 26, 2018 at 11:38 PM

Re: Release Today/Tomorrow

+1 On Mon, Feb 26, 2018 at 8:38 PM, Jerry Peng wrote: > We haven't done a release in a while. Should we do a release today or > tomorrow? > > Best, > > Jerry >

Release Today/Tomorrow

We haven't done a release in a while. Should we do a release today or tomorrow? Best, Jerry

Re: Proposing Changes To Heron

Josh, Totally agree with your concern. I was bringing that idea into conversation and thought that as a back up solution. Since Heron is getting more and more popular, it would be really nice to have SQL support. I think having a built-in Heron SQL can shorten the development iteration since

Re: Proposing Changes To Heron

Thanks Josh for initiating this. It will be a great feature to add for Heron. cheers /karthik > On Feb 26, 2018, at 11:11 AM, Josh Fischer wrote: > > Jerry, > > Great point. Lets keep things simple for the migration to make sure the > implementation is correct. Then we

Re: Proposing Changes To Heron

Jerry, Great point. Lets keep things simple for the migration to make sure the implementation is correct. Then we can modify from there. On Sun, Feb 25, 2018 at 11:28 PM, Jerry Peng wrote: > Thanks Josh for taking the initiative to get this start! SQL on Heron >

Re: Proposing Changes To Heron

+1 for Heron SQL On Sun, Feb 25, 2018 at 9:28 PM, Jerry Peng wrote: > Thanks Josh for taking the initiative to get this start! SQL on Heron > will be a great feature! The plan sounds great to me. Lets first get > an initial version of the Heron SQL out and then we