Hi, Xiangrui Meng. +1 for the proposal.
However, please update the following section for this vote. As we see, it seems to be inaccurate because today is Jan. 29th. (Almost February). (Since I cannot comment on the SPIP, I replied here.) Q7. How long will it take? - If accepted by the community by the end of December 2018, we predict to be feature complete by mid-end March, allowing for QA during April 2019, making the SPIP part of the next major Spark release (3.0, ETA May, 2019). Bests, Dongjoon. On Tue, Jan 29, 2019 at 8:52 AM Xiao Li <gatorsm...@gmail.com> wrote: > +1 > > Jules Damji <dmat...@comcast.net> 于2019年1月29日周二 上午8:14写道： > >> +1 (non-binding) >> (Heard their proposed tech-talk at Spark + A.I summit in London. Well >> attended & well received.) >> >> — >> Sent from my iPhone >> Pardon the dumb thumb typos :) >> >> On Jan 29, 2019, at 7:30 AM, Denny Lee <denny.g....@gmail.com> wrote: >> >> +1 >> >> yay - let's do it! >> >> On Tue, Jan 29, 2019 at 6:28 AM Xiangrui Meng <men...@gmail.com> wrote: >> >>> Hi all, >>> >>> I want to call for a vote of SPARK-25994 >>> <https://issues.apache.org/jira/browse/SPARK-25994>. It introduces a >>> new DataFrame-based component to Spark, which supports property graph >>> construction, Cypher queries, and graph algorithms. The proposal >>> <https://docs.google.com/document/d/1ljqVsAh2wxTZS8XqwDQgRT6i_mania3ffYSYpEgLx9k/edit> >>> was made available on user@ >>> <https://lists.apache.org/thread.html/269cbffb04a0fbfe2ec298c3e95f01c05b47b5a72838004d27b74169@%3Cuser.spark.apache.org%3E> >>> and dev@ >>> <https://lists.apache.org/thread.html/c4c9c9d31caa4a9be3dd99444e597b43f7cd2823e456be9f108e8193@%3Cdev.spark.apache.org%3E> >>> to >>> collect input. You can also find a sketch design doc attached to >>> SPARK-26028 <https://issues.apache.org/jira/browse/SPARK-26028>. >>> >>> The vote will be up for the next 72 hours. Please reply with your vote: >>> >>> +1: Yeah, let's go forward and implement the SPIP. >>> +0: Don't really care. >>> -1: I don't think this is a good idea because of the following technical >>> reasons. >>> >>> Best, >>> Xiangrui >>> >>
