On Tue, Jan 8, 2019 at 12:15 AM Dave Fisher <dave2w...@comcast.net> wrote:
> Hi - > > Sent from my iPhone > > > On Jan 6, 2019, at 8:55 PM, Sijie Guo <guosi...@gmail.com> wrote: > > > > That’s a good suggestion. I also think that provides a better way to > > organize sub modules for now or even mid-term. > > > > However in long term, we should try to move out them out of Pulsar repo, > or > > even to push to corresponding computing engine repo. > > Are you suggesting that these be kept by the Pulsar project or donated to > the other projects? We could do either approaches - moving to a separate apache repo that managed by Pulsar PMC, or pushing the sub module to upstream projects. For SPE related integration, I am more in favor of pushing them to upstream projects (e.g. pushing pulsar-flink integration to flink). This would give Pulsar more exposures to other communities, and lead a closer collaboration between pulsar and other projects. Because the upstream projects have more experts on (helping) maintaining & improving those connectors. > > > This would 1) allow > > those modules having their own release schedules without interfering with > > pulsar core release, 2) allow more exposures or publicity of Pulsar if > they > > are pushed to the computing engine’s repo. E.g. pulsar-storm goes to > storm > > repo, pulsar-flink goes to flink repo and pulsar-spark goes to spark > repo. > > I think these connectors are a significant value to Pulsar and should > remain in Pulsar. Having separate releases for connectors might be an > advantage. > > Regards, > Dave > > > > > Hope this makes sense! > > > > Sijie > > > >> On Mon, Jan 7, 2019 at 1:43 PM Pingle Wang <1269223...@qq.com> wrote: > >> > >> sorry, the photo not show in content. The structure is as follows： > >> /pulsar > >> /pulsar-external > >> /pulsar-flink > >> /pulsar-spark > >> /pulsar-storm etc.. > >> > >> ------------------ 原始邮件 ------------------ > >> *发件人:* "Pingle Wang"<1269223...@qq.com>; > >> *发送时间:* 2019年1月7日(星期一) 中午12:38 > >> *收件人:* "dev"<dev@pulsar.apache.org>; > >> *主题:* 回复： [ANNOUNCE] Apache Pulsar > >> > >> like: > >> > >> > >> ------------------ 原始邮件 ------------------ > >> *发件人:* "Pingle Wang"<1269223...@qq.com>; > >> *发送时间:* 2019年1月7日(星期一) 中午12:36 > >> *收件人:* "dev"<dev@pulsar.apache.org>; > >> *主题:* 回复： [ANNOUNCE] Apache Pulsar > >> > >> Dear all: > >> when I PR found, we can have pulsar-external(sub-module) under > /pulsar, > >> as long-term, other computing engine can be rolled under > /pulsar-external > >> as well: > >> /pulsar-external |-- pulsar-flink |-- > >> pulsar-spark |-- pulsar-storm etc.. > >> > >> WDYT? > >> > >> > >> > >> > >> ------------------ 原始邮件 ------------------ > >> 发件人: "zhaijia03"<zhaiji...@gmail.com>; > >> 发送时间: 2019年1月4日(星期五) 上午8:12 > >> 收件人: "dev"<dev@pulsar.apache.org>; > >> 抄送: "users"<us...@pulsar.apache.org>; "announce"<annou...@apache.org>; > >> 主题: Re: [ANNOUNCE] Apache Pulsar 2.2.1 released > >> > >> > >> > >> cong~ > >> > >>> On Tue, Jan 1, 2019 at 5:14 AM Sijie Guo <si...@apache.org> wrote: > >>> > >>> 👍 congrats!🎉🎈 > >>> > >>> Thanks everyone for making this happen! > >>> > >>> Sijie > >>> > >>>> On Mon, Dec 31, 2018 at 12:37 PM Matteo Merli <mme...@apache.org> > wrote: > >>>> > >>>> The Apache Pulsar team is proud to announce Apache Pulsar version > >> 2.2.1. > >>>> > >>>> Pulsar is a highly scalable, low latency messaging platform running on > >>>> commodity hardware. It provides simple pub-sub semantics over topics, > >>>> guaranteed at-least-once delivery of messages, automatic cursor > >>> management > >>>> for > >>>> subscribers, and cross-datacenter replication. > >>>> > >>>> For Pulsar release details and downloads, visit: > >>>> > >>>> https://pulsar.apache.org/download > >>>> > >>>> Release Notes are at: > >>>> http://pulsar.apache.org/release-notes > >>>> > >>>> We would like to thank the contributors that made the release > possible. > >>>> > >>>> Regards, > >>>> > >>>> The Pulsar Team > >>>> > >>> > >> > >
