+1 Wishing that this goes to calcite too someday (hoping that it makes Beam side maintenance simpler)
On Tue, Aug 13, 2019 at 6:18 AM Manu Zhang <owenzhang1...@gmail.com> wrote: > > +1 > > On Tue, Aug 13, 2019 at 11:55 AM Mingmin Xu <mingm...@gmail.com> wrote: >> >> +1 >> >> On Mon, Aug 12, 2019 at 8:53 PM Ryan McDowell <ryanmcdow...@google.com> >> wrote: >>> >>> +1 >>> >>> On Mon, Aug 12, 2019 at 8:30 PM Reza Rokni <r...@google.com> wrote: >>>> >>>> +1 >>>> >>>> On Tue, 13 Aug 2019 at 09:28, Ahmet Altay <al...@google.com> wrote: >>>>> >>>>> +1 >>>>> >>>>> On Mon, Aug 12, 2019 at 6:27 PM Kenneth Knowles <k...@apache.org> wrote: >>>>>> >>>>>> +1 >>>>>> >>>>>> On Mon, Aug 12, 2019 at 4:43 PM Rui Wang <ruw...@google.com> wrote: >>>>>>> >>>>>>> Hi Community, >>>>>>> >>>>>>> I am using this separate thread to collect votes on contributing Beam >>>>>>> ZetaSQL(my way to say ZetaSQL as a dialect supported by BeamSQL) to >>>>>>> Beam repo. >>>>>>> >>>>>>> There are discussions related to benefits, technical design and others >>>>>>> on Beam ZetaSQL in [1]. The Beam ZetaSQL code lives in [2]. Note that >>>>>>> this vote is not about merging the PR, which should be decided by code >>>>>>> review. This vote is only to vote if Beam ZetaSQL should live in Beam >>>>>>> repo. >>>>>>> >>>>>>> +1: Beam repo can host Beam ZetaSQL >>>>>>> -1: Beam repo should not host Beam ZetaSQL >>>>>>> >>>>>>> If there are more questions related to Beam ZetaSQL, please discuss it >>>>>>> in [1]. >>>>>>> >>>>>>> [1]: >>>>>>> https://lists.apache.org/thread.html/eab70bb99218aaedfd506e979967379c0efa05ea56a792a1486f9c74@%3Cdev.beam.apache.org%3E >>>>>>> [2]: https://github.com/apache/beam/pull/9210 >>>>>>> >>>>>>> -Rui >>>> >>>> >>>> >>>> -- >>>> >>>> This email may be confidential and privileged. If you received this >>>> communication by mistake, please don't forward it to anyone else, please >>>> erase all copies and attachments, and please let me know that it has gone >>>> to the wrong person. >>>> >>>> The above terms reflect a potential business arrangement, are provided >>>> solely as a basis for further discussion, and are not intended to be and >>>> do not constitute a legally binding obligation. No legally binding >>>> obligations will be created, implied, or inferred until an agreement in >>>> final form is executed in writing by all parties involved. >> >> >> >> -- >> ---- >> Mingmin
