I just made a pull request for that. Alireza
On Wed, Jun 12, 2019 at 2:24 AM Ismaël Mejía <ieme...@gmail.com> wrote: > Can you please add this to the design documents webpage. > https://beam.apache.org/contribute/design-documents/ > > On Fri, Jun 7, 2019 at 10:44 PM Kenneth Knowles <k...@apache.org> wrote: > > > > Thanks for the doc. This is really clear and readable. It all looks like > a good improvement, whatever the result of the various open threads. And > nice bonus that you've pointed to more good reading material. > > > > Kenn > > > > On Fri, Jun 7, 2019 at 12:25 PM Alireza Samadian <asamad...@google.com> > wrote: > >> > >> Thank you so much. > >> > >> Best, > >> Alireza > >> > >> On Fri, Jun 7, 2019 at 11:48 AM Pablo Estrada <pabl...@google.com> > wrote: > >>> > >>> I've added you as a contributor! : ) > >>> > >>> On Fri, Jun 7, 2019 at 11:20 AM Alireza Samadian <asamad...@google.com> > wrote: > >>>> > >>>> Hi, > >>>> > >>>> I am going to create Issues in Jira and start implementing row > estimation of each source separately. I will appreciate if someone gives me > the permission to assign Jira Issues to myself. My Jira id is riazela. > >>>> > >>>> Best, > >>>> Alireza > >>>> > >>>> On Fri, May 31, 2019 at 3:54 PM Alireza Samadian < > asamad...@google.com> wrote: > >>>>> > >>>>> Dear Members of Apache Beam Dev List, > >>>>> > >>>>> My name is Alireza; I am a Software Engineer Intern at Google, and I > am working closely with Anton on Beam SQL query optimizer. Currently, it > uses Apache Calcite without any cost estimation; I am proposing to > implement the cost estimator for it. > >>>>> The first step would be implementing cost estimator for the sources; > this is my design proposal for this implementation. I will appreciate your > comments and suggestions. > >>>>> > >>>>> > https://docs.google.com/document/d/1vi1PBBu5IqSy-qZl1Gk-49CcANOpbNs1UAud6LnOaiY/edit#heading=h.6rlkpwwx7gvf > >>>>> > >>>>> Best, > >>>>> Alireza Samadian >
