Re: Podling S2graph Report Reminder - November 2019

[DO YUNG YOON]

Hi all.
Here is the draft for the report for November.

S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make the third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  * Not much activities.
  * There was a meetup with active committers and a mentor to discuss the
future of the project.
- The link what we have discussed:
https://markmail.org/message/igdjlveeptsnskoh

How has the project developed since the last report?

  * No issues has been resolved.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

* Our mentor is very helpful and responsive.

Signed-off-by:



On Mon, Nov 4, 2019 at 5:55 AM Justin Mclean  wrote:

> Hi,
>
> Just a friendly reminder that this is due in a couple of days and I don't
> see any progress on it. It's best to work on the report in the open before
> it is due.
>
> Thanks,
> Justin
>

Re: Sharing offline discourse with active committers (Was: Meet and chat in Seoul area?)

[DO YUNG YOON]

Thanks for sharing woonsan.

Here is what I thought thanks to this meeting.

1. There has not been much project / community activity for the last 1+
years.

I have been thought that the usability of this project can be improved if
the committers agree and pursue it.
I have been busy with operating S2Graph at kakao, not improving and
contributing for a while, but since I changed my work, I am available to
contributing again. As far as I remember, I pointed out the issues that we
opened, but never actually worked on, such as improving documentation and
API accessibility. I might reinvolve this project by starting on these
issues(of course others who interested are welcome).

2. Various ideas on how to improve developer's experience were spoken.

Personally, I have changed the works, and the new enviroment requires me to
work with spring boot and AWS RDS(postgre), instead of netty and HBase on
on-premise cloud at kakao. Now I have strong initiative for JDBC storage
backend, and also Java Client, so I think I can persue these new features
and we will see if it is beneficial.

On Wed, Oct 23, 2019 at 4:14 PM Woonsan Ko  wrote:

> And thank you so much, Do Yung, for inviting us to the delicious
> lunch! Also thanks to Daewon and
> Hwansung for coming far from the south and north in the metropolitan
> area during the day.
>
> Cheers,
>
> Woonsan
>
> On Wed, Oct 23, 2019 at 12:05 PM Woonsan Ko  wrote:
> >
> > Hi folks in S2Graph community,
> >
> > I had a chance to visit Seoul for two months, even better I met and
> > chatted with some active committers - Daewon Jeong, Do Yung Yoon and
> > Hwansung Yu - over lunch in a Chinese restaurant in Seoul yesterday.
> > We discussed informally how we can help grow our community as well as
> > personal interests. So, even if it was a very short talk for about 1.5
> > hr, I'd like to share a summary on what we discussed _informally_
> > regarding community development issues with other developers and users
> > in this community. I believe this is compliant with the "Open
> > Communications" policy [1] in the Apache Way. ;-)
> >
> > 1. There has not been much project / community activity for last 1+ year.
> > I also had a concern about the progress. However, after having
> > talks face-to-face with the active committers, I was able to
> > understand what they had to face in their $dayjobs, working  very hard
> > to successfully maintain a lot of S2Graph services in real sites
> > handling huge amount of traffics. They have tried to improve
> > documentation and API accessibility for new comers, just to give a few
> > examples, but it has been a struggle... Things seem to start changing.
> > They started reorganizing their work/time, and trying to find ways to
> > help new developers get involved more easily by improving the
> > developer experiences. Even if it looks slow-moving at this moment,
> > I'm personally confident with their passion as a mentor.
> >
> > 2. Various ideas on how to improve developer's experience were spoken.
> > For example, I personally mentioned that I tried to contribute
> > Swagger API documentation before but due to programming language
> > barrier - Scala which I had to start learning - it was very hard for
> > me to complete, adding "if it was Java, I could have been more
> > productive...". ;-) Daewon mentioned that they planned to provide a
> > Java client in the past and it is still something in their radar.
> > Also, I shared that Apache Jackrabbit has an option to run the JCR
> > server instance in-process residing in a web application, with an
> > alternative option to deploy the server instance in a separate process
> > to communicate with remotely. We may consider in the future that the
> > in-process option could be good to help developer's experience, too.
> > Like how developers feel confident and convenient nowadays with
> > spring-boot.
> >
> > 3. And we chatted on open source communities/cultures and business
> > models in general.
> > I don't think I can describe these properly as each topic was too
> > brief, scattered at random and it might sound a bit vague without
> > regional context information. Probably it's just worth mentioning that
> > we got better understandings on each by sharing same concerns and
> > information in these topics.
> >
> > All right. That's all I can recall. ;-)
> > Please feel free to add your thoughts in this thread if you have any
> > suggestions or insights.
> > I personally think this project has a unique value as the open source
> > graph database server in ASF. As the project artifacts have been used
> >

Re: Podling Report Reminder - August 2019

[DO YUNG YOON]

Hi Woonsan.

Thanks for reviewing it and just updated the wiki page.
- https://cwiki.apache.org/confluence/display/INCUBATOR/August2019#s2graph.

Regards.


On Fri, Aug 9, 2019 at 2:49 AM Woonsan Ko  wrote:

> Hi Do Yung,
>
> Could you update the wiki page as well?
> - https://cwiki.apache.org/confluence/display/INCUBATOR/August2019
>
> Regards,
>
> Woonsan
>
> On Wed, Aug 7, 2019 at 9:35 AM Woonsan Ko  wrote:
> >
> > Thanks, Do Yung!
> > I think it captures our status very well.
> >
> > Regards,
> >
> > Woonsan
> >
> > On Wed, Aug 7, 2019 at 8:39 AM DO YUNG YOON  wrote:
> > >
> > > Hi
> > >
> > > Here is my draft for the report. Apologies for being late. Please
> review
> > > this.
> > >
> > > S2Graph
> > >
> > > S2Graph is a distributed and scalable OLTP graph database built on
> Apache
> > > HBase to support fast traversal of extremely large graphs.
> > >
> > > S2Graph has been incubating since 2015-11-29.
> > >
> > > Three most important issues to address in the move towards graduation:
> > >
> > >   1. Make the third release.
> > >   2. Attract more users and contributors.
> > >   3. Build the developer community in both size and diversity.
> > >
> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> > > of?
> > >
> > >   None
> > >
> > > How has the community developed since the last report?
> > >
> > >   * There were some questions and answers from the community about how
> to
> > > getting started.
> > >   * New feature requests are opened on JIRA.
> > >
> > > How has the project developed since the last report?
> > >
> > >   * Providing OpenAPI documentation for REST API is pending since
> there was
> > > lack of discussion.
> > >   * It has been very quiet since the last report(only 1 JIRA issue
> opened).
> > >
> > > How would you assess the podling's maturity?
> > > Please feel free to add your own commentary.
> > >
> > >   [ ] Initial setup
> > >   [ ] Working towards first release
> > >   [X] Community building
> > >   [ ] Nearing graduation
> > >   [ ] Other:
> > >
> > > Date of last release:
> > >
> > >   2017-08-26
> > >
> > > When were the last committers or PPMC members elected?
> > >
> > > Have your mentors been helpful and responsive or are things falling
> > > through the cracks? In the latter case, please list any open issues
> > > that need to be addressed.
> > >
> > > * Our mentor is very helpful and responsive.
> > >
> > > Signed-off-by:
> > >
> > >
> > > On Wed, Aug 7, 2019 at 12:05 PM Justin Mclean 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > Just a friendly reminder that the report is due in a day. Is anyone
> > > > working on it?
> > > >
> > > > Thanks,
> > > > Justin
> > > >
>

Re: Podling Report Reminder - August 2019

[DO YUNG YOON]

Hi

Here is my draft for the report. Apologies for being late. Please review
this.

S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make the third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  * There were some questions and answers from the community about how to
getting started.
  * New feature requests are opened on JIRA.

How has the project developed since the last report?

  * Providing OpenAPI documentation for REST API is pending since there was
lack of discussion.
  * It has been very quiet since the last report(only 1 JIRA issue opened).

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

* Our mentor is very helpful and responsive.

Signed-off-by:


On Wed, Aug 7, 2019 at 12:05 PM Justin Mclean  wrote:

> Hi,
>
> Just a friendly reminder that the report is due in a day. Is anyone
> working on it?
>
> Thanks,
> Justin
>

Re: It's time to report! (Was: Podling report due)

[DO YUNG YOON]

Thanks for the review and I just updated the wiki page(
https://cwiki.apache.org/confluence/display/INCUBATOR/May2019).


On Fri, May 3, 2019 at 7:01 AM Woonsan Ko  wrote:

> It looks good to me. Would you also update the wiki page? Then I can
> sign it off.
>
> Thanks,
>
> Woonsan
>
> On Wed, May 1, 2019 at 4:17 AM DO YUNG YOON  wrote:
> >
> > Hi all.
> >
> > I just prepared the first version of the draft. Please review and let me
> > know what you think
> >
> >
> > S2Graph
> >
> > S2Graph is a distributed and scalable OLTP graph database built on Apache
> > HBase to support fast traversal of extremely large graphs.
> >
> > S2Graph has been incubating since 2015-11-29.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Make the third release.
> >   2. Attract more users and contributors.
> >   3. Build the developer community in both size and diversity.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> > of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >
> >   * There were some discussions on the documentation of the project.
> >   * There were some questions and answers from the community about the
> > migration tool
> >
> > How has the project developed since the last report?
> >
> >   * Working on providing OpenAPI documentation for REST API.
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2017-08-26
> >
> > When were the last committers or PPMC members elected?
> >
> > Have your mentors been helpful and responsive or are things falling
> > through the cracks? In the latter case, please list any open issues
> > that need to be addressed.
> >
> > * Our mentor is very helpful and responsive.
> >
> > Signed-off-by:
> >
> >
> > On Wed, May 1, 2019 at 10:19 AM Woonsan Ko  wrote:
> >
> > > Hi S2Graphe PPMC,
> > >
> > > Today May 1st is the expected due date to submit your podling project
> > > report.
> > >
> > > Just to repeat what Justin encouraged you folks several times already,
> > > - PPMC needs to submit the report until May 1st, in order to give all
> > > PPMC members and mentors enough time to review and discuss.
> > > - And all the PPMC reports are gathered and reviewed again by IPMC to
> > > submit to the board finally a week prior (May 8th) to the board
> > > meeting (on May 15th).
> > >
> > > Report submission (~May 1st) -> PPMC/Mentors/IPMC review (~May 8th) ->
> > > Board meeting (May 15th).
> > >
> > > If we delay it, IPMC won't have enough time to review and assess the
> > > status.
> > >
> > > So, could you draft and submit the report as soon as possible?
> > > Also, I encourage all PPMC members to review the report and discuss
> > > things if necessary.
> > >
> > > Kind regards,
> > >
> > > Woonsan
> > >
> > > -- Forwarded message -
> > > From: Justin Mclean 
> > > Date: Tue, Apr 30, 2019 at 8:44 PM
> > > Subject: Podling report due
> > > To: 
> > >
> > >
> > > Hi,
> > >
> > > Given the report date falls on the 1st this month we’re going to give
> > > codlings a couple of days (until Friday) to get them in.
> > >
> > > The report can be found here:
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
> > >
> > > We still have the following reports to be filled in:
> > > ECharts
> > > Edgent
> > > Milagro
> > > S2Graph
> > > SDAP
> > > Tamaya
> > > Toree
> > > Training
> > > Tuweni
> > >
> > > I can see that Training is working on a a report.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
>

Re: Swagger Doc and UI support (Was: Documentation to the official online site svn?)

[DO YUNG YOON]

Hi Woonsan.

Sorry for the late response. It took me for a while to figure out what
would be a nice way for working with OpenAPI document spec.

I agree with your two cents, especially the importance of generating rest
API reference through the right tool.

Here is the tools I played with a little bit.

- tapir: https://github.com/softwaremill/tapir
- endpoints: http://julienrf.github.io/endpoints/index.html

Personally, I prefer tapir, but it seems like it does not provide scala
2.11 available on maven central. I spent few days to upgrade scala version
from 2.11 to 2.12, but realize it is not that easy(we may need to open up a
separate discussion how we are going to upgrade scala version to 2.12).

so just played with endpoints at this point and just sharing it with you to
check if we are doing the right thing.

here is how to test this PR(
https://github.com/woonsan/incubator-s2graph/pull/1)

1. setup docker image on local for hbase.

cd dev_support; docker-compose up graph_hbase

2. run akka http server in dev environment.

sbt 'project s2http' '~reStart'

3. check the specs that generated by documentation server/spec.

http://localhost:8000/api-docs/documentation.json

4. check the AdminEndpoints

this is where our admin specs will reside on.
I added few more specs for listing service/label/serviceColumns etc to
validate if they are working.

ex)
- localhost:8000/admin/listServices
- localhost:8000/admin/listLabels
- localhost:8000/admin/listServiceColumns/s2graph

IMAO, The nice thing about the above two libraries is that it separates the
implementation and spec but still validate it on compile time, which I
prefer over the annotation approach.
I think it takes some time to get used to it for the first time, then after
struggling, the library shine and basically, help us to synchronize API and
doc so worth it.

Please review and give any comments.

On Wed, Apr 10, 2019 at 8:24 AM Woonsan Ko  wrote:

> On Mon, Apr 8, 2019 at 6:58 PM Woonsan Ko  wrote:
> >
> > Hi Daewon, Do Yung and/or anyone interested in,
> >
> > I've just submitted a PR which has the swagger UI support with the
> > default swagger document, initially for admin services:
> > - https://github.com/apache/incubator-s2graph/pull/197
> >
> > I think Swagger UI with the default swagger doc for the APIs will make
> > it easier for many devs.
> > Could you please review it?
> >
> > I figured out how to add /api-docs route there, but feel free to
> > correct it if I didn't follow any (Scala or Akka) best practices. ;-)
> >
> > As described in the PR description, the following operations work fine
> > with the examples:
> > - /admin/createService, /admin/createLabel, /admin/addIndex,
> > /admin/getLabel/{name}
> >
> > But, the following returns 404, for some reason which I can't figure out
> now:
> > - /admin/deleteLabel/{name}, /admin/addProp/{name},
> /admin/createServiceColumn
>
> I've pushed more and now those three are working fine.
> I've noticed that `/admin/deleteLabel/{name}` in documentation was
> changed to `/admin/deleteLabelReally/{name}` in code:
> -
> https://github.com/apache/incubator-s2graph/blob/master/s2http/src/main/scala/org/apache/s2graph/http/S2GraphAdminRoute.scala#L226
>
> There seems to be many in code outdating the documentation. For
> example, there are many undocumented operations too. e.g. renameLabel,
> copyLabel, swapLabel, etc.
>
> My two cents:
> If you folks like the OpenAPI (swagger) document and its UI, then I'd
> like to suggest you should keep the swagger doc as the single source
> of truth for internal/external developers who are using the APIs,
> always keeping it synchronized with the code. So, for example, if
> someone makes changes in the REST APIs, it must be affected in the
> OpenAPI (swagger) doc, too.
> And, consider generating rest api reference documentation through a
> tool like [1], and include or link those from the online
> documentation.
> Then you can minimize the risk of mismatch and outdated API references
> and confusing developers who want to use it.
>
> Regards,
>
> Woonsan
>
> [1]
> https://github.com/swagger-api/swagger-codegen#generating-static-html-api-documentation
>
> >
> > Kind regards,
> >
> > Woonsan
> >
> > On Thu, Mar 28, 2019 at 9:45 AM Woonsan Ko  wrote:
> > >
> > > On Thu, Mar 28, 2019 at 9:19 AM DO YUNG YOON  wrote:
> > > >
> > > > +1 for 'running' examples and would be happy to help if there is
> anything I
> > > > can help with.
> > > >
> > > > Also while I was going through the documentation to check if it is
> correct,
> > > > I found it is a bit tedious to copy payload on the doc to rest
> client(such
>

Re: It's time to report! (Was: Podling report due)

[DO YUNG YOON]

Hi all.

I just prepared the first version of the draft. Please review and let me
know what you think


S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make the third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  * There were some discussions on the documentation of the project.
  * There were some questions and answers from the community about the
migration tool

How has the project developed since the last report?

  * Working on providing OpenAPI documentation for REST API.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

* Our mentor is very helpful and responsive.

Signed-off-by:


On Wed, May 1, 2019 at 10:19 AM Woonsan Ko  wrote:

> Hi S2Graphe PPMC,
>
> Today May 1st is the expected due date to submit your podling project
> report.
>
> Just to repeat what Justin encouraged you folks several times already,
> - PPMC needs to submit the report until May 1st, in order to give all
> PPMC members and mentors enough time to review and discuss.
> - And all the PPMC reports are gathered and reviewed again by IPMC to
> submit to the board finally a week prior (May 8th) to the board
> meeting (on May 15th).
>
> Report submission (~May 1st) -> PPMC/Mentors/IPMC review (~May 8th) ->
> Board meeting (May 15th).
>
> If we delay it, IPMC won't have enough time to review and assess the
> status.
>
> So, could you draft and submit the report as soon as possible?
> Also, I encourage all PPMC members to review the report and discuss
> things if necessary.
>
> Kind regards,
>
> Woonsan
>
> -- Forwarded message -
> From: Justin Mclean 
> Date: Tue, Apr 30, 2019 at 8:44 PM
> Subject: Podling report due
> To: 
>
>
> Hi,
>
> Given the report date falls on the 1st this month we’re going to give
> codlings a couple of days (until Friday) to get them in.
>
> The report can be found here:
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
>
> We still have the following reports to be filled in:
> ECharts
> Edgent
> Milagro
> S2Graph
> SDAP
> Tamaya
> Toree
> Training
> Tuweni
>
> I can see that Training is working on a a report.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: Swagger Doc and UI support (Was: Documentation to the official online site svn?)

[DO YUNG YOON]

Hi Woonsan. Sorry for the late reply.

I really appreciate getting involved and I would love to review it.
I will read through the PR on this week, then ask any questions on this
thread.

Thanks for your contribution!

On Tue, Apr 9, 2019 at 7:58 AM Woonsan Ko  wrote:

> Hi Daewon, Do Yung and/or anyone interested in,
>
> I've just submitted a PR which has the swagger UI support with the
> default swagger document, initially for admin services:
> - https://github.com/apache/incubator-s2graph/pull/197
>
> I think Swagger UI with the default swagger doc for the APIs will make
> it easier for many devs.
> Could you please review it?
>
> I figured out how to add /api-docs route there, but feel free to
> correct it if I didn't follow any (Scala or Akka) best practices. ;-)
>
> As described in the PR description, the following operations work fine
> with the examples:
> - /admin/createService, /admin/createLabel, /admin/addIndex,
> /admin/getLabel/{name}
>
> But, the following returns 404, for some reason which I can't figure out
> now:
> - /admin/deleteLabel/{name}, /admin/addProp/{name},
> /admin/createServiceColumn
>
> Kind regards,
>
> Woonsan
>
> On Thu, Mar 28, 2019 at 9:45 AM Woonsan Ko  wrote:
> >
> > On Thu, Mar 28, 2019 at 9:19 AM DO YUNG YOON  wrote:
> > >
> > > +1 for 'running' examples and would be happy to help if there is
> anything I
> > > can help with.
> > >
> > > Also while I was going through the documentation to check if it is
> correct,
> > > I found it is a bit tedious to copy payload on the doc to rest
> client(such
> > > as postman).
> > > I wish there was a documentation tool integration, such as swagger,
> which
> > > also provides specs and UI to try each endpoint with examples.
> > > I think integration with documentation tools is good for not only for
> users
> > > but also developers who set up local development environments and fix
> code
> > > and testing.
> > >
> > > Any thoughts?
> >
> > +1
> > Great idea!
> > If we provide a swagger UI (e.g, http://localhost:8000/api-docs), it
> > will really boost developers understanding!
> > We can probably include swagger UI under the /api-docs endpoint with a
> > swagger.{json|yaml} file. I'm not accustomed to the scala web
> > framework, but if someone expose a simple index.html under the
> > /api-docs, then I can contribute or help create a pull request to
> > enable swagger UI.
> >
> > Cheers,
> >
> > Woonsan
> >
> > >
> > >
> > > On Thu, Mar 28, 2019 at 10:05 PM Woonsan Ko 
> wrote:
> > >
> > > > Wow, this is great!!!
> > > > Thank you very much.
> > > >
> > > > As a side note, I'll try to follow the documentation to implement
> > > > something simple -- by using S2Graph of course -- such as "Related
> > > > articles" or "Related products" which are really popular use cases in
> > > > most websites nowadays, but it's hard to implement actually in an
> > > > automated way based on users' behaviors.
> > > > If we have simple 'running' examples somewhere for normal web
> > > > developers, I think it would help people adopt this project and
> > > > solutions.
> > > >
> > > > Cheers,
> > > >
> > > > Woonsan
> > > >
> > > > On Thu, Mar 28, 2019 at 8:02 AM DO YUNG YOON 
> wrote:
> > > > >
> > > > > Hi Woonsan, Sorry for being late.
> > > > >
> > > > > I followed the instructions and the changes are now pushed to svn.
> > > > >
> > > > > Here is the updates
> > > > >
> > > > > - svn: https://svn.apache.org/repos/asf/incubator/s2graph/site
> (revision
> > > > > 1856470)
> > > > > - doc link on incubator site: *
> > > > https://s2graph.apache.org/docs/index.html
> > > > > <https://s2graph.apache.org/docs/index.html>*
> > > > >
> > > > > Please check the updates and feel free to comment
> > > > >
> > > > >
> > > > > On Tue, Mar 5, 2019 at 11:10 PM Woonsan Ko 
> wrote:
> > > > >
> > > > > > Thanks a lot, Do Yung, as always!
> > > > > > Please tell me if there's anything I can help with.
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Woonsan
> > > > > >
&

Re: Documentation to the official online site svn?

[DO YUNG YOON]

Hi Woonsan, Sorry for being late.

I followed the instructions and the changes are now pushed to svn.

Here is the updates

- svn: https://svn.apache.org/repos/asf/incubator/s2graph/site (revision
1856470)
- doc link on incubator site: *https://s2graph.apache.org/docs/index.html
<https://s2graph.apache.org/docs/index.html>*

Please check the updates and feel free to comment


On Tue, Mar 5, 2019 at 11:10 PM Woonsan Ko  wrote:

> Thanks a lot, Do Yung, as always!
> Please tell me if there's anything I can help with.
>
> Cheers,
>
> Woonsan
>
> On Tue, Mar 5, 2019 at 12:12 AM DO YUNG YOON  wrote:
> >
> > Hi Woonsan.
> >
> > I agree with your suggestion, and I am volunteering for this.
> > Let me try working on this on weekends then I will share any
> > questions/updates.
> >
> > Thanks for your suggestion.
> >
> >
> > On Tue, Mar 5, 2019 at 11:27 AM Woonsan Ko  wrote:
> >
> > > Hi folks,
> > >
> > > At the moment, the "Docs" link at the top menu bar [1] is linked to a
> > > non-ASF URL [2].
> > > I don't think we can keep the non-ASF pages there in the future.
> > > Furthermore, the documentation there is outdated from the
> > > documentation source at doc/.
> > >
> > > Our official documentation repository is the SVN [3], as of [4].
> > >
> > > Therefore, I'd like to propose the following:
> > > 1. Initially one of the committers should generate the site html from
> > > the doc/ in git source repo, following the instruction in
> > > doc/readme.md, until `make html`, which generates all the html and
> > > other static resource files at docs/build/html/. (I've just tested and
> > > it works fine.)
> > >And, the generated files at docs/build/html/** should be committed
> > > to a new directory, "docs", in [3].
> > > 2. Change the "Docs" menu link to "docs/index.html" from the external
> link.
> > > 3. From now on, whenever committers update documentation, once in a
> > > while, do the step 1 and 2 periodically, to synchronize the online
> > > site with the documentation source.
> > >
> > > When we really want to expand the community during the incubation
> > > period, the online documentation is really crucial: new comers start
> > > from there...
> > >
> > > Any thoughts?
> > > If this sounds okay, any volunteers?
> > >
> > > Regards,
> > >
> > > Woonsan
> > >
> > > [1] http://s2graph.incubator.apache.org/
> > > [2] https://steamshon.gitbooks.io/s2graph-book/content/
> > > [3] http://svn.apache.org/repos/asf/incubator/s2graph/site/
> > > [4] https://issues.apache.org/jira/browse/INFRA-11806
> > >
>

Re: Documentation to the official online site svn?

[DO YUNG YOON]

Hi Woonsan.

I agree with your suggestion, and I am volunteering for this.
Let me try working on this on weekends then I will share any
questions/updates.

Thanks for your suggestion.


On Tue, Mar 5, 2019 at 11:27 AM Woonsan Ko  wrote:

> Hi folks,
>
> At the moment, the "Docs" link at the top menu bar [1] is linked to a
> non-ASF URL [2].
> I don't think we can keep the non-ASF pages there in the future.
> Furthermore, the documentation there is outdated from the
> documentation source at doc/.
>
> Our official documentation repository is the SVN [3], as of [4].
>
> Therefore, I'd like to propose the following:
> 1. Initially one of the committers should generate the site html from
> the doc/ in git source repo, following the instruction in
> doc/readme.md, until `make html`, which generates all the html and
> other static resource files at docs/build/html/. (I've just tested and
> it works fine.)
>And, the generated files at docs/build/html/** should be committed
> to a new directory, "docs", in [3].
> 2. Change the "Docs" menu link to "docs/index.html" from the external link.
> 3. From now on, whenever committers update documentation, once in a
> while, do the step 1 and 2 periodically, to synchronize the online
> site with the documentation source.
>
> When we really want to expand the community during the incubation
> period, the online documentation is really crucial: new comers start
> from there...
>
> Any thoughts?
> If this sounds okay, any volunteers?
>
> Regards,
>
> Woonsan
>
> [1] http://s2graph.incubator.apache.org/
> [2] https://steamshon.gitbooks.io/s2graph-book/content/
> [3] http://svn.apache.org/repos/asf/incubator/s2graph/site/
> [4] https://issues.apache.org/jira/browse/INFRA-11806
>

Re: Podling Report Reminder - February 2019

[DO YUNG YOON]

Thanks for quick response Woonsan.

I updated wiki(https://wiki.apache.org/incubator/February2019) as
you suggested.

Here is the copy of updates(same as wiki).


S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make the third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

  None

How has the community developed since the last report?

  * Adding two committer.
  * One more mentor has joined.
  * There were some questions and answers from the community about the
deployment of
S2Graph.

How has the project developed since the last report?

  * We are overhauling documentation(S2GRAPH-246)
- Integrate gitbook into the project.
  * New HTTP interface integration(S2GRAPH-248)

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

* 2018-12: Jong Wook Kim
* 2018-12: Hyunsung Jo

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

* Our mentor is very helpful and responsive.

Signed-off-by:

  [ ](s2graph) Sergio Fernández
 Comments:
  [ ](s2graph) Woonsan Ko
 Comments:

On Tue, Feb 5, 2019 at 9:59 AM Woonsan Ko  wrote:

> Hi Do Yung,
>
> Thanks for the draft and sharing it here.
>
> On Mon, Feb 4, 2019 at 6:41 PM DO YUNG YOON  wrote:
> >
> > Hi folks. Here is the draft of Feb Report.
> > Please review and give feedback and I will update it on wiki tonight.
> >
> >
> > S2Graph
> >
> > S2Graph is a distributed and scalable OLTP graph database built on Apache
> > HBase to support fast traversal of extremely large graphs.
> >
> > S2Graph has been incubating since 2015-11-29.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Make a third release.
> >   2. Attract more users and contributors.
> >   3. Build the developer community in both size and diversity.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> beaware
> > of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >   * Adding two committer.
> >   * One more mentor has joined.
> >   * There were some questions from the community about the deployment of
> > S2Graph.
>
> ... questions and answers ... ;-)
>
> >
> > How has the project developed since the last report?
> >
> >   * We are overhauling documentation(S2GRAPH-246)
> > - Integrate gitbook into project.
> >   * New HTTP interface integration(S2GRAPH-248)
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2017-08-26
> >
> > When were the last committers or PPMC members elected?
>
> Could you add the dates and names for the new committers here?
> Find an example in the Tamaya podling report [1].
>
> [1] https://wiki.apache.org/incubator/February2019
>
> >
> >   None
>
> Also, below this, could you add "Have your mentors been helpful and
> responsive ..." question and answer as well? See Tamaya as an example.
>
> The other things look good to me.
>
> Thanks,
>
> Woonsan
>
> >
> > Signed-off-by:
> >
> >   [ ](s2graph) Andrew Purtell
> >  Comments:
> >   [ ](s2graph) Seetharam Venkatesh
> >  Comments:
> >   [ ](s2graph) Sergio Fernández
> >  Comments:
> >   [ ](s2graph) Woonsan Ko
> >  Comments:
> >
> > On Sat, Jan 26, 2019 at 5:17 AM  wrote:
> >
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 20 February 2019, 10:30 am PDT.
> > > The report for your podling will form a part of t

Re: Podling Report Reminder - February 2019

[DO YUNG YOON]

Hi folks. Here is the draft of Feb Report.
Please review and give feedback and I will update it on wiki tonight.


S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to beaware
of?

  None

How has the community developed since the last report?
  * Adding two committer.
  * One more mentor has joined.
  * There were some questions from the community about the deployment of
S2Graph.

How has the project developed since the last report?

  * We are overhauling documentation(S2GRAPH-246)
- Integrate gitbook into project.
  * New HTTP interface integration(S2GRAPH-248)

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [ ](s2graph) Sergio Fernández
 Comments:
  [ ](s2graph) Woonsan Ko
 Comments:

On Sat, Jan 26, 2019 at 5:17 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 February 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, February 06).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/February2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

[DISCUSS]: implementation of meta storage(schema)

[DO YUNG YOON]

Hi folks.

I want to discuss the current implementation of meta storage(schema).

The roles of the schema in S2Graph are following.

1. When it accepts write request that is represented by logical
vertex/edge, it uses schema to build a physical internal representation,
which is specific to storage backend. Also, the schema is used to validate
the request.

2. When a query comes in, it uses schema to build physical request, which
is specific to storage backend, then it uses schema to transform physical
representation to logical vertex/edge.

Current implementation assumes that the schema is very small, compared to
actual vertex/edge data. since it read schema a lot so it is important to
build a correct index that supports O(1) for schema is crucial, so it uses
a local cache to increase performance.

The problem with current implementation is that it is impossible to inject
a different implementation of schema since implementations are too tightly
coupled.

In s2jobs, S2GraphSource/S2GraphSink use S2Graph instance to
serialize/deserialize data from HFile, and there is no way to avoid
accessing meta database for schema on each spark executor(details on
https://issues.apache.org/jira/browse/S2GRAPH-252). In this case, a static
schema can be built on spark driver via reading the file or read meta
database or whatever, then broadcast static schema on every spark executor.

In general, I believe what we need is the way to inject a different
implementation of a schema. Currently S2Graph only have the implementation
using meta database with local cache, but it would be great if the
implementation of the schema is abstracted, and finally, a different
implementation can be injected when we create S2Graph instance.

To achieve this, I believe abstracting the necessary methods in one
interface is a good start, so here I collected most of the methods that are
related to the schema.

I suggest to add SchemaManager interface, then refactor current code base
to use this interface to access schema.

I want to discuss if this is the right way and if we need to work on this
first since it will affect lots of codes.

Please feel free to comment.

Here is the draft of the interface.

https://docs.google.com/document/d/134zPVm8vtXMRKC77bsVorp_06zZhU9hk2rQIKXH6HpI/edit?usp=sharing

Re: [DISCUSS]: asking about future of s2graph

[DO YUNG YOON]

Sorry for being late for reading this and Really Appreciate your opinion
Woonsan.

> Write blogs with compelling stories for potential active users who need
to live on this technology, potentially with runnable GitHub project(s) for
readers Stories with real use cases attract people as their lives can rely
on those. It could make them active users at least.

I would love to contribute to writing blogs, and runnable GitHub projects.
I tried few times to share the user stories from Kakao, but I think we are
open to any topics regarding S2Graph. Not sure how to start the blogs(I
guess we need to discuss what topics we cover), but count me in.

> Make more noise through Kakao, Twitter, Facebook, ... I have been a
non-social-web guy, but I have written blog articles for Apache Jackrabbit,
etc. JMeter twitts often to broadcast community activities. It works.

I am not an active user on the social things so not sure how to working on
this. Maybe more social people can help us. we can try this when we have
some activities to broadcast such as release, adding the cool feature,
writing blogs so on.

> If necessary or useful, consider writing those in Korean for local
communities, even in users@ mailing list. As long as you keep deciding
together in devs@, it's no problem.

Actually, didn't know this. Would be helpful if we need to explain in
details for users who are not comfortable with English. Mixing up with the
first suggestion, I am wondering writing blogs in Korean is ok, since I
think it can help lowering the bar to local users.

> Try to leverage your company's marketing department's power. They might
be eager to leverage you as an Apache community leaders for their reasons,
too. It could be a win-win. For example, I always try to secure my tech
session(s) about Apache Jackrabbit and related topics in my company's
annual conference, making deals with the marketing dept.

Not sure if my company can support this, but worth to ask so let me ask
them.

I hope we can further discuss how and what for blogs.


On Thu, Nov 22, 2018 at 7:36 AM Woonsan Ko  wrote:

> Hi Do Yung,
>
> Thank you very much for the clear explanation.
> I've recently applied for a mentor for this project, so I'm reading past
> messages to understand the context now. ;-)
> Please see my comments inline.
>
> On 2018/10/31 06:56:15, DO YUNG YOON  wrote:
> > It's been almost 3 years since s2graph has entered apache incubating. Our
> > community has not been successful to reach more people so far and I think
> > failing on growing community is the blocker issue for s2graph to
> graduate.
> >
> > I want to open up the discussion about what we have to do for growing
> > community, and eventually for graduation.
> >
> > In my opinion, there are many parts have been changed after incubation.
> >
> > Followings are notable improvements we have been working on.
> >
> > 1. Query Interface
> >
> > - Tinkerpop OLTP support
> > - GraphQL support
> >
> > 2. Storage
> >
> > - Embedded RocksDB
> > - JDBC Storage
> >
> > 3. Full-text search
> >
> > - ElasticSearch for search on vertex/edge property
> >
> > 4. OLAP
> >
> > - S2GraphSource: dump HFile then creates Spark dataframe.
> > - S2GraphSink: sink Spark dataframe to S2Graph.
> >
> > Even though the project has been improved, our community has not been
> > grown.
> >
> > There could be many reasons that our community is not growing(please list
> > them so we can discuss if we can resolve them), but in my humble opinion,
> > we have not even released above improvements since the last release.
> >
> > As far as I remember, the last time we discuss the release was a long
> time
> > ago(2017-09-08) at here
> >
> https://lists.apache.org/thread.html/d0d8e264b7625128a6c2832723cf2ad555d169f9f277086ce69c3a7b@%3Cdev.s2graph.apache.org%3E
> > .
> >
> > Back then I was under pressure that we need to show that our community
> > growing after release, and since I was not sure, I avoid talking about
> the
> > release, and rather keep working on issues.
> >
> > Now I think it is much better to start by releasing it rather than only
> > just wondering how to grow the community.
> >
> > To grow the community, the very basic way I know is to keep improving the
> > project, releasing it, and advertise it, and get user feedback, and I
> think
> > we stuck to step 1 for too long time.
>
> My two cents:
>
> From my experiences, it's really about selling your technology to people.
> We might want to be focused on marketing a little bit more. Possible
> marketing activities for community growth are in my mind:
> - Write blogs with compelling s

Re: [jira] [Commented] (S2GRAPH-248) HTTP interface integration.

[DO YUNG YOON]

No problem deawon, I will work on S2GRAPH-249 based on your commit.

Just quick questions, I guess you mention 4 high-level functionalities.

1. write
2. read
3. admin
4. graphql

It seems like you intend to migrate s2graphql also into this new subproject
s2http, so just quick question, are we going to deprecate s2graphql
subproject?

On Mon, Nov 26, 2018 at 5:38 PM daewon  wrote:

> [S2GRAPH-248] I made the first commit for the issue.
>
> Link: https://github.com/daewon/incubator-s2graph/tree/S2GRAPH-248/s2http
>
> I chose `akka http` because it was stable and lightweight with the`
> framework` for `http layer`.
> The initial implementation focused on minimizing external dependencies and
> allowing the separate logically separate functions `write, read, admin,
> graphql`.
>
> To do this, I chose to define logically separated `route` functions as each
> `Trait` S2GraphAdminRoute | S2GraphTraversalRoute. (Please comment if you
> have any opinions)
>
> An example implementation of functionality is `getEdges, experiments`, etc.
> in` S2GraphTraversalRoute`.
>
> The `/graphs/*` APIs are implemented to be branched from the existing
> restHandler.
> Implement it first by delegating that function.
>
> ```
> // expose routes in `S2GraphTraversalRoute` Trait
> lazy val traversalRoute: Route =
>   post {
> concat(
>   delegated // getEdges, experiments, etc.
> )
>   }
> ```
>
> An example implementation of functionality is `get / create Label /
> Service` in `S2GraphAdminRoute`.
>
> ```
> // expose routes in `S2GraphAdminRoute` Trait
> lazy val adminRoute: Route =
>   get {
> concat(
>   getService,
>   getLabel
> )
>   } ~ post {
> concat(
>   createService,
>   createLabel
> )
>   }
> ```
>
> There is a brief description in README.md about running the server and
> testing its functionality.
>
> I think the rest of the functions will be created by creating each issue.
>
> @DOYUNG `https://issues.apache.org/jira/browse/S2GRAPH-249`
>  It seems to be
> related to the issue.
>
>
> 2018년 11월 23일 (금) 오후 2:18, Daewon Jeong (JIRA) 님이 작성:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/S2GRAPH-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696384#comment-16696384
> > ]
> >
> > Daewon Jeong commented on S2GRAPH-248:
> > --
> >
> > [~steamshon] Thank you for your feedback.
> >
> > I will quickly build a basic project that will be the base for HTTP
> > integration task.
> >
> > > HTTP interface integration.
> > > ---
> > >
> > > Key: S2GRAPH-248
> > > URL: https://issues.apache.org/jira/browse/S2GRAPH-248
> > > Project: S2Graph
> > >  Issue Type: Task
> > >  Components: s2core, s2rest_netty, s2rest_play
> > >Reporter: Daewon Jeong
> > >Priority: Minor
> > >
> > > The current HTTP interface in S2Graph has the following problems.
> > >  known issues:
> > >1. The `s2rest_netty` project is experimental and supports only
> > `graph traverse` API.
> > >2. `s2rest_play` based on Play! Framework.
> > >   - Play! Framework is full stack framework, so it has a lot of
> > dependencies that s2graph does not need.
> > >   - There is also a conflict with byte buddy for patching
> asynchbase.
> > >3. `GraphQL` is still in the experimental phase and does not yet
> > provide all the functionality.
> > > The discussion below is written on the link below.
> > > discussions: [
> >
> https://lists.apache.org/thread.html/56379268a12ed5e64a2d7497a8741b09cdf2194bf7a3c303000420b6@%3Cdev.s2graph.apache.org%3E
> > ]
> > >
> > > Based on this issue, the following work should be done.
> > >  * Create an HTTP interface project(without play!)
> > >  * Remove s2rest_netty
> > >  * API documentation (GraphQL, Rest)
> > >  * GraphQL and Rest HTTP interface integration
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> >
>

Re: HTTP interface integration and unfinished project (s2rest_netty) removal.

[DO YUNG YOON]

Thanks, daewon. I will follow this on JIRA.

On Thu, Nov 22, 2018 at 3:33 PM daewon  wrote:

> I created an issue <https://issues.apache.org/jira/browse/S2GRAPH-248> for
> this discussion.
> I think we will make the decisions in JIRA and start working on them.
>
>
> 2018년 11월 22일 (목) 오후 2:00, DO YUNG YOON 님이 작성:
>
> > Thanks for getting involved in the discussion Woonsan.
> >
> > @deawon, can you please create the Jira issue for this?
> >
> > By the way, I merged S2GRAPH-246(integration of documents into S2Graph
> > project) into master yesterday, so I think we are ready to work on this.
> > What if we move the APIs one by one and document them together?
> >
> > Since we have to go through the full list of APIs, I think it is a good
> > time to document them also.
> >
> >
> >
> >
> >
> > On Thu, Nov 22, 2018 at 6:10 AM Woonsan Ko  wrote:
> >
> > > Now I see why it was broken. ;-)
> > > I recently re-subscribed the lists and started reading past messages to
> > > understand the context.
> > > I'm very looking forward to seeing the progress!
> > >
> > > Cheers,
> > >
> > > Woonsan
> > >
> > > On 2018/11/07 07:51:20, daewon  wrote:
> > > > I've looked at the features that are available to remove the Play!
> > > > Framework.
> > > >
> > > > I have written my comments for each function groups.
> > > >
> > > > - The Admin and Create APIs have yet to integrate many functions into
> > the
> > > > Play! controller code, so code separation must be preceded in order
> to
> > > move
> > > > functionality.
> > > > - The API with the `withWait` postfix of the Edge/Vertex creation API
> > is
> > > an
> > > > API that tells the client whether the request is applied correctly.
> > > >This is a duplicate API that exists for backward compatibility.
> > > > - Management routes are suggested to unify API routes with prefixes
> > such
> > > as
> > > > `/admin/?` or `/managment/?`.
> > > > - Server health_check or Counter related features are not available
> > > > anymore, so I suggest you exclude them.
> > > >
> > > > ## Edge creation
> > > >   ### List of APIs to leave
> > > > POST/graphs/edges/insert
> > > >
> > > > POST/graphs/edges/insertBulk
> > > > POST/graphs/edges/delete
> > > >
> > > > POST/graphs/edges/deleteAll
> > > >
> > > > POST/graphs/edges/deleteAllWithOutWait
> > > >
> > > > POST/graphs/edges/update
> > > >
> > > > POST/graphs/edges/increment
> > > > POST/graphs/edges/incrementCount
> > > > POST/graphs/edges/bulk
> > > >
> > > >   ### List of APIs that should be removed
> > > > POST/graphs/edges/deleteWithWait
> > > >
> > > > POST/graphs/edges/updateWithWait
> > > >
> > > > POST/graphs/edges/incrementWithWait
> > > >
> > > > POST/graphs/edges/bulkWithWait
> > > >
> > > > POST/graphs/edges/insertWithWait
> > > >
> > > >
> > > > ## Edge query
> > > >
> > > >   ### List of APIs to leave
> > > > POST/graphs/getEdges
> > > >
> > > > POST/graphs/checkEdges
> > > >
> > > >
> > > >   ### List of APIs that should be removed
> > > > POST/graphs/getEdgesGrouped
> > > >
> > > > POST/graphs/getEdgesGroupedExcluded
> > > >
> > > > POST/graphs/getEdgesGroupedExcludedFormatted
> > > >
> > > > GET /graphs/getEdge/:srcId/:tgtId/:labelName/:direction
> > > >
> > > > POST/graphs/getEdgesExcluded
> > > >
> > > > POST/graphs/getEdgesExcluded/grouped
> > > >
> > > > POST/graphs/getEdges/grouped
> > > >
> > > >
> > > >
> > > > ## Vertex related
> > > >   ### List of APIs to leave
> > > > POST/graphs/getVertices
> > > > POST/graphs/vertices/insert
> > > > POST/graphs/

Re: HTTP interface integration and unfinished project (s2rest_netty) removal.

[DO YUNG YOON]

Thanks for getting involved in the discussion Woonsan.

@deawon, can you please create the Jira issue for this?

By the way, I merged S2GRAPH-246(integration of documents into S2Graph
project) into master yesterday, so I think we are ready to work on this.
What if we move the APIs one by one and document them together?

Since we have to go through the full list of APIs, I think it is a good
time to document them also.





On Thu, Nov 22, 2018 at 6:10 AM Woonsan Ko  wrote:

> Now I see why it was broken. ;-)
> I recently re-subscribed the lists and started reading past messages to
> understand the context.
> I'm very looking forward to seeing the progress!
>
> Cheers,
>
> Woonsan
>
> On 2018/11/07 07:51:20, daewon  wrote:
> > I've looked at the features that are available to remove the Play!
> > Framework.
> >
> > I have written my comments for each function groups.
> >
> > - The Admin and Create APIs have yet to integrate many functions into the
> > Play! controller code, so code separation must be preceded in order to
> move
> > functionality.
> > - The API with the `withWait` postfix of the Edge/Vertex creation API is
> an
> > API that tells the client whether the request is applied correctly.
> >This is a duplicate API that exists for backward compatibility.
> > - Management routes are suggested to unify API routes with prefixes such
> as
> > `/admin/?` or `/managment/?`.
> > - Server health_check or Counter related features are not available
> > anymore, so I suggest you exclude them.
> >
> > ## Edge creation
> >   ### List of APIs to leave
> > POST/graphs/edges/insert
> >
> > POST/graphs/edges/insertBulk
> > POST/graphs/edges/delete
> >
> > POST/graphs/edges/deleteAll
> >
> > POST/graphs/edges/deleteAllWithOutWait
> >
> > POST/graphs/edges/update
> >
> > POST/graphs/edges/increment
> > POST/graphs/edges/incrementCount
> > POST/graphs/edges/bulk
> >
> >   ### List of APIs that should be removed
> > POST/graphs/edges/deleteWithWait
> >
> > POST/graphs/edges/updateWithWait
> >
> > POST/graphs/edges/incrementWithWait
> >
> > POST/graphs/edges/bulkWithWait
> >
> > POST/graphs/edges/insertWithWait
> >
> >
> > ## Edge query
> >
> >   ### List of APIs to leave
> > POST/graphs/getEdges
> >
> > POST/graphs/checkEdges
> >
> >
> >   ### List of APIs that should be removed
> > POST/graphs/getEdgesGrouped
> >
> > POST/graphs/getEdgesGroupedExcluded
> >
> > POST/graphs/getEdgesGroupedExcludedFormatted
> >
> > GET /graphs/getEdge/:srcId/:tgtId/:labelName/:direction
> >
> > POST/graphs/getEdgesExcluded
> >
> > POST/graphs/getEdgesExcluded/grouped
> >
> > POST/graphs/getEdges/grouped
> >
> >
> >
> > ## Vertex related
> >   ### List of APIs to leave
> > POST/graphs/getVertices
> > POST/graphs/vertices/insert
> > POST/graphs/vertices/delete
> > POST/graphs/vertices/deleteAll
> >
> >   ### List of APIs that should be removed
> > POST/graphs/vertices/insert/:serviceName/:columnName
> > POST/graphs/vertices/delete/:serviceName/:columnName
> >
> > POST/graphs/vertices/deleteAll/:serviceName/:columnName
> >
> > POST/graphs/vertices/insertWithWait
> >
> > POST/graphs/vertices/deleteWithWait
> >
> >
> > ## Vertex related
> >   ### List of APIs to leave
> > POST/graphs/createService
> >
> > GET /graphs/getService/:serviceName
> >
> > GET /graphs/getLabels/:serviceName
> >
> > POST/graphs/createLabel
> >
> > POST/graphs/addIndex
> >
> > GET /graphs/getLabel/:labelName
> >
> > PUT /graphs/deleteLabelReally/:labelName
> >
> > POST/graphs/addProp/:labelName
> >
> > POST/graphs/createServiceColumn
> >
> > PUT /graphs/deleteServiceColumn/:serviceName/:columnName
> >
> > POST/graphs/addServiceColumnProp/:serviceName/:columnName
> >
> > POST/graphs/addServiceColumnProps/:serviceName/:columnName
> >
> > GET /graphs/getServiceColumn/:serviceName/:columnName
> >
> > POST/graphs/createHTable
> >
> > GET /admin/labels/:serviceName
> >
> > POST/graphs/copyLabel/:oldLabelName/:newLabelName
> >
> > POST/graphs/renameLabel/:oldLabelName/:newLabelName
> >
> > POST/graphs/swapLabels/:leftLabelName/:rightLabelName
> >
> > POST/graphs/updateHTable/:labelName/:newHTableName
> >
> > PUT /graphs/loadCache
> >
> >
> > ## Experiment related
> >   ### List of API to leave
> > POST/graphs/experiment/:accessToken/:experimentName/:uuid
> >
> > POST/graphs/experiments
> >
> >
> > ## publish (deprecated)
> >   ### List 

Re: Operating s2graph in a Cloud enviroment

[DO YUNG YOON]

Just sharing the updates.

I made the WIP version for google datastore on
https://github.com/SteamShon/incubator-s2graph/tree/datastore.
To test this please reference on DatastoreStorageTest.

I tested it only on my local environment as follow.

1. startup local datastore HTTP server using emulators.

gcloud beta emulators datastore start --host-port localhost:8080
--consistency 1.0 --project async-test --data-dir project-test

2. checkout above branch.

3. startup s2graphql server using following options.

sbt -DschemaCacheTTL=-1 -Dhttp.port=8000 -DenableMutation=true
-Ds2graph.storage.backend=datastore  -Ddatastore.host="http://localhost:8080;
-Ddatastore.dataset=async-test -Ddatastore.version=v1beta3
-Ddatastore.namespace=test 'project s2graphql' '~re-start'

then you can follow up
https://github.com/apache/incubator-s2graph/tree/master/s2graphql

If anyone with interest and time, please review. I would appreciate any
feedback.


On Sat, Nov 3, 2018 at 7:24 AM DO YUNG YOON  wrote:

> Hi Hwansung.
>
> I think implementing DatastoreFetcher/DatastoreMutator,
> DynamoDBFetcher/DynamoDBMutator class which implement our Fetcher/Mutator
> interface will help you to work with data in that storage.
>
> The purpose of exposing Fetcher/Mutator interface is for others to
> implement in their way to work with their storage, only focusing on how to
> fetch vertex/edge from storage when the S2Query is given, and how to store
> vertex/edge to storage when S2Edge/S2Vertex are given.
>
> Also if you are deploying s2graph rest on the public cloud, then we can
> provide docker image for s2graph rest(not sure if we are already providing
> it, let me check it out).
>
> I have very little experience on the public cloud, such as GCP and AWS, so
> I might think the wrong direction. I guess we can list what are the
> necessary parts, then create issues regarding it.
>
> Please feel free to advise on my comments.
>
> On Fri, Nov 2, 2018 at 10:09 AM Hwansung Yu  wrote:
>
>> Hi, folks.
>>
>> I have recently been working in a new environment.
>> I'm considering running s2graph on the Google Cloud Platform (GCP) and
>> AWS.
>> But operating HBase in a cloud platform environment is not easy.
>> Of course, AWS provides Hbase based on EMR, but if it supports
>> nosql basically provided  such as DynamoDB or Datastore(GCP), is it
>> possible to operate s2graph more easily in the cloud environment?
>>
>> Regards.
>>
>

Re: HTTP interface integration and unfinished project (s2rest_netty) removal.

[DO YUNG YOON]

+1 on deprecate unnecessary routes.
About 'WithWait' postfix, I think we should make routes with `WithWait`
postfix as the default and deprecate others, so for example, only
leave `/graphs/edges/insert`
and replace use `/graphs/edges/insertWithWait` implementation in there.

Anyway, the list looks pretty long. Why don't we split list to groups, and
let any volunteers like me to work on this.

On Wed, Nov 7, 2018 at 4:51 PM daewon  wrote:

> I've looked at the features that are available to remove the Play!
> Framework.
>
> I have written my comments for each function groups.
>
> - The Admin and Create APIs have yet to integrate many functions into the
> Play! controller code, so code separation must be preceded in order to move
> functionality.
> - The API with the `withWait` postfix of the Edge/Vertex creation API is an
> API that tells the client whether the request is applied correctly.
>This is a duplicate API that exists for backward compatibility.
> - Management routes are suggested to unify API routes with prefixes such as
> `/admin/?` or `/managment/?`.
> - Server health_check or Counter related features are not available
> anymore, so I suggest you exclude them.
>
> ## Edge creation
>   ### List of APIs to leave
> POST/graphs/edges/insert
>
> POST/graphs/edges/insertBulk
> POST/graphs/edges/delete
>
> POST/graphs/edges/deleteAll
>
> POST/graphs/edges/deleteAllWithOutWait
>
> POST/graphs/edges/update
>
> POST/graphs/edges/increment
> POST/graphs/edges/incrementCount
> POST/graphs/edges/bulk
>
>   ### List of APIs that should be removed
> POST/graphs/edges/deleteWithWait
>
> POST/graphs/edges/updateWithWait
>
> POST/graphs/edges/incrementWithWait
>
> POST/graphs/edges/bulkWithWait
>
> POST/graphs/edges/insertWithWait
>
>
> ## Edge query
>
>   ### List of APIs to leave
> POST/graphs/getEdges
>
> POST/graphs/checkEdges
>
>
>   ### List of APIs that should be removed
> POST/graphs/getEdgesGrouped
>
> POST/graphs/getEdgesGroupedExcluded
>
> POST/graphs/getEdgesGroupedExcludedFormatted
>
> GET /graphs/getEdge/:srcId/:tgtId/:labelName/:direction
>
> POST/graphs/getEdgesExcluded
>
> POST/graphs/getEdgesExcluded/grouped
>
> POST/graphs/getEdges/grouped
>
>
>
> ## Vertex related
>   ### List of APIs to leave
> POST/graphs/getVertices
> POST/graphs/vertices/insert
> POST/graphs/vertices/delete
> POST/graphs/vertices/deleteAll
>
>   ### List of APIs that should be removed
> POST/graphs/vertices/insert/:serviceName/:columnName
> POST/graphs/vertices/delete/:serviceName/:columnName
>
> POST/graphs/vertices/deleteAll/:serviceName/:columnName
>
> POST/graphs/vertices/insertWithWait
>
> POST/graphs/vertices/deleteWithWait
>
>
> ## Vertex related
>   ### List of APIs to leave
> POST/graphs/createService
>
> GET /graphs/getService/:serviceName
>
> GET /graphs/getLabels/:serviceName
>
> POST/graphs/createLabel
>
> POST/graphs/addIndex
>
> GET /graphs/getLabel/:labelName
>
> PUT /graphs/deleteLabelReally/:labelName
>
> POST/graphs/addProp/:labelName
>
> POST/graphs/createServiceColumn
>
> PUT /graphs/deleteServiceColumn/:serviceName/:columnName
>
> POST/graphs/addServiceColumnProp/:serviceName/:columnName
>
> POST/graphs/addServiceColumnProps/:serviceName/:columnName
>
> GET /graphs/getServiceColumn/:serviceName/:columnName
>
> POST/graphs/createHTable
>
> GET /admin/labels/:serviceName
>
> POST/graphs/copyLabel/:oldLabelName/:newLabelName
>
> POST/graphs/renameLabel/:oldLabelName/:newLabelName
>
> POST/graphs/swapLabels/:leftLabelName/:rightLabelName
>
> POST/graphs/updateHTable/:labelName/:newHTableName
>
> PUT /graphs/loadCache
>
>
> ## Experiment related
>   ### List of API to leave
> POST/graphs/experiment/:accessToken/:experimentName/:uuid
>
> POST/graphs/experiments
>
>
> ## publish (deprecated)
>   ### List of APIs that should be removed
> POST/publish/:topic
>
> POST/publishOnly/:topic
>
>
>  Health Check(deprecated)
>   ### List of APIs that should be removed
> GET /health_check.html
>
> PUT /health_check/:isHealthy
>
>
> ## Counter related (deprecated)
>   ### List of APIs that should be removed
> POST/counter/v1/:service/:action
> GET /counter/v1/:service/:action
> PUT /counter/v1/:service/:action
> PUT /counter/v1/:service/:action/prepare
> DELETE  /counter/v1/:service/:action
>  

Re: Integrate s2graph documents into projects

[DO YUNG YOON]

I believe that the only reason current document resides on the gitbook was
that person who wrote the documentation(me) did not know another way.

If we can reference other project and find out the better way, I would be
happy to help.
I agree that maintaining documentation on the same repository as source
code would be better way, but I do not know how to start.

It would be great if you can show around how we can do this.

On Wed, Nov 7, 2018 at 12:23 PM daewon  wrote:

> How to use s2grpah can be found in the repository's README.md file and in
> the Gitbook (https://steamshon.gitbooks.io/s2graph-book/content/)
>
> I think there are some problems with how to use s2graph.
>   1. The README.md file does not describe all the APIs.
> ex) Absence of admin API description
>
>   2. The Gitbook does not support changes based on the release version.
> ex) No description for new API: Vertex search query
>
> For these reasons, I think it would be nice if the documentation source is
> in the same repository as the code source.
>
> I've looked at a similar example, and Python seems to be using it this way.
> ex) https://github.com/python/cpython/tree/master/Doc
>
> I think s2graph is better to manage documents like Python in the source
> code repository.
>
> I look forward to feedback.
>

Re: HTTP interface integration and unfinished project (s2rest_netty) removal.

[DO YUNG YOON]

Hi deawon.

Thanks for bringing this issue up.

I agree with your suggestions since I got pretty frustrated when I was
working on S2GRAPH-243(I modify one line of code and had to re-package
project since dev mode on s2rest_play is not working because of classpath
issue).

I am more than happy to work on this since the current dev environment has
been broken.



On Mon, Nov 5, 2018 at 6:15 PM daewon  wrote:

> S2Graph's main web interface is based on Play! Framework.
>
> Key features provided include:
>   - admin api
>   - read/write api (include graph traverse)
>
> and known issues:
>   1. The `s2rest_netty` project is experimental and supports only `graph
> traverse` API.
>   2. `s2rest_play` based on Play! Framework.
> Play! Framework is full stack framework, so it has a lot of
> dependencies that s2graph does not need.
> There is also a conflict with byte buddy for patching asynchbase.
>   3. `GraphQL` is still in the experimental phase and does not yet provide
> all the functionality.
>
> I suggest removing `s2rest_play` and `s2rest_netty` to solve the above
> problem.
>
> Akka HTTP is a stable phase, and the GraphQL web interface is built on Akka
> HTTP.
> It would be nice if a full-featured Web Interface would be provided by
> connecting an existing Web Interface to an implemented GraphQL server.
>
> Thank you for your feedback.
>
> reference: https://richardimaoka.github.io/blog/hello-world-http-bench/
>

Re: Podling Report Reminder - November 2018

[DO YUNG YOON]

Thanks for signing off Sergio

On Sat, Nov 3, 2018 at 11:07 AM Sergio Fernández  wrote:

> signed-off, thanks!
>
> On Fri, Nov 2, 2018, 11:36 DO YUNG YOON 
> > I noticed that the report has not been on wiki, so I just moved what
> > deawon wrote here to https://wiki.apache.org/incubator/November2018
> >
> >
> > On Fri, Oct 26, 2018 at 12:08 AM Sergio Fernández 
> > wrote:
> >
> > > LGTM
> > >
> > > The only tooic I may extend it a bit would be the graduation: It's been
> > > almost three years incubating. I don't see how the podling could
> graduate
> > > given the current shape. Should be discuss alternatives? I'd love to
> see
> > > that captured in the report.
> > >
> > >
> > > On Thu, Oct 25, 2018, 03:01 daewon  wrote:
> > >
> > > > Hi folks.
> > > >
> > > > Here I try to write the report for.
> > > >
> > > > Please feel free to comment.
> > > >
> > > > --
> > > >
> > > > S2Graph
> > > >
> > > > S2Graph is a distributed and scalable OLTP graph database built on
> > Apache
> > > > HBase to support fast traversal of extremely large graphs.
> > > >
> > > > S2Graph has been incubating since 2015-11-29.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > >   1. Make a third release.
> > > >   2. Attract more users and contributors.
> > > >   3. Build the developer community in both size and diversity.
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> > > beaware
> > > > of?
> > > >
> > > >   None
> > > >
> > > > How has the community developed since the last report?
> > > >
> > > >   * In ACNA 2018, we announced S2Graph as the title of the Apache
> > > > S2Graph(incubating) with the build data management platform and
> > audience
> > > > targeting online application system using Graph Database.
> > > > -
> > > >
> > >
> >
> https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
> > > >
> > > >   * There were some questions from the community about the
> introduction
> > > of
> > > > S2Graph.
> > > >
> > > > How has the project developed since the last report?
> > > >
> > > >   * We have received some inquiries from the community and created an
> > > issue
> > > > that does not solve it yet.
> > > > - 5 issues are created and 0 of them are resolved since the last
> > > > report(Sep 2018).
> > > >
> > > > How would you assess the podling's maturity?
> > > > Please feel free to add your own commentary.
> > > >
> > > >   [ ] Initial setup
> > > >   [ ] Working towards first release
> > > >   [X] Community building
> > > >   [ ] Nearing graduation
> > > >   [ ] Other:
> > > >
> > > > Date of last release:
> > > >
> > > >   2017-08-26
> > > >
> > > > When were the last committers or PPMC members elected?
> > > >
> > > >   None
> > > >
> > > > Signed-off-by:
> > > >
> > > >   [ ](s2graph) Andrew Purtell
> > > >  Comments:
> > > >   [ ](s2graph) Seetharam Venkatesh
> > > >  Comments:
> > > >   [ ](s2graph) Sergio Fernández
> > > >  Comments:
> > > >
> > >
> >
>

Re: [DISCUSS]: asking about future of s2graph

[DO YUNG YOON]

Thanks for the comments deawon.

I think providing contribution guide, documentation on the dev environment
and documentation on usage are necessary, and feel like we do not have
these now.

Also, I suggest provide release documentation so any other committer like
you can easily get involved on release cycle. I guess I can work on the
release documentation and ask feedback, targeting the next release which I
hope to happen soon.

Do you think providing more documentation is the top priority for community
building?

There are a few times that someone asked about S2Graph and then they did
not get involved, and I think we should learn from our previous failure to
attract people to our community.

Is S2Graph hard to play around since the lack of documentation or is
s2graph not doing well on what it suppose to provide?

If we think former is the main reason, I think providing documentation on
getting started not only for users but also developers is our top priority.



On Wed, Oct 31, 2018 at 6:32 PM daewon  wrote:

> I agree with many of your comments.
>
> For a community building, what you can do right now is just to listen to
> external requests while constantly improving functionality.
>
> In order to improve the accessibility of the S2Graph project, I think it
> would be better to create a development environment, a contribution guide,
> etc., in addition to documenting how to use it.
>
> We hope that the S2Graph will continue to be developed and successfully
> graduated from the incubation.
>
> 2018년 10월 31일 (수) 오후 3:56, DO YUNG YOON 님이 작성:
>
> > It's been almost 3 years since s2graph has entered apache incubating. Our
> > community has not been successful to reach more people so far and I think
> > failing on growing community is the blocker issue for s2graph to
> graduate.
> >
> > I want to open up the discussion about what we have to do for growing
> > community, and eventually for graduation.
> >
> > In my opinion, there are many parts have been changed after incubation.
> >
> > Followings are notable improvements we have been working on.
> >
> > 1. Query Interface
> >
> > - Tinkerpop OLTP support
> > - GraphQL support
> >
> > 2. Storage
> >
> > - Embedded RocksDB
> > - JDBC Storage
> >
> > 3. Full-text search
> >
> > - ElasticSearch for search on vertex/edge property
> >
> > 4. OLAP
> >
> > - S2GraphSource: dump HFile then creates Spark dataframe.
> > - S2GraphSink: sink Spark dataframe to S2Graph.
> >
> > Even though the project has been improved, our community has not been
> > grown.
> >
> > There could be many reasons that our community is not growing(please list
> > them so we can discuss if we can resolve them), but in my humble opinion,
> > we have not even released above improvements since the last release.
> >
> > As far as I remember, the last time we discuss the release was a long
> time
> > ago(2017-09-08) at here
> >
> >
> https://lists.apache.org/thread.html/d0d8e264b7625128a6c2832723cf2ad555d169f9f277086ce69c3a7b@%3Cdev.s2graph.apache.org%3E
> > .
> >
> > Back then I was under pressure that we need to show that our community
> > growing after release, and since I was not sure, I avoid talking about
> the
> > release, and rather keep working on issues.
> >
> > Now I think it is much better to start by releasing it rather than only
> > just wondering how to grow the community.
> >
> > To grow the community, the very basic way I know is to keep improving the
> > project, releasing it, and advertise it, and get user feedback, and I
> think
> > we stuck to step 1 for too long time.
> >
> > After a few more releases, then if there is no one found s2graph useful,
> > then I think we can happily retire from apache incubating, but I just
> don't
> > feel like we did our best yet.
> >
> > I am willing to pursue building community, and I think it is worth to try
> > out a few more release until decide what's the next step.
> >
> > I want to ask what others think. are there any others who are willing to
> > get more involved?
> >
>

Re: Operating s2graph in a Cloud enviroment

[DO YUNG YOON]

Hi Hwansung.

I think implementing DatastoreFetcher/DatastoreMutator,
DynamoDBFetcher/DynamoDBMutator class which implement our Fetcher/Mutator
interface will help you to work with data in that storage.

The purpose of exposing Fetcher/Mutator interface is for others to
implement in their way to work with their storage, only focusing on how to
fetch vertex/edge from storage when the S2Query is given, and how to store
vertex/edge to storage when S2Edge/S2Vertex are given.

Also if you are deploying s2graph rest on the public cloud, then we can
provide docker image for s2graph rest(not sure if we are already providing
it, let me check it out).

I have very little experience on the public cloud, such as GCP and AWS, so
I might think the wrong direction. I guess we can list what are the
necessary parts, then create issues regarding it.

Please feel free to advise on my comments.

On Fri, Nov 2, 2018 at 10:09 AM Hwansung Yu  wrote:

> Hi, folks.
>
> I have recently been working in a new environment.
> I'm considering running s2graph on the Google Cloud Platform (GCP) and AWS.
> But operating HBase in a cloud platform environment is not easy.
> Of course, AWS provides Hbase based on EMR, but if it supports
> nosql basically provided  such as DynamoDB or Datastore(GCP), is it
> possible to operate s2graph more easily in the cloud environment?
>
> Regards.
>

Re: Podling Report Reminder - November 2018

[DO YUNG YOON]

I noticed that the report has not been on wiki, so I just moved what
deawon wrote here to https://wiki.apache.org/incubator/November2018


On Fri, Oct 26, 2018 at 12:08 AM Sergio Fernández  wrote:

> LGTM
>
> The only tooic I may extend it a bit would be the graduation: It's been
> almost three years incubating. I don't see how the podling could graduate
> given the current shape. Should be discuss alternatives? I'd love to see
> that captured in the report.
>
>
> On Thu, Oct 25, 2018, 03:01 daewon  wrote:
>
> > Hi folks.
> >
> > Here I try to write the report for.
> >
> > Please feel free to comment.
> >
> > --
> >
> > S2Graph
> >
> > S2Graph is a distributed and scalable OLTP graph database built on Apache
> > HBase to support fast traversal of extremely large graphs.
> >
> > S2Graph has been incubating since 2015-11-29.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Make a third release.
> >   2. Attract more users and contributors.
> >   3. Build the developer community in both size and diversity.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> beaware
> > of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >
> >   * In ACNA 2018, we announced S2Graph as the title of the Apache
> > S2Graph(incubating) with the build data management platform and audience
> > targeting online application system using Graph Database.
> > -
> >
> https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
> >
> >   * There were some questions from the community about the introduction
> of
> > S2Graph.
> >
> > How has the project developed since the last report?
> >
> >   * We have received some inquiries from the community and created an
> issue
> > that does not solve it yet.
> > - 5 issues are created and 0 of them are resolved since the last
> > report(Sep 2018).
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2017-08-26
> >
> > When were the last committers or PPMC members elected?
> >
> >   None
> >
> > Signed-off-by:
> >
> >   [ ](s2graph) Andrew Purtell
> >  Comments:
> >   [ ](s2graph) Seetharam Venkatesh
> >  Comments:
> >   [ ](s2graph) Sergio Fernández
> >  Comments:
> >
>

[DISCUSS]: asking about future of s2graph

[DO YUNG YOON]

It's been almost 3 years since s2graph has entered apache incubating. Our
community has not been successful to reach more people so far and I think
failing on growing community is the blocker issue for s2graph to graduate.

I want to open up the discussion about what we have to do for growing
community, and eventually for graduation.

In my opinion, there are many parts have been changed after incubation.

Followings are notable improvements we have been working on.

1. Query Interface

- Tinkerpop OLTP support
- GraphQL support

2. Storage

- Embedded RocksDB
- JDBC Storage

3. Full-text search

- ElasticSearch for search on vertex/edge property

4. OLAP

- S2GraphSource: dump HFile then creates Spark dataframe.
- S2GraphSink: sink Spark dataframe to S2Graph.

Even though the project has been improved, our community has not been
grown.

There could be many reasons that our community is not growing(please list
them so we can discuss if we can resolve them), but in my humble opinion,
we have not even released above improvements since the last release.

As far as I remember, the last time we discuss the release was a long time
ago(2017-09-08) at here
https://lists.apache.org/thread.html/d0d8e264b7625128a6c2832723cf2ad555d169f9f277086ce69c3a7b@%3Cdev.s2graph.apache.org%3E
.

Back then I was under pressure that we need to show that our community
growing after release, and since I was not sure, I avoid talking about the
release, and rather keep working on issues.

Now I think it is much better to start by releasing it rather than only
just wondering how to grow the community.

To grow the community, the very basic way I know is to keep improving the
project, releasing it, and advertise it, and get user feedback, and I think
we stuck to step 1 for too long time.

After a few more releases, then if there is no one found s2graph useful,
then I think we can happily retire from apache incubating, but I just don't
feel like we did our best yet.

I am willing to pursue building community, and I think it is worth to try
out a few more release until decide what's the next step.

I want to ask what others think. are there any others who are willing to
get more involved?

Re: Podling Report Reminder - September 2018

[DO YUNG YOON]

Hi folks.

I was bit busy during the last 2 month and missed our podling report for
August.

Here I try to write the report for September.

Please feel free to comment.



S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

1. Make a third release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None

How has the community developed since the last report?

* not much activities on the mailing list.
* few active committers spend their time working on opened issues.

How has the project developed since the last report?

* mostly still working on opened issues.
  - 22 issues are created and 16 of them are resolved since the last
report(June 2018).
  - keep working on GraphQL integration/OLAP supports.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:

Date of last release:

2017-08-26

When were the last committers or PPMC members elected?

None

Signed-off-by:

[ ](s2graph) Andrew Purtell
Comments:
[ ](s2graph) Seetharam Venkatesh
Comments:
[ ](s2graph) Sergio Fernández
Comments:

IPMC/Shepherd notes:



On Mon, Sep 3, 2018 at 9:55 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 19 September 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, September 05).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/September2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Podling Report Reminder - July 2018

[DO YUNG YOON]

Hi all.

One quick question is that why podling report changes from 3-month interval
to 1-month interval.
I know that s2graph community failed to report on May 2018, which trigger
June 2018 report, but seems like we succeed on July 2018.

Anyway, here is the podling report for July 2018, I am sorry for being
late. Please review.


S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * not much activities on the mailing list.
  * few active committers spend their time working on opened issues.

How has the project developed since the last report?

  * mostly still working on opened issues.
- 15 issues are created and 11 of them are resolved since the last
report(June 2018).
- keep working on GraphQL integration/OLAP supports.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [x](s2graph) Sergio Fernández
 Comments:

IPMC/Shepherd notes:

On Thu, Jun 28, 2018 at 6:41 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, July 04).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/July2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Podling Report Reminder - June 2018

[DO YUNG YOON]

Hi, sergio.

Thanks for taking time for review. I added it to the wiki
<https://wiki.apache.org/incubator/June2018> for signing.


On Tue, Jun 12, 2018 at 2:30 PM Sergio Fernández  wrote:

> LGTM
>
> I'd just stress a bit more the community growing out of the company who
> donated the original source base. But it should be fine.
>
> Please, add it to the wiki for signing. Apologize for the delay.
>
>
> On Mon, Jun 11, 2018, 20:21 daewon  wrote:
>
> > It has been 4 days since the review was requested.
> >
> > I just wonder if I should just wait or what other activities should I do
> > for signed-off?
> >
> > Now no one has any feedback.
> > How do I get a review for a request?
> >
> > On Fri, Jun 8, 2018 at 10:30 AM DO YUNG YOON  wrote:
> >
> > > I tried to write June 2018 report and here it is. Please review.
> > >
> > > S2Graph is a distributed and scalable OLTP graph database built on
> Apache
> > > HBase to support fast traversal of extremely large graphs.
> > >
> > > S2Graph has been incubating since 2015-11-29.
> > >
> > > Three most important issues to address in the move towards graduation:
> > >
> > >   1. Make a third release.
> > >   2. Attract more users and contributors.
> > >   3. Build the developer community in both size and diversity.
> > >
> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > aware of?
> > >
> > > None
> > >
> > > How has the community developed since the last report?
> > >
> > >   * Contributions on few components from community
> > > - bulk loader (S2GRAPH-178, S2GRAPH-184)
> > > - rest api(S2GRAPH-186)
> > > - logger(S2GRAPH-188)
> > >   * Submit a talk to ApacheCon NA 2018
> > > -
> > >
> >
> https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
> > >   * Two initial committer become active, which make 3 active
> committers.
> > > How has the project developed since the last report?
> > >
> > >   * 42 issues are created and 36 of them are resolved.
> > >   * Works more on GraphQL integration.
> > >   * Start to work on supporting OLAP.
> > > * Add simple example using movielens dataset.
> > >   * Generalize read/write interface more to integrate more storage
> > backend
> > > easily.
> > >
> > > How would you assess the podling's maturity?
> > > Please feel free to add your own commentary.
> > >
> > >   [ ] Initial setup
> > >   [ ] Working towards first release
> > >   [x] Community building
> > >   [ ] Nearing graduation
> > >   [ ] Other:
> > >
> > > Date of last release:
> > >
> > >   2017-08-26
> > >
> > > When were the last committers or PPMC members elected?
> > >
> > >   None
> > >
> > > Signed-off-by:
> > >
> > >   [ ](s2graph) Andrew Purtell
> > >  Comments:
> > >   [ ](s2graph) Seetharam Venkatesh
> > >  Comments:
> > >   [ ](s2graph) Sergio Fernández
> > >  Comments:
> > >
> > > IPMC/Shepherd notes:
> > >
> > >
> > >
> > >
> > > On Mon, Jun 4, 2018 at 9:06 AM  wrote:
> > >
> > > > Dear podling,
> > > >
> > > > This email was sent by an automated system on behalf of the Apache
> > > > Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > > > prepare your quarterly board report.
> > > >
> > > > The board meeting is scheduled for Wed, 20 June 2018, 10:30 am PDT.
> > > > The report for your podling will form a part of the Incubator PMC
> > > > report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > > before the board meeting, to allow sufficient time for review and
> > > > submission (Wed, June 06).
> > > >
> > > > Please submit your report with sufficient time to allow the Incubator
> > > > PMC, and subsequently board members to review and digest. Again, the
> > > > very latest you should submit your report is 2 weeks prior to the
> board
> > > > meeting.
> > > >
> > > > Candidate names should not be made public before people are actually
> > > > elected, so please do not include the names of potential committers
> or
> > > > PPMC members in your rep

Re: Podling Report Reminder - June 2018

[DO YUNG YOON]

I tried to write June 2018 report and here it is. Please review.

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None

How has the community developed since the last report?

  * Contributions on few components from community
- bulk loader (S2GRAPH-178, S2GRAPH-184)
- rest api(S2GRAPH-186)
- logger(S2GRAPH-188)
  * Submit a talk to ApacheCon NA 2018
-
https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
  * Two initial committer become active, which make 3 active committers.
How has the project developed since the last report?

  * 42 issues are created and 36 of them are resolved.
  * Works more on GraphQL integration.
  * Start to work on supporting OLAP.
* Add simple example using movielens dataset.
  * Generalize read/write interface more to integrate more storage backend
easily.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [ ](s2graph) Sergio Fernández
 Comments:

IPMC/Shepherd notes:




On Mon, Jun 4, 2018 at 9:06 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 June 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 06).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/June2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: State of S2Graph

[DO YUNG YOON]

Hi John, Sergio.

IMO, I think there are enough activities and I wrote up what we have been
worked on here.
(https://www.mail-archive.com/dev@s2graph.incubator.apache.org/msg01737.html
)

Overall, I agree with Sergio that we have struggled with community growth
from the beginning, and the problem never been to addressed.

There are 3 active committers currently(I counted ones who have committed
for a month), and they are all from the same Org. They were dormant for
about 2 years and now they become active, which I really appreciate and
think it is better than ever in this community. Even though there are few
questions and few followup bug fix issues from the community, there are no
other contributors from other org. IMO, it will take more time and effort
for anyone who tried out start to contribute.

Happy to discuss this topic on the table.


On Sun, Jun 3, 2018 at 1:32 AM Sergio Fernández  wrote:

> Hi John,
>
> I apologise, last month report time was a very bad personal time for me, so
> I missed it.
>
> Overall IMO the podling is lacking community growing out of the original
> company the source was donated. Very few active committers, a from the same
> org. We have discussed few times what could be a viable plan, but we never
> reached any conclusion. So maybe it's a goid time to put the topic on the
> table for the good of the project.
>
> Greetings,
>
> On Sat, Jun 2, 2018, 05:23 John D. Ament  wrote:
>
> > All,
> >
> > Last month the S2Graph podling provided a report, but did not receive
> > mentor sign off.  I don't see any activity from mentors on list, but I do
> > see some activity from the podling.
> >
> > I just want to check, is there enough activity on the podling?  Are the
> > mentors available to review the actions of the podling?
> >
> > John
> >
>

Re: Podling Report Reminder - May 2018

[DO YUNG YOON]

I tried to write May report and here it is. please review.


S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * Contributions on few components from community
- bulk loader (S2GRAPH-178, S2GRAPH-184)
- rest api(S2GRAPH-186)
- logger(S2GRAPH-188)
  * Submit a talk to ApacheCon NA 2018
-
https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
  * One more initial committer who has been dormant become active
on(S2GRAPH-185)
How has the project developed since the last report?

  * 31 issues are created and 27 of them are resolved.
  * Works more on GraphQL integration.
  * Start to work on supporting OLAP.
  * Generalize read/write interface more to integrate more storage backend
easily.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [ ](s2graph) Sergio Fernández
 Comments:


On Tue, May 1, 2018 at 9:27 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 May 2018, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, May 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/May2018
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Podling Report Reminder - February 2018

[DO YUNG YOON]

I tried to write *February* report and here it is. please review.


S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * Suggestion from community on interactive graph visualization feature is
under development(S2GRAPH-174)
  * Initial committer who has been dormant for a while become active
on(S2GRAPH-172)
How has the project developed since the last report?

  * Support GraphQL as standard web interface. (S2GRAPH-172)
  * Support Elastic Search as global index provider. (S2GRAPH-175)
  * Add Embedded RocksDB as storage backend. (S2GRAPH-166)
  * Provide java client.
- Define public interface and change code base to only use interface.
(S2GRAPH-170)
- Implementing java client is not yet started.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [ ](s2graph) Sergio Fernández
 Comments:


On Thu, Feb 1, 2018 at 5:50 PM DO YUNG YOON <sho...@gmail.com> wrote:

> I am going to volunteer this time, and will write it by this weekend.
>
> Thanks for notifying.
>
> On Tue, Jan 30, 2018 at 1:35 PM Sergio Fernández <wik...@apache.org>
> wrote:
>
>> Any volunteer for this reporting cycle?
>>
>> On Mon, Jan 29, 2018 at 8:20 PM, <johndam...@apache.org> wrote:
>>
>> > Dear podling,
>> >
>> > This email was sent by an automated system on behalf of the Apache
>> > Incubator PMC. It is an initial reminder to give you plenty of time to
>> > prepare your quarterly board report.
>> >
>> > The board meeting is scheduled for Wed, 21 February 2018, 10:30 am PDT.
>> > The report for your podling will form a part of the Incubator PMC
>> > report. The Incubator PMC requires your report to be submitted 2 weeks
>> > before the board meeting, to allow sufficient time for review and
>> > submission (Wed, February 07).
>> >
>> > Please submit your report with sufficient time to allow the Incubator
>> > PMC, and subsequently board members to review and digest. Again, the
>> > very latest you should submit your report is 2 weeks prior to the board
>> > meeting.
>> >
>> > Thanks,
>> >
>> > The Apache Incubator PMC
>> >
>> > Submitting your Report
>> >
>> > --
>> >
>> > Your report should contain the following:
>> >
>> > *   Your project name
>> > *   A brief description of your project, which assumes no knowledge of
>> > the project or necessarily of its field
>> > *   A list of the three most important issues to address in the move
>> > towards graduation.
>> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>> > aware of
>> > *   How has the community developed since the last report
>> > *   How has the project developed since the last report.
>> > *   How does the podling rate their own maturity.
>> >
>> > This should be appended to the Incubator Wiki page at:
>> >
>> > https://wiki.apache.org/incubator/February2018
>> >
>> > Note: This is manually populated. You may need to wait a little before
>> > this page is created from a template.
>> >
>> > Mentors
>> > ---
>> >
>> > Mentors should review reports for their project(s) and sign them off on
>> > the Incubator wiki page. Signing off reports shows that you are
>> > following the project - projects that are not signed may raise alarms
>> > for the Incubator PMC.
>> >
>> > Incubator PMC
>> >
>>
>

Re: Podling Report Reminder - February 2018

[DO YUNG YOON]

I am going to volunteer this time, and will write it by this weekend.

Thanks for notifying.

On Tue, Jan 30, 2018 at 1:35 PM Sergio Fernández  wrote:

> Any volunteer for this reporting cycle?
>
> On Mon, Jan 29, 2018 at 8:20 PM,  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 21 February 2018, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, February 07).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/February2018
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>

Re: Podling Report Reminder - November 2017

[DO YUNG YOON]

Thanks for your review Sergio.

On Fri, Nov 3, 2017 at 10:12 AM Sergio Fernández <wik...@apache.org> wrote:

> LGTM. Signing it off.
>
> On Tue, Oct 31, 2017 at 6:06 PM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > I tried to write November report and here it is. please review.
> >
> > S2Graph is a distributed and scalable OLTP graph database built on Apache
> > HBase to support fast traversal of extremely large graphs.
> >
> > S2Graph has been incubating since 2015-11-29.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Make a third release.
> >   2. Attract more users and contributors.
> >   3. Build the developer community in both size and diversity.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   None
> >
> > How has the community developed since the last report?
> >
> >   * We had our second official release 0.2.0 on Aug 26th 2017.
> >   * There have been 2 PR from a new contributor
> > How has the project developed since the last report?
> >
> >   * Discuss the scope of next release.
> > - New Feature: Provide java client. (on going S2GRAPH-80)
> > - New Feature: Support more storage backend implementation. (ongoing
> > S2GRAPH-169, S2GRAPH-166)
> > - New Feature: Support more Index Provider implementation. (not
> > started)
> > - New Feature: Implement TinkerPop`s Graph Compute for OLAP support
> > (not started)
> >
> > How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> >
> >   [ ] Initial setup
> >   [ ] Working towards first release
> >   [x] Community building
> >   [ ] Nearing graduation
> >   [ ] Other:
> >
> > Date of last release:
> >
> >   2017-08-26
> >
> > When were the last committers or PPMC members elected?
> >
> >   None
> >
> > Signed-off-by:
> >
> >   [ ](s2graph) Andrew Purtell
> >  Comments:
> >   [ ](s2graph) Seetharam Venkatesh
> >  Comments:
> >   [ ](s2graph) Sergio Fernández
> >  Comments:
> >
> >
> >
> > On Sat, Oct 28, 2017 at 9:11 PM <johndam...@apache.org> wrote:
> >
> > > Dear podling,
> > >
> > > This email was sent by an automated system on behalf of the Apache
> > > Incubator PMC. It is an initial reminder to give you plenty of time to
> > > prepare your quarterly board report.
> > >
> > > The board meeting is scheduled for Wed, 15 November 2017, 10:30 am PDT.
> > > The report for your podling will form a part of the Incubator PMC
> > > report. The Incubator PMC requires your report to be submitted 2 weeks
> > > before the board meeting, to allow sufficient time for review and
> > > submission (Wed, November 01).
> > >
> > > Please submit your report with sufficient time to allow the Incubator
> > > PMC, and subsequently board members to review and digest. Again, the
> > > very latest you should submit your report is 2 weeks prior to the board
> > > meeting.
> > >
> > > Thanks,
> > >
> > > The Apache Incubator PMC
> > >
> > > Submitting your Report
> > >
> > > --
> > >
> > > Your report should contain the following:
> > >
> > > *   Your project name
> > > *   A brief description of your project, which assumes no knowledge of
> > > the project or necessarily of its field
> > > *   A list of the three most important issues to address in the move
> > > towards graduation.
> > > *   Any issues that the Incubator PMC or ASF Board might wish/need to
> be
> > > aware of
> > > *   How has the community developed since the last report
> > > *   How has the project developed since the last report.
> > > *   How does the podling rate their own maturity.
> > >
> > > This should be appended to the Incubator Wiki page at:
> > >
> > > https://wiki.apache.org/incubator/November2017
> > >
> > > Note: This is manually populated. You may need to wait a little before
> > > this page is created from a template.
> > >
> > > Mentors
> > > ---
> > >
> > > Mentors should review reports for their project(s) and sign them off on
> > > the Incubator wiki page. Signing off reports shows that you are
> > > following the project - projects that are not signed may raise alarms
> > > for the Incubator PMC.
> > >
> > > Incubator PMC
> > >
> >
>

Re: Podling Report Reminder - November 2017

[DO YUNG YOON]

I tried to write November report and here it is. please review.

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a third release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * We had our second official release 0.2.0 on Aug 26th 2017.
  * There have been 2 PR from a new contributor
How has the project developed since the last report?

  * Discuss the scope of next release.
- New Feature: Provide java client. (on going S2GRAPH-80)
- New Feature: Support more storage backend implementation. (ongoing
S2GRAPH-169, S2GRAPH-166)
- New Feature: Support more Index Provider implementation. (not started)
- New Feature: Implement TinkerPop`s Graph Compute for OLAP support
(not started)

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [ ](s2graph) Sergio Fernández
 Comments:



On Sat, Oct 28, 2017 at 9:11 PM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 November 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, November 01).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/November2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: s2graph

[DO YUNG YOON]

Hi Ruchir.

Welcome and thanks for your interests.

If you want to setup development environment, I think following link can
also be helpful.
- https://github.com/apache/incubator-s2graph/tree/master/dev_support

Best Regards.
DOYUNG

On Tue, Oct 10, 2017 at 9:05 PM Hyunsung Jo  wrote:

> Hi Ruchir,
>
> You will be able to find the basic guidelines in the following links:
> - https://github.com/apache/incubator-s2graph#quick-start
> - https://steamshon.gitbooks.io/s2graph-book/content/getting_started.html
>
> While some of the information might be dated you can always reach out to
> the dev mail-list .
>
> Regards,
> Jo
>
>
> On Mon, Oct 9, 2017 at 10:17 PM Ruchir Choudhry <
> ruchirchoudhr...@gmail.com> wrote:
>
>> Need your help to get started with this project.
>>
>> Will appreciate if you can provide me a link or a doc
>> for setup and some basic guideline,
>>
>>
>> I will be happy to help you all along the project.
>>
>>
>> Regards,
>> Ruchir
>>
>

Re: [DISCUSS] milestone for next release

[DO YUNG YOON]

Hi Sergio.

I am happy to discuss how to growth our community in general. Can you
please explain more about mid-term approaches?

On Mon, Sep 18, 2017 at 10:44 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi daewon, Thanks for feedback.
>
> I was thinking about including admin interface, tinkerpop interface, and
> few public interface from S2Graph in java client. I agree that tinkerpop
> interface need to be simple as possible(if that is what you mean by POJO).
>
> On Thu, Sep 14, 2017 at 1:01 AM Sergio Fernández <wik...@apache.org>
> wrote:
>
>> This is going to be your third incubator release. Since community growth
>> is
>> not yet reached, do you want to discuss mid-term approaches to exit
>> Incubator?
>>
>> On Tue, Sep 12, 2017 at 5:37 PM, daewon <dae...@apache.org> wrote:
>>
>> > Every suggestion looks good. 1. Java Client Is `JavaClient` related to
>> > Admin Interface? If you exclude `Admin Interface`, use Tinkerpop
>> Interface
>> > as main Java Interface. In this case, however, it is likely to lose the
>> > advantage of Asynchronous Traverse, a feature of S2Graph. If need to
>> > implement it separately for the above reason, we should use `S2Edge,
>> > S2Vertex` from Tinkerpop implemention as POJO. and JavaClient should
>> > include a query builder.
>> > Given the user base, the provision of JavaClient is likely to be
>> > meaningful.
>> >
>> >
>> >
>> > On Fri, Sep 8, 2017 at 9:29 PM DO YUNG YOON <sho...@gmail.com> wrote:
>> >
>> > > Hi folks.
>> > >
>> > > I want to discuss milestone for next release.
>> > >
>> > > Here is a my list that I wish include in next release. Please feel
>> free
>> > to
>> > > correct me or add more issues I missed.
>> > >
>> > > 1. Java Client
>> > >
>> > > even though it is possible to use scala code in java, using scala
>> code in
>> > > java project is frustrating. since there are more java users than
>> scala
>> > > users, I think it is reasonable to provide both java and scala client.
>> > >
>> > > Regarding client, tinkerpop related codes are currently mixed with
>> > > s2graph's core scala code. it would be better if we can separate these
>> > two.
>> > > I think chainging tinkerpop related codes into java could make things
>> > easy
>> > > but not sure before try out.
>> > >
>> > > 2. Storage Backend
>> > >
>> > > I think it would be great if we can provide more storage backend.
>> > > personally, I really liked tinker graph which store data in memory,
>> for
>> > > development and test. I suggest providing local storage data so users
>> > > without HBase can try out s2graph more easily. Also by trying to add
>> new
>> > > storage backend, we can identify what need to be improved on our
>> storage
>> > > interface. I think redis, cassandra, mysql, postgresql can be
>> integrated
>> > > with s2graph as storage backend in theory, but have to try
>> implementing
>> > > them to make sure they are possible.
>> > >
>> > > 3. Index Provider
>> > >
>> > > current implementation only use local lucene for global index.
>> > distributed
>> > > index provider, such as solr, elastic search seems more practical and
>> it
>> > > would be great addition also.
>> > >
>> > > 4. Graph Compute
>> > >
>> > > it would be great if we can explore integrate with existing OLAP
>> > framework
>> > > from TinkerPop so our users not only run OLTP query but also run OLAP
>> > query
>> > > with data alread stored in s2graph.
>> > >
>> > > About schedule for next release, I would suggest to build next release
>> > > candidate at end of september.
>> > >
>> > > I don't expect all of above to be included on our next release scope,
>> > but I
>> > > think they are at least worth to discuss.
>> > >
>> > > What you guys think?
>> > >
>> >
>>
>

Re: [DISCUSS] milestone for next release

[DO YUNG YOON]

Hi daewon, Thanks for feedback.

I was thinking about including admin interface, tinkerpop interface, and
few public interface from S2Graph in java client. I agree that tinkerpop
interface need to be simple as possible(if that is what you mean by POJO).

On Thu, Sep 14, 2017 at 1:01 AM Sergio Fernández <wik...@apache.org> wrote:

> This is going to be your third incubator release. Since community growth is
> not yet reached, do you want to discuss mid-term approaches to exit
> Incubator?
>
> On Tue, Sep 12, 2017 at 5:37 PM, daewon <dae...@apache.org> wrote:
>
> > Every suggestion looks good. 1. Java Client Is `JavaClient` related to
> > Admin Interface? If you exclude `Admin Interface`, use Tinkerpop
> Interface
> > as main Java Interface. In this case, however, it is likely to lose the
> > advantage of Asynchronous Traverse, a feature of S2Graph. If need to
> > implement it separately for the above reason, we should use `S2Edge,
> > S2Vertex` from Tinkerpop implemention as POJO. and JavaClient should
> > include a query builder.
> > Given the user base, the provision of JavaClient is likely to be
> > meaningful.
> >
> >
> >
> > On Fri, Sep 8, 2017 at 9:29 PM DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > > Hi folks.
> > >
> > > I want to discuss milestone for next release.
> > >
> > > Here is a my list that I wish include in next release. Please feel free
> > to
> > > correct me or add more issues I missed.
> > >
> > > 1. Java Client
> > >
> > > even though it is possible to use scala code in java, using scala code
> in
> > > java project is frustrating. since there are more java users than scala
> > > users, I think it is reasonable to provide both java and scala client.
> > >
> > > Regarding client, tinkerpop related codes are currently mixed with
> > > s2graph's core scala code. it would be better if we can separate these
> > two.
> > > I think chainging tinkerpop related codes into java could make things
> > easy
> > > but not sure before try out.
> > >
> > > 2. Storage Backend
> > >
> > > I think it would be great if we can provide more storage backend.
> > > personally, I really liked tinker graph which store data in memory, for
> > > development and test. I suggest providing local storage data so users
> > > without HBase can try out s2graph more easily. Also by trying to add
> new
> > > storage backend, we can identify what need to be improved on our
> storage
> > > interface. I think redis, cassandra, mysql, postgresql can be
> integrated
> > > with s2graph as storage backend in theory, but have to try implementing
> > > them to make sure they are possible.
> > >
> > > 3. Index Provider
> > >
> > > current implementation only use local lucene for global index.
> > distributed
> > > index provider, such as solr, elastic search seems more practical and
> it
> > > would be great addition also.
> > >
> > > 4. Graph Compute
> > >
> > > it would be great if we can explore integrate with existing OLAP
> > framework
> > > from TinkerPop so our users not only run OLTP query but also run OLAP
> > query
> > > with data alread stored in s2graph.
> > >
> > > About schedule for next release, I would suggest to build next release
> > > candidate at end of september.
> > >
> > > I don't expect all of above to be included on our next release scope,
> > but I
> > > think they are at least worth to discuss.
> > >
> > > What you guys think?
> > >
> >
>

[DISCUSS] milestone for next release

[DO YUNG YOON]

Hi folks.

I want to discuss milestone for next release.

Here is a my list that I wish include in next release. Please feel free to
correct me or add more issues I missed.

1. Java Client

even though it is possible to use scala code in java, using scala code in
java project is frustrating. since there are more java users than scala
users, I think it is reasonable to provide both java and scala client.

Regarding client, tinkerpop related codes are currently mixed with
s2graph's core scala code. it would be better if we can separate these two.
I think chainging tinkerpop related codes into java could make things easy
but not sure before try out.

2. Storage Backend

I think it would be great if we can provide more storage backend.
personally, I really liked tinker graph which store data in memory, for
development and test. I suggest providing local storage data so users
without HBase can try out s2graph more easily. Also by trying to add new
storage backend, we can identify what need to be improved on our storage
interface. I think redis, cassandra, mysql, postgresql can be integrated
with s2graph as storage backend in theory, but have to try implementing
them to make sure they are possible.

3. Index Provider

current implementation only use local lucene for global index. distributed
index provider, such as solr, elastic search seems more practical and it
would be great addition also.

4. Graph Compute

it would be great if we can explore integrate with existing OLAP framework
from TinkerPop so our users not only run OLTP query but also run OLAP query
with data alread stored in s2graph.

About schedule for next release, I would suggest to build next release
candidate at end of september.

I don't expect all of above to be included on our next release scope, but I
think they are at least worth to discuss.

What you guys think?

Re: [RESULT][VOTE] Apache S2Graph(incubating) 0.2.0 release RC3

[DO YUNG YOON]

I have done below so far after vote has passed.

1. tag v0.2.0-incubating and remove the RC tags.
2. update the version in version.sbt to 0.2.1-SNAPSHOT.
3. upload the source release to ASF mirrors.
4. publish the binary and source JAR to the Maven Central.

I need help on post download link at the website. Can anybody help me to
add 0.2.0 release download link on website?

Unless objection, I will send official announce tomorrow after read through
https://lists.apache.org/list.html?annou...@apache.org tonight.

Thanks.

On Wed, Aug 23, 2017 at 1:42 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi All,
>
> The vote for releasing Apache S2Graph 0.2.0-incubating passed with 5
> binding +1s, 3 non-binding +1s, and no 0 or -1.
>
> Binding +1s:
> Sergio Fernández
> Justin Mclean
> Josh Elser
> John D. Ament
> Seetharam Venkatesh
>
> The votes were (
> https://www.mail-archive.com/general@incubator.apache.org/msg60928.html)
>
> Thanks to everyone for taking the time to review and vote. We will now
> proceed with the release.
>
>
>

[RESULT][VOTE] Apache S2Graph(incubating) 0.2.0 release RC3

[DO YUNG YOON]

Hi all.

After being opened for over 72 hours, the vote for releasing Apache S2Graph
0.2.0-incubating RC3 passed with following result.

+1 binding
- Sergio Fernández

+1 non-binding
- DO YUNG YOON
- Daewon Jung

There was no -1 and 0.

I am going to create a vote in the general@ list.

Thanks.

Re: [VOTE] Apache S2Graph(incubating) 0.2.0 release RC3

[DO YUNG YOON]

Thanks for your review daewon.

On Tue, Aug 15, 2017 at 3:01 AM daewon <dae...@apache.org> wrote:

> +1 (non-binding)
>
> I tested below work well in the following environment.
>   - sbt test
>   - sbt package
>   - run w/ example.sh
>
> # TEST ENV
>
> ## O/S
> ```
> NAME="Ubuntu"
> VERSION="16.04.2 LTS (Xenial Xerus)"
> ID=ubuntu
> ID_LIKE=debian
> PRETTY_NAME="Ubuntu 16.04.2 LTS"
> VERSION_ID="16.04"
> HOME_URL="http://www.ubuntu.com/;
> SUPPORT_URL="http://help.ubuntu.com/;
> BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
> VERSION_CODENAME=xenial
> UBUNTU_CODENAME=xenial
> ```
>
> ## java
> ```
> openjdk version "1.8.0_131"
> OpenJDK Runtime Environment (build
> 1.8.0_131-8u131-b11-2ubuntu1.16.04.3-b11)
> OpenJDK 64-Bit Server VM (build 25.131-b11, mixed mode)
> ```
>
>
> On Mon, Aug 14, 2017 at 9:57 AM DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi Sergio, Thank you for reviewing RC3.
> >
> > - S2GRAPH-159: Appreciate your patch.
> > - S2GRAPH-160: I identified 3 reasons for this issues(
> >
> >
> https://issues.apache.org/jira/browse/S2GRAPH-160?focusedCommentId=16123376=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16123376
> > ).
> > I am going to create 3 separate issue targeting next release.
> > - S2GRAPH-161: got your point. I will create task to add `(incubating)`
> > suffix on version.
> >
> >
> > Best Regards
> >
> > On Sun, Aug 13, 2017 at 1:05 PM Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > +1 (binding)
> > >
> > > So far I've successfully checked:
> > >
> > > * signatures and digests
> > > * source releases file layouts
> > > * matched git tags and commit ids
> > > * incubator suffix and disclaimer
> > > * NOTICE and LICENSE files
> > > * license headers
> > > * clean build (Java 1.8.0_131, Scala, 2.11.8, SBT 0.13.12, Debian
> amd64)
> > >
> > > With respect to my vote to RC2:
> > >
> > > * S2GRAPH-159 has been fixed.
> > > * S2GRAPH-160 has been minimized, not fixed, but looks much better.
> > > * S2GRAPH-161 is not fully right, because new CHANGES file shows a
> > version
> > > without the incubating suffix. As the file is not part of the release
> > > tarball it should be fine, but would be nice to keep that very clear.
> > >
> > > Thanks for the work on this new release!
> > >
> > > Cheers,
> > >
> > >
> > >
> > > On Sat, Aug 12, 2017 at 4:38 PM, DO YUNG YOON <sho...@gmail.com>
> wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > I tried RC3 on ubuntu 16.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK
> > 1.8.0_91.
> > > >
> > > > Checked followings.
> > > >
> > > > 1. Checksums and PGP signatures are valid
> > > > 2. Release consists of source code only, no binaries
> > > > 3. DISCLAIMER is correct, filenames include "incubating", top level
> > > NOTICE
> > > > and LICENSE files.
> > > > 4. Check license header on files by following DEVELOPMENT.md.
> > > > 5. Test if I can run `bin/example.sh` after build using `sbt
> package`.
> > > > 6. `sbt compile`, `sbt test:compile` to see any compile errors.
> > > > 7. `sbt "project loader" assembly`, `sbt "project s2counter_loader"`
> > > > assembly to see executable jar successfully built from source.
> > > > 8. `sbt test` to see if all test cases passed.
> > > >
> > > > Thanks.
> > > >
> > > > On Sat, Aug 12, 2017 at 7:31 AM DO YUNG YOON <sho...@gmail.com>
> wrote:
> > > >
> > > > > Hi all
> > > > >
> > > > > This is a call for a releasing Apache S2Graph 0.2.0-incubating,
> > release
> > > > > candidate 3.
> > > > >
> > > > > The source tarball, including signatures, digests, etc. can be
> found
> > > at:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> > > > 2.0-incubating-RC3
> > > > >
> > > > > The tag to be voted upon is v0.2.0-incubating-rc3:
> > > > >
> > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > > > git;a=shortlog;h

Re: [VOTE] Apache S2Graph(incubating) 0.2.0 release RC3

[DO YUNG YOON]

Hi Sergio, Thank you for reviewing RC3.

- S2GRAPH-159: Appreciate your patch.
- S2GRAPH-160: I identified 3 reasons for this issues(
https://issues.apache.org/jira/browse/S2GRAPH-160?focusedCommentId=16123376=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16123376).
I am going to create 3 separate issue targeting next release.
- S2GRAPH-161: got your point. I will create task to add `(incubating)`
suffix on version.


Best Regards

On Sun, Aug 13, 2017 at 1:05 PM Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> +1 (binding)
>
> So far I've successfully checked:
>
> * signatures and digests
> * source releases file layouts
> * matched git tags and commit ids
> * incubator suffix and disclaimer
> * NOTICE and LICENSE files
> * license headers
> * clean build (Java 1.8.0_131, Scala, 2.11.8, SBT 0.13.12, Debian amd64)
>
> With respect to my vote to RC2:
>
> * S2GRAPH-159 has been fixed.
> * S2GRAPH-160 has been minimized, not fixed, but looks much better.
> * S2GRAPH-161 is not fully right, because new CHANGES file shows a version
> without the incubating suffix. As the file is not part of the release
> tarball it should be fine, but would be nice to keep that very clear.
>
> Thanks for the work on this new release!
>
> Cheers,
>
>
>
> On Sat, Aug 12, 2017 at 4:38 PM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > I tried RC3 on ubuntu 16.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_91.
> >
> > Checked followings.
> >
> > 1. Checksums and PGP signatures are valid
> > 2. Release consists of source code only, no binaries
> > 3. DISCLAIMER is correct, filenames include "incubating", top level
> NOTICE
> > and LICENSE files.
> > 4. Check license header on files by following DEVELOPMENT.md.
> > 5. Test if I can run `bin/example.sh` after build using `sbt package`.
> > 6. `sbt compile`, `sbt test:compile` to see any compile errors.
> > 7. `sbt "project loader" assembly`, `sbt "project s2counter_loader"`
> > assembly to see executable jar successfully built from source.
> > 8. `sbt test` to see if all test cases passed.
> >
> > Thanks.
> >
> > On Sat, Aug 12, 2017 at 7:31 AM DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > > Hi all
> > >
> > > This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
> > > candidate 3.
> > >
> > > The source tarball, including signatures, digests, etc. can be found
> at:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> > 2.0-incubating-RC3
> > >
> > > The tag to be voted upon is v0.2.0-incubating-rc3:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc3
> > >
> > > The release hash is b66a56e39c250c8626286c4f4612c1f4b78adcf1:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=commit;h=b66a56e39c250c8626286c4f4612c1f4b78adcf1
> > >
> > > Release artifacts are signed with the following key:
> > > https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
> > >
> > > Once download source, please look into README.md to build from source.
> > >
> > > Notable changes from 0.1.0 is providing tinkerpop3
> > integration(S2GRAPH-72,
> > > S2GRAPH-151).
> > >
> > > Changes from rc2 is following.
> > >
> > > - S2GRAPH-159: Wrong syntax at a bash script under Linux
> > > - S2GRAPH-161: Update CHANGES file for 0.2.0 release
> > > - S2GRAPH-160: Remove warning while package
> > >
> > > The vote will be open for at least 72 hours. Unless objection I will
> try
> > > to close it Tuesday August 15 if we have sufficient votes.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> > > please vote:
> > >
> > > [ ] +1 Release this package as 0.2.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks,
> > > DOYUNG YOON.
> > >
> >
>

Re: [VOTE] Apache S2Graph(incubating) 0.2.0 release RC3

[DO YUNG YOON]

+1 (non-binding)

I tried RC3 on ubuntu 16.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_91.

Checked followings.

1. Checksums and PGP signatures are valid
2. Release consists of source code only, no binaries
3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
and LICENSE files.
4. Check license header on files by following DEVELOPMENT.md.
5. Test if I can run `bin/example.sh` after build using `sbt package`.
6. `sbt compile`, `sbt test:compile` to see any compile errors.
7. `sbt "project loader" assembly`, `sbt "project s2counter_loader"`
assembly to see executable jar successfully built from source.
8. `sbt test` to see if all test cases passed.

Thanks.

On Sat, Aug 12, 2017 at 7:31 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi all
>
> This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
> candidate 3.
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC3
>
> The tag to be voted upon is v0.2.0-incubating-rc3:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc3
>
> The release hash is b66a56e39c250c8626286c4f4612c1f4b78adcf1:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=b66a56e39c250c8626286c4f4612c1f4b78adcf1
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
>
> Once download source, please look into README.md to build from source.
>
> Notable changes from 0.1.0 is providing tinkerpop3 integration(S2GRAPH-72,
> S2GRAPH-151).
>
> Changes from rc2 is following.
>
> - S2GRAPH-159: Wrong syntax at a bash script under Linux
> - S2GRAPH-161: Update CHANGES file for 0.2.0 release
> - S2GRAPH-160: Remove warning while package
>
> The vote will be open for at least 72 hours. Unless objection I will try
> to close it Tuesday August 15 if we have sufficient votes.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> please vote:
>
> [ ] +1 Release this package as 0.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks,
> DOYUNG YOON.
>

[VOTE] Apache S2Graph(incubating) 0.2.0 release RC3

[DO YUNG YOON]

Hi all

This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
candidate 3.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC3

The tag to be voted upon is v0.2.0-incubating-rc3:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc3

The release hash is b66a56e39c250c8626286c4f4612c1f4b78adcf1:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=b66a56e39c250c8626286c4f4612c1f4b78adcf1

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md to build from source.

Notable changes from 0.1.0 is providing tinkerpop3 integration(S2GRAPH-72,
S2GRAPH-151).

Changes from rc2 is following.

- S2GRAPH-159: Wrong syntax at a bash script under Linux
- S2GRAPH-161: Update CHANGES file for 0.2.0 release
- S2GRAPH-160: Remove warning while package

The vote will be open for at least 72 hours. Unless objection I will try to
close it Tuesday August 15 if we have sufficient votes.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.2.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

Re: [VOTE] Apache S2Graph(incubating) 0.2.0 release RC2

[DO YUNG YOON]

Hi Sergio.

Thanks for reviewing and providing patch for the bug.
I am going to work on RC3 since this vote is closed.

Best Regards


On Fri, Aug 11, 2017 at 12:00 PM Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> apologize for the late vote.
>
> -1 (binding)
>
> So far I've successfully checked:
> * signatures and digests
> * source releases file layouts
> * matched git tags and commit ids
> * incubator suffix and disclaimer
> * NOTICE and LICENSE files
> * license headers
> * clean build (Java 1.8.0_131, Scala, 2.11.8, SBT 0.13.12, Debian amd64)
>
> I still got quite some warnings on the build, as happened for
> 0.1.0-incubating.
>
> But why I vote negatively to the release it isn't any formal requirement,
> but a functional error I think should be easy to fix:
>
> $ sh bin/start-s2graph.sh
> bin/start-s2graph.sh: 22:
>
> /home/wikier/tmp/s2graph/apache-s2graph-0.2.0-incubating-src/bin/s2graph-env.sh:
> Bad substitution
>
> Already reported as S2GRAPH-159. I'll provide a patch to fix it.
>
> BTW, the file https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> 2.0-incubating-RC2/CHANGES
> <https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC2/CHANGES>
> claims changes for "Release 0.1.0 - unreleased".
>
> Best,
>
>
> On Mon, Aug 7, 2017 at 10:10 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi all
> >
> > This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
> > candidate 2.
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> > 2.0-incubating-RC2
> >
> > The tag to be voted upon is v0.2.0-incubating-rc2:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc2
> >
> > The release hash is 917475b62d68ac952716df5d8ce6465656ec1f25:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=commit;h=917475b62d68ac952716df5d8ce6465656ec1f25
> >
> > Release artifacts are signed with the following key:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
> >
> > Once download source, please look into README.md to build from source.
> >
> > Notable changes from 0.1.0 is providing tinkerpop3
> integration(S2GRAPH-72,
> > S2GRAPH-151).
> >
> > The vote will be open for at least 72 hours. Unless objection I will try
> to
> > close it Wednesday August 9 if we have sufficient votes.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > please vote:
> >
> > [ ] +1 Release this package as 0.2.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks,
> > DOYUNG YOON.
> >
>

Re: Need mentor sign off on the S2Graph report

[DO YUNG YOON]

Sergio, Thanks for your answer.


On Fri, Aug 11, 2017 at 11:33 AM Sergio Fernández <wik...@apache.org> wrote:

> Doyung, release candidate would need to get at least 3 binding votes. If
> you don't get them from dev@s2graph, you would need to go to
> general@incubator. Mentors or not, every IPMC member counts here.
>
> On Thu, Aug 10, 2017 at 8:08 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi John.
> >
> > I was wondering what podlings supposed to do if we failed to get sign off
> > from our mentors.
> >
> > Also we opened up vote for new release candidates(
> > http://markmail.org/message/i7ix3rqk7ishp4r3) and we still need binding
> > vote from our mentors. I am also wondering what RM should do to proceed
> > incubator release process in case when mentors are not available.
> >
> > Best Regards.
> > Doyung Yoon
> >
> >
> > On Thu, Aug 10, 2017 at 10:58 AM John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > All,
> > >
> > > Just a reminder, we need at least one mentor to sign off on the S2
> Graph
> > > report.  If no one can get to it in the next 24 hours I'll need to move
> > the
> > > podling to monthly and expect a report next month.
> > >
> > > John
> > >
> >
>

Re: Need mentor sign off on the S2Graph report

[DO YUNG YOON]

Thank you for signing off Andrew.

On Fri, Aug 11, 2017 at 2:54 AM Andrew Purtell  wrote:

> I signed off with the comment
>
>  "We need to find more mentors for this podling. In the past
>  Sergio was helpful but he hasn't been around much recently. I would
>  resign but am lurking as mentor of last resort."
>
> and removed s2graph from the list of podlings missing signoff. (This time.)
>
>
> On Thu, Aug 10, 2017 at 10:47 AM, Andrew Purtell 
> wrote:
>
> > I can sign off this time. Normally I would have resigned by now but am
> > lurking enough to be a last resort. Thanks for bringing this to my
> > attention. We should find more mentors for S2Graph. The current situation
> > is quite unfair to them.
> >
> > On Wed, Aug 9, 2017 at 6:58 PM, John D. Ament 
> > wrote:
> >
> >> All,
> >>
> >> Just a reminder, we need at least one mentor to sign off on the S2 Graph
> >> report.  If no one can get to it in the next 24 hours I'll need to move
> >> the
> >> podling to monthly and expect a report next month.
> >>
> >> John
> >>
> >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Words like orphans lost among the crosstalk, meaning torn from truth's
> > decrepit hands
> >- A23, Crosstalk
> >
>
>
>
> --
> Best regards,
> Andrew
>
> Words like orphans lost among the crosstalk, meaning torn from truth's
> decrepit hands
>- A23, Crosstalk
>

Re: Need mentor sign off on the S2Graph report

[DO YUNG YOON]

Hi John.

I was wondering what podlings supposed to do if we failed to get sign off
from our mentors.

Also we opened up vote for new release candidates(
http://markmail.org/message/i7ix3rqk7ishp4r3) and we still need binding
vote from our mentors. I am also wondering what RM should do to proceed
incubator release process in case when mentors are not available.

Best Regards.
Doyung Yoon


On Thu, Aug 10, 2017 at 10:58 AM John D. Ament 
wrote:

> All,
>
> Just a reminder, we need at least one mentor to sign off on the S2 Graph
> report.  If no one can get to it in the next 24 hours I'll need to move the
> podling to monthly and expect a report next month.
>
> John
>

Re: [VOTE] Apache S2Graph(incubating) 0.2.0 release RC2

[DO YUNG YOON]

+1 (non-binding)

I tried RC2 on ubuntu 16.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_91.

Checked followings.

1. Checksums and PGP signatures are valid
2. Release consists of source code only, no binaries
3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
and LICENSE files.
4. Check license header on files by following DEVELOPMENT.md.
5. Test if I can run `bin/example.sh` after build using `sbt package`.
6. `sbt compile`, `sbt test:compile` to see any compile errors.
7. `sbt "project loader" assembly`, `sbt "project s2counter_loader"`
assembly to see executable jar successfully built from source.
8. `sbt test` to see if all test cases passed.

Thanks.

On Mon, Aug 7, 2017 at 5:10 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi all
>
> This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
> candidate 2.
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC2
>
> The tag to be voted upon is v0.2.0-incubating-rc2:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc2
>
> The release hash is 917475b62d68ac952716df5d8ce6465656ec1f25:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=917475b62d68ac952716df5d8ce6465656ec1f25
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
>
> Once download source, please look into README.md to build from source.
>
> Notable changes from 0.1.0 is providing tinkerpop3 integration(S2GRAPH-72,
> S2GRAPH-151).
>
> The vote will be open for at least 72 hours. Unless objection I will try
> to close it Wednesday August 9 if we have sufficient votes.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> please vote:
>
> [ ] +1 Release this package as 0.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks,
> DOYUNG YOON.
>

[CANCELED][VOTE] Apache S2Graph(incubating) 0.2.0 release RC1

[DO YUNG YOON]

This vote has been canceled because of -1 vote and bug.

Re: [VOTE] Apache S2Graph(incubating) 0.2.0 release RC1

[DO YUNG YOON]

-1 (non-binding)

I tried RC1(
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC1/)
on ubuntu 16.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_91.

Checked followings.

1. Checksums and PGP signatures are valid
2. Release consists of source code only, no binaries
3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
and LICENSE files.
4. Check license header on files by following DEVELOPMENT.md.
5. Test if I can run `bin/example.sh` after build.
6. `sbt compile`, `sbt test:compile` to see any compile errors.
7. `sbt "project loader" assembly`, `sbt "project s2counter_loader"`
assembly to see executable jar successfully built from source.
8. `sbt test` to see if all test cases passed.


I found error on 8, more specifically InnerValTest failed on "korean".

I am going to create issue for fixing this and re-open vote thread with RC2
once this bug fixed.



On Mon, Aug 7, 2017 at 2:30 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi all
>
> This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
> candidate 1.
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC1
>
> The tag to be voted upon is v0.2.0-incubating-rc1:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc1
>
> The release hash is cddbaa48290b2d38b1d0f8c6401b0535689f6a49:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=cddbaa48290b2d38b1d0f8c6401b0535689f6a49
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
>
> Once download source, please look into README.md to build from source.
>
> Notable changes from 0.1.0 is providing tinkerpop3 integration(S2GRAPH-72,
> S2GRAPH-151).
>
> The vote will be open for at least 72 hours. Unless objection I will try
> to close it Wednesday August 9 if we have sufficient votes.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> please vote:
>
> [ ] +1 Release this package as 0.2.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks,
> DOYUNG YOON.
>

[VOTE] Apache S2Graph(incubating) 0.2.0 release RC1

[DO YUNG YOON]

Hi all

This is a call for a releasing Apache S2Graph 0.2.0-incubating, release
candidate 1.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.2.0-incubating-RC1

The tag to be voted upon is v0.2.0-incubating-rc1:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.2.0-incubating-rc1

The release hash is cddbaa48290b2d38b1d0f8c6401b0535689f6a49:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=cddbaa48290b2d38b1d0f8c6401b0535689f6a49

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md to build from source.

Notable changes from 0.1.0 is providing tinkerpop3 integration(S2GRAPH-72,
S2GRAPH-151).

The vote will be open for at least 72 hours. Unless objection I will try to
close it Wednesday August 9 if we have sufficient votes.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.2.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

Re: Work on 0.2.0 release has started

[DO YUNG YOON]

I have just created new release branch for 0.2.0-incubating release. Please
continue committing to "master" branch as usual, I will cherry-pick commits
to branch-0.2.0 on per needed basis.

Thanks.

On Fri, Aug 4, 2017 at 8:03 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi guys.
>
> We are staring the process to prepare for S2Graph 0.2.0 release.
>
> I have opend JIRA(https://issues.apache.org/jira/browse/S2GRAPH-156) to
> cover the tasks under 0.2.0 release.
>
> If you have any JIRA in progress and would like to include it in this
> release, please follow the process to do so.
> Feel free to comment on the JIRA if you have any comments/suggestions.
>
> Best Regards.
> DOYUNG YOON
>

Re: Podling Report Reminder - August 2017

[DO YUNG YOON]

I just found out I sent my draft for report to wrong mailing list on Aug.
1. So just want to share it on correct mailing list.

Here is copy of report I attached on WIKI(
https://wiki.apache.org/incubator/August2017).

Please review this.

S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a second release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  * There have been 45 Commits
- All of 45 commits were by single active committers
  * Mailing list has been quite.
- Discuss next release schedule and scope.

How has the project developed since the last report?

  * Focused on Tinkerpop3 integration.
- Added Global Index layer.
- Full text predicate support.
- Provide Gremlin plugin to integrate gremlin-console, gremlin-server.
- S2Graph is now TinkerPop compliant.

  * Discuss next release schedule and scope.
- Agrees to release with Tinkerpop3 integration.
- Release manager is working on building release candidate.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2016-11-01

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
 Comments:
  [ ](s2graph) Seetharam Venkatesh
 Comments:
  [ ](s2graph) Sergio Fernández
 Comments:

IPMC/Shepherd notes:

On Mon, Jul 24, 2017 at 9:07 AM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 August 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, August 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/August2017
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: [DISCUSSION] second release schedule and scope

[DO YUNG YOON]

Seems like everyone agrees on second release and I am going to work on
building release candidates this weekend.

Thanks for testing and giving feedbacks.

On Thu, Aug 3, 2017 at 12:34 PM Hwansung Yu <deejayf...@gmail.com> wrote:

> I checkouted PR 115 (included daewon's commit) and executed the test.
> All test were confirmed to have passed.
>
> And then, I tried running gremlin example and this worked well.
> As you might think, this is enough to release.
>
> You did good job. This PR will make a great contribution to our community
> as well.
>
> Best Regards.
>
> On Wed, Aug 2, 2017 at 3:27 PM, daewon <dae...@apache.org> wrote:
>
> > I agree with the above comments and I agree with the release.
> >
> > On Tue, Aug 1, 2017 at 7:45 PM DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > > Updates on our second release scope and schedule.
> > >
> > > Since Hwansung suggest to resolve tinkerpop related issue before second
> > > release, I was working on the S2GRAPH-151, S2GRAPH-148.
> > >
> > > Currently, S2GRAPH-151 is partially done(2 out of 4 subtasks are done)
> > and
> > > S2GRAPH-148 has PR ready.
> > >
> > > Please review https://github.com/apache/incubator-s2graph/pull/115 .
> > >
> > > As this point, I think we are ready for second release.
> > >
> > > Followings are issues I raised first.
> > >
> > > 1. provide provider optimization, we have none currently.
> > > - S2GRAPH-153 has S2GraphStep optimization that lookup EdgeId/VertexId
> > from
> > > IndexProvider such as Lucene.
> > > - Other optimization can be added on consecutive releases.
> > >
> > > 2. full text search predicate is not currently supported(as @echarles
> > > pointed out)
> > > - S2GRAPH-153 resolve this by using lucene as IndexProvider.
> > > - g.V().has("name", "*steamshon*") will try to find EdgeId/VertexId
> from
> > > IndexProvider then actually lookup Storage for Edge/Vertex.
> > > - IndexProvider interface currently not optimized for large amount of
> > > documents hit, but this can be improved later.
> > >
> > > 3. provide gremlin plugin
> > > - S2GRAPH-148 provide subproject call s2graph-gremlin which contains
> > > S2GraphGremlinPlugin.
> > > - After merging https://github.com/apache/incubator-s2graph/pull/115,
> > > users
> > > can use gremlin-console to try out S2Graph.
> > >
> > > 4. make sure tinkerpop stack works correctly.
> > > - S2GRAPH-148 make sure gremlin-conole is working properly.
> > > - However, I found out it is too tedius to use scala code in
> > > gremlin-console(groovy), so I think creating java client can improve
> > > usability, but this also can be done later.
> > >
> > > In summary, I have resolved tinkerpop related issues, not totally, but
> > just
> > > enough for others to try out.
> > >
> > > I suggest to build our second release candidates at this point if there
> > is
> > > no objection.
> > > I want to hear what others think.
> > >
> > >
> > >
> > > On Sun, Jul 9, 2017 at 10:26 AM DO YUNG YOON <sho...@gmail.com> wrote:
> > >
> > > > Thanks for your feedback. Here is my questions.
> > > >
> > > > 1. Release schedule:
> > > > - Do you think we should wait until all issues with tinkerpop support
> > > > resolved after?
> > > >
> > > > What others think about the release schedule?
> > > >
> > > > Should we wait until all of tinkerpop related issues resolving?
> > > > Can you guys list up "must resolve" issues on our second release?
> > > > The reason I mentioned index is I think it is the only one blocker
> > issue
> > > > from list for next release.
> > > >
> > > > 2. Full-Text search:
> > > > - There would be 2 types of index support with
> > variation(mixed/composite)
> > > > - Graph-Index: s2graph do not have this type of index.
> > > > - Composite-Index
> > > > - Mixed-Index
> > > > - Vertex-Centric-Index: s2graph do have this type of index.
> > > >
> > > >
> > > > Since they are two different type of index, it is inevitable to
> provide
> > > > them as separate option.
> > > >
> > > > I doubt there could be confusion between graph-index and
> > > > ver

Work on 0.2.0 release has started

[DO YUNG YOON]

Hi guys.

We are staring the process to prepare for S2Graph 0.2.0 release.

I have opend JIRA(https://issues.apache.org/jira/browse/S2GRAPH-156) to
cover the tasks under 0.2.0 release.

If you have any JIRA in progress and would like to include it in this
release, please follow the process to do so.
Feel free to comment on the JIRA if you have any comments/suggestions.

Best Regards.
DOYUNG YOON

Re: [DISCUSSION] second release schedule and scope

[DO YUNG YOON]

Updates on our second release scope and schedule.

Since Hwansung suggest to resolve tinkerpop related issue before second
release, I was working on the S2GRAPH-151, S2GRAPH-148.

Currently, S2GRAPH-151 is partially done(2 out of 4 subtasks are done) and
S2GRAPH-148 has PR ready.

Please review https://github.com/apache/incubator-s2graph/pull/115 .

As this point, I think we are ready for second release.

Followings are issues I raised first.

1. provide provider optimization, we have none currently.
- S2GRAPH-153 has S2GraphStep optimization that lookup EdgeId/VertexId from
IndexProvider such as Lucene.
- Other optimization can be added on consecutive releases.

2. full text search predicate is not currently supported(as @echarles
pointed out)
- S2GRAPH-153 resolve this by using lucene as IndexProvider.
- g.V().has("name", "*steamshon*") will try to find EdgeId/VertexId from
IndexProvider then actually lookup Storage for Edge/Vertex.
- IndexProvider interface currently not optimized for large amount of
documents hit, but this can be improved later.

3. provide gremlin plugin
- S2GRAPH-148 provide subproject call s2graph-gremlin which contains
S2GraphGremlinPlugin.
- After merging https://github.com/apache/incubator-s2graph/pull/115, users
can use gremlin-console to try out S2Graph.

4. make sure tinkerpop stack works correctly.
- S2GRAPH-148 make sure gremlin-conole is working properly.
- However, I found out it is too tedius to use scala code in
gremlin-console(groovy), so I think creating java client can improve
usability, but this also can be done later.

In summary, I have resolved tinkerpop related issues, not totally, but just
enough for others to try out.

I suggest to build our second release candidates at this point if there is
no objection.
I want to hear what others think.



On Sun, Jul 9, 2017 at 10:26 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Thanks for your feedback. Here is my questions.
>
> 1. Release schedule:
> - Do you think we should wait until all issues with tinkerpop support
> resolved after?
>
> What others think about the release schedule?
>
> Should we wait until all of tinkerpop related issues resolving?
> Can you guys list up "must resolve" issues on our second release?
> The reason I mentioned index is I think it is the only one blocker issue
> from list for next release.
>
> 2. Full-Text search:
> - There would be 2 types of index support with variation(mixed/composite)
> - Graph-Index: s2graph do not have this type of index.
> - Composite-Index
> - Mixed-Index
> - Vertex-Centric-Index: s2graph do have this type of index.
>
>
> Since they are two different type of index, it is inevitable to provide
> them as separate option.
>
> I doubt there could be confusion between graph-index and
> vertex-centric-index and always clarify it on documentation.
>
> If we agree that graph index layer is necessary, then develop the features
> first, then see if there could be confusion and decide what to do to
> clarify it. I think you agree that graph-index is necessary addition on
> project(tell me if you don't).
>
> Continue on more details on index topic.
>
> Following is what titan provide and I think it would be nice if we can
> provide this in S2Graph so let me briefly explain. (I suggest read through
> http://s3.thinkaurelius.com/docs/titan/1.0.0/indexes.html if you are not
> familiar with notations)
>
> 1. composite
>
> Composite indexes retrieve vertices or edges by one or a (fixed)
> composition of multiple keys.
>
> this example is how user can create composite index on titan.
>
> ```
> mgmt.buildIndex('byNameAndAgeComposite',
> Vertex.class).addKey(name).addKey(age).buildCompositeIndex()
> mgmt.commit()
> ```
>
> then following traversal take benefit from `byNameComposite` index.
>
> ```
> g.V().has('age', 30).has('name', 'hercules')
> ```
>
> We can use HBase to store this index by creating row key as ("age", 30,
> "name", "hercules").
>
> ```
> g.V().has('name', 'hercules').has('age', 30)
> ```
>
> To answer above traveral, it seems to sort property key and value in
> composite index.
>
> we can also make partial composite index such as below.
>
> ```
> ("age", 30)
> ("name", "hercules")
> ```
>
> I am not sure if this is necessary. user can explicitly create above as
> seperate index such as 'byName', 'byAge'.
>
> One more suggestion is provide option to partition index, since there
> could be lots of vertices/edges that has specific value. for example,
> 'byCountryGender' index can contains lots of vertices/edges and it is
> problematic to store vertices/edges on same HBase region. we need to
> auto-partition theses into user

Re: [DISCUSSION] second release schedule and scope

[DO YUNG YOON]

>
> I think it is important to implement Tinkerpop in terms of functionality of
> S2Graph and for the activation of the community.
> I agree with your suggestion to concentrate on tinkerpop implementation
> issues in the second release.
> In my opinion, the time of release is when the tinkerpop implementation
> issue is cleaned up.
>
> And with regard to full text search...
> If full-text search is supported, we expect that constraints that were able
> to traversal will disappear only if the vertex is known.
> If supported, it would be better to leave it as a separate option to avoid
> confusion with existing indexes.
>
> On Sat, Jul 8, 2017 at 9:10 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > I guess there is no objection on my suggestion, so I am going to try list
> > up issues in more detail while preparing 0.2.0 release on late this
> month.
> >
> > Before list up above issues as task on jira, I want to discuss index in
> > more details.
> >
> > Following is my understanding on index to support tinkerpop fully and
> > efficiently
> > - reference: http://s3.thinkaurelius.com/docs/titan/1.0.0/indexes.html
> >
> > 1. graph index: traversal from a list of vertices or edges that are
> > identified by their properties
> >
> > 2. vertex-centric index: traversal through vertices with many incident
> > edges.
> >
> > I believe s2graph has vertex-centric index already, but it does not have
> > graph index layer so full text predicate, and range search features in
> > tinkerpop runs very inefficiently.
> >
> > For example, following traversal run full scan.
> >
> > - g.V().has('name', 'hercules')
> > - g.E().has('reason', textContains('loves'))
> >
> > To support full tinkerpop features efficiently, we need to add graph
> index
> > layer and I want to discuss how we are going to achieve this. like
> > suggested here(http://markmail.org/message/2vn2bwrwh5zbeie4) using
> > external
> > search engine totally make sense to me.
> >
> > I suggest to design index management interface first, since graph index
> has
> > never exist in S2Graph previously. then decision about index storage
> > backend, implementation can be discussed in more detail(the other way
> > around could also possible).
> >
> > Following is how user create index in s2graph currently.
> >
> > Management.createServiceColumn(
> > serviceName = serviceName, columnName = "person", columnType = "integer",
> > props = Seq(
> > Prop("name", "-", "string"),
> > Prop("age", "0", "integer"),
> > Prop("location", "-", "string")
> > )
> > )
> >
> > management.createLabel(
> > label = "bought",
> > srcServiceName = serviceName, srcColumnName = "person",
> srcColumnType =
> > "integer",
> > tgtServiceName = serviceName, tgtColumnName = "product",
> tgtColumnType
> > = "integer", idDirected = true,
> > serviceName = serviceName,
> > indices = Seq(
> > Index("PK", Seq("amount", "created_at")
> > ),
> > props = Seq(
> > Prop("amount", "0.0", "double"),
> > Prop("created_at", "2000-01-01", "string")
> > ),
> > consistencyLevel = "strong"
> > )
> >
> > How we going to let user to create graph-index? Should we add extra
> > parameters on existing methods, or provide separate methods?
> >
> >
> > On Mon, Jul 3, 2017 at 10:11 PM DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > > Hi folks.
> > >
> > > It's been for a while we released our first release.
> > > It seems that needs for implementing tinkerpop interface has been high,
> > > but we have not finished it. I have been working on
> > > https://issues.apache.org/jira/browse/S2GRAPH-136 since April, then
> > > recently merged it into master.
> > >
> > > I think Gremlin-core is tested, but following is what I think we have
> to
> > > improve for tinkerpop users to try out s2graph easily.
> > >
> > > 1. provide provider optimization, we have none currently.
> > > 2. full text search predicate is not currently supported(as @echarles
> > > pointed out)
> > > 3. provide gremlin plugin
> > > 4. make sure tinkerpop stack works correctly.
> > >
> > > A

Re: [DISCUSSION] second release schedule and scope

[DO YUNG YOON]

I guess there is no objection on my suggestion, so I am going to try list
up issues in more detail while preparing 0.2.0 release on late this month.

Before list up above issues as task on jira, I want to discuss index in
more details.

Following is my understanding on index to support tinkerpop fully and
efficiently
- reference: http://s3.thinkaurelius.com/docs/titan/1.0.0/indexes.html

1. graph index: traversal from a list of vertices or edges that are
identified by their properties

2. vertex-centric index: traversal through vertices with many incident
edges.

I believe s2graph has vertex-centric index already, but it does not have
graph index layer so full text predicate, and range search features in
tinkerpop runs very inefficiently.

For example, following traversal run full scan.

- g.V().has('name', 'hercules')
- g.E().has('reason', textContains('loves'))

To support full tinkerpop features efficiently, we need to add graph index
layer and I want to discuss how we are going to achieve this. like
suggested here(http://markmail.org/message/2vn2bwrwh5zbeie4) using external
search engine totally make sense to me.

I suggest to design index management interface first, since graph index has
never exist in S2Graph previously. then decision about index storage
backend, implementation can be discussed in more detail(the other way
around could also possible).

Following is how user create index in s2graph currently.

Management.createServiceColumn(
serviceName = serviceName, columnName = "person", columnType = "integer",
props = Seq(
Prop("name", "-", "string"),
Prop("age", "0", "integer"),
Prop("location", "-", "string")
)
)

management.createLabel(
label = "bought",
srcServiceName = serviceName, srcColumnName = "person", srcColumnType =
"integer",
tgtServiceName = serviceName, tgtColumnName = "product", tgtColumnType
= "integer", idDirected = true,
serviceName = serviceName,
indices = Seq(
Index("PK", Seq("amount", "created_at")
),
props = Seq(
Prop("amount", "0.0", "double"),
Prop("created_at", "2000-01-01", "string")
),
consistencyLevel = "strong"
)

How we going to let user to create graph-index? Should we add extra
parameters on existing methods, or provide separate methods?


On Mon, Jul 3, 2017 at 10:11 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi folks.
>
> It's been for a while we released our first release.
> It seems that needs for implementing tinkerpop interface has been high,
> but we have not finished it. I have been working on
> https://issues.apache.org/jira/browse/S2GRAPH-136 since April, then
> recently merged it into master.
>
> I think Gremlin-core is tested, but following is what I think we have to
> improve for tinkerpop users to try out s2graph easily.
>
> 1. provide provider optimization, we have none currently.
> 2. full text search predicate is not currently supported(as @echarles
> pointed out)
> 3. provide gremlin plugin
> 4. make sure tinkerpop stack works correctly.
>
> Any help on above issues would be highly appreciated(help on any other
> issue would be also highly appreciated).
>
> By the way, What I want to discuss is the schedule and what will be
> included on our second release.
>
> I suggest to focus on integrate with tinkerpop on our second release. It
> would be best if we can address above issues by this month, but I doubt if
> it is possible.
>
> I am suggesting fix our release date on late this month, then focus on
> above issues with high priority. if we can address them all, great, but if
> we can't, then release with version as much as we can deliver in time, then
> move them on next next release so on.
>
> Want to hear what other folks think about focus and schedule on our second
> release, and happy to volunteer as release manager for this time if there
> are no other volunteer.
>
> If there are other issues which anyone think to be included on next
> release, please list them on this thread.
>
> Thanks
>
> DO YUNG YOON
>
>

[DISCUSSION] second release schedule and scope

[DO YUNG YOON]

Hi folks.

It's been for a while we released our first release.
It seems that needs for implementing tinkerpop interface has been high, but
we have not finished it. I have been working on
https://issues.apache.org/jira/browse/S2GRAPH-136 since April, then
recently merged it into master.

I think Gremlin-core is tested, but following is what I think we have to
improve for tinkerpop users to try out s2graph easily.

1. provide provider optimization, we have none currently.
2. full text search predicate is not currently supported(as @echarles
pointed out)
3. provide gremlin plugin
4. make sure tinkerpop stack works correctly.

Any help on above issues would be highly appreciated(help on any other
issue would be also highly appreciated).

By the way, What I want to discuss is the schedule and what will be
included on our second release.

I suggest to focus on integrate with tinkerpop on our second release. It
would be best if we can address above issues by this month, but I doubt if
it is possible.

I am suggesting fix our release date on late this month, then focus on
above issues with high priority. if we can address them all, great, but if
we can't, then release with version as much as we can deliver in time, then
move them on next next release so on.

Want to hear what other folks think about focus and schedule on our second
release, and happy to volunteer as release manager for this time if there
are no other volunteer.

If there are other issues which anyone think to be included on next
release, please list them on this thread.

Thanks

DO YUNG YOON

Re: [DISCUSS] Support Apache TinkerPop and Gremlin

[DO YUNG YOON]

I has been working on this issue for a while, and I finally opened PR that
I believe the right direction(
https://github.com/apache/incubator-s2graph/pull/112).
Please review PR112 and give any feedback.
Here are some important notes on this PR.

1. Data type of property value.

checkout
https://github.com/apache/incubator-s2graph/pull/112/files#diff-8caf8eace8a4d2a42e1b0279d531d286

basically, currently we are only support data type already supported by
s2graph previously. more data type support is also possible, but on
seperate issue later if necessary.

2. No notion of VertexProperty. Property is same on Vertex and Edge in
S2Graph so we have to decide what's our S2VertexProperty would be. Are we
going to support this or just say we can't provide it(for now or what).

checkout
https://github.com/apache/incubator-s2graph/pull/112/files#diff-b64b1af513f07d8e34fb498c7618cf67

currently, only Cardinality.single vertex property is supported.

3. Vertex Id: S2Graph use ServiceColumn + UserProvidedId as internal vertex
Id. We need to decide how we are going to map ServiceColumn into tp3's
Verte. Are we going to serialize/deserialize ServiceColumn into tp3's
Vertex label or not? Not just about ServiceColumn but want to discuss
further about what S2Graph are going to provide through tp3's interface and
how.

checkout
https://github.com/apache/incubator-s2graph/pull/112/files#diff-95ac55266df22a798b8f3ac2d9298ead

it basically specify how to serialize/deserialize S2Graph's VertexId/EdgeId
into Tp3's id() method.

Also here is how to run tp3 test suite.

just run junit test on
org.apache.s2graph.core.tinkerpop.structure.S2GraphStructureStandardTest/org.apache.s2graph.core.tinkerpop.process.S2GraphProcessStandardTest
without any setup.

There are lots of tests so it will take some time.

One thing I found useful for debugging is setting environment variables
GREMLIN_TESTS as test class name such as
org.apache.tinkerpop.gremlin.structure.GraphTest, then it will run the one
test case only.

Also there are a few OptOuts on S2Graph.

Most of them are there because I think it is not currently possible to pass
such test cases. These are solely based on my knowledge so please ask
anything if it seems inappropriate.

Even though I believe that PR112 is valid implementation of tp3 interface,
there are many more things remain.

- TraversalStrategy: we do not have any provider optimization yet(
http://tinkerpop.apache.org/docs/current/reference/#traversalstrategy).
I think there are a few optimization we can provide.

ex) `g.V(vid/v).outE` will lookup graph by vid/v then finally return all
adjacent edges start from this vertex. current implementation in PR use
Await to wait I/O request to storage backend for V(vid/v) one time, then
after that Await S2Vertex.edges method for vertex fetched. this simply
require 2 I/O request, and 2 Await.
in S2Graph this query can be reduced to first create vertext to fetch in
memory, then fire one I/O request to storage backend which I think
efficient.

above is very limited example, but just want to know what others think.

- Global index: checkout http://markmail.org/message/2vn2bwrwh5zbeie4.
While I was going this issue, I noticed S2Graph do not have index provider
layer for global index.

ex) `g.V().has("name", "marko")`. current implementation do not have global
index provider, so it will fetch all vertex and then check if it has
property name as 'mark'.
check out
http://tinkerpop.apache.org/docs/current/reference/#traversalstrategy.
Basically, we need some layer that get traversal, then modify it using
global index. how to build global index is listed on
http://markmail.org/message/2vn2bwrwh5zbeie4.

- GremlinPlugin(https://issues.apache.org/jira/browse/S2GRAPH-148)
For user to try out S2Graph through tinkerpop APIs on Gremlin Console,
Gremlin Server, I believe we should provide `S2GraphGremlinPlugin`.

- OLAP(GraphComputer) support
I have not gone through GraphComputer parts yet(
http://tinkerpop.apache.org/docs/current/reference/#graphcomputer), but I
think s2graph can take benefits from tp3's OLAP framework.


All of above needs some help from community which is very limited
currently.
Please feel free to open issue/discussion on above or any other things we
should think about.

Best Regards.
DOYUNG YOON

On Thu, Nov 24, 2016 at 12:45 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi folks.
>
> After discussion at ApacheCon BigData Europe(sevile), I was wondering if
> it is possible to change S2Graph's core library to implement tp3's
> interface directly rather than providing layer atop of existing codebase.
>
> I have updated corresponding issue
> <https://issues.apache.org/jira/browse/S2GRAPH-72> and create 2 sub tasks(
> S2GRAPH-129 <https://issues.apache.org/jira/browse/S2GRAPH-129> ,
> S2GRAPH-130 <https://issues.apache.org/jira/browse/S2GRAPH-130> ) to try
> out this idea.
>
> @committers, Please 

[DISCUSS] manage our subprojects

[DO YUNG YOON]

Hi folks.

I think we should discuss what we provide as subproject until next release.

Since initial code imports to apache, we have not worked on other
subprojects except s2core, s2rest_play.

Here is what you can find in each subproject(from our README).

   1. s2core: The core library, containing the data abstractions for graph
   entities, storage adapters and utilities.
   2. s2rest_play: The REST server built with Play framework
   , providing the write and query API.
   3. s2rest_netty: The REST server built directly using Netty,
   implementing only the query API.
   4. loader: A collection of Spark jobs for bulk loading streaming data
   into S2Graph.
   5. spark: Spark utilities for loader and s2counter_loader.
   6. s2counter_core: The core library providing data structures and logics
   for s2counter_loader.
   7. s2counter_loader: Spark streaming jobs that consume Kafka WAL logs
   and calculate various top-*K* results on-the-fly.


I want to suggest to merge loader, spark, s2counter_loader into one project
called s2loader, make it responsible for streaming/batch utils to work with
S2Graph.

The reason behind of this is improving codebase(we have lots of duplicate
codes currently and it seems quite abandoned).

Also documentations are missed so we should provide firm documentation to
help others to understand them.

Finally there is no specs and test cases. I think adding test cases is
important because we can start refactor our code to easily testable one.

I have opened discussion thread at
http://markmail.org/message/3j2hbfquwwybyz4e but not enough attention has
been showed, so please give any feedback on this so we can start to work on
our subprojects.

Thanks.

Re: Opinion on the directional index feature provided in ISSUE-123

[DO YUNG YOON]

Hi Daewon.

As far as I understand, you are suggesting to drop `dir` column in
LabelIndex model and let user to specify direction on each option?

I agree that `dir` should be deprecated since what user logically think for
query is based on indexName, not (indexName, dir) pair.
I have +1 on this suggestion.

On Mon, Nov 28, 2016 at 3:06 PM daewon  wrote:

> S2GRAPH-123(https://issues.apache.org/jira/browse/S2GRAPH-123) I have
> opinion on the directional index feature provided in this issue. The
> current implementation creates an 'index edge' according to the 'dir'
> column value (in or out) in the 'label_indices' table. The current
> implementation chooses the first 'index' in 'indices' when querying without
> a proper 'index' name. If the problem is that the query does not give the
> proper index name at the time of the query in the one-step query to the out
> direction, then the query in the two-step query in the direction of in.
> Also, since the existing indexes are changed, 'index_id' is changed for
> newly added indexes. Therefore, there is no way to perform migration when
> you want to no longer use the index for in direction in the label used
> previously. So I suggest changing the implementation as shown below.
> 'Index' is used for both directions as before, but it changes its behavior
> by referring to the value of the 'option' field. {   "In": {
>  "StoreDegree": true,  "StoreIndex": false},   "Out": {
>"StoreDegree": false,"StoreIndex": true   } } If no option
> is given for each direction, it assumes that all values ​​are set to
> 'true'. Thank you.
>

Re: [DISCUSS] Support Apache TinkerPop and Gremlin

[DO YUNG YOON]

I have implemented initial draft based on suggestions.
Jira ISSUE: S2GRAPH-131 <https://issues.apache.org/jira/browse/S2GRAPH-131>
and PR: pull101 <https://github.com/apache/incubator-s2graph/pull/101>.
Please review this and give feedback on what you guys suggested. I think I
understood the VertexLabel parts, but not sure about other suggestions.
More than welcome to comment or send PR.

Other than above issue, I want to start discussion on the Features can be
provided by S2Graph.
This is actually done through override ElementFeatures interface by
provide(as far as I understand), so we need to discuss what features are
available on S2Graph.

DataTypeFeatures
EdgeFeatures
EdgePropertyFeatures
ElementFeatures
GraphFeatures
PropertyFeatures
VariableFeatures
VertexFeatures
VertexPropertyFeatures

I am not an expert on TinkerPop3 so I need more time to ingest what these
features are.
It would be appreciate if anyone who have idea what they are and what kind
of features S2Graph can provide.

Thanks.




On Mon, Nov 28, 2016 at 11:20 AM daewon <dae...@apache.org> wrote:

> Hongki's suggested is most intuitive.
> +1
>
> On Mon, Nov 28, 2016 at 11:08 AM Hyunsung Jo <hyunsung...@gmail.com>
> wrote:
>
> Hi All,
> From the three options that Hongki suggested, using S2Graph serviceName and
> columnName as TinkerPop3 Vertex Label seems like the most intuitive. So +1
> on that.
>
> Regards,
> Jo
>
> On Fri, Nov 25, 2016 at 12:50 PM hongki kim <reinhardh...@gmail.com>
> wrote:
>
> > I concluded my thoughts briefly, and I agree that the details are
> lacking.
> > Let me write a little more detail.
> >
> >
> >  - The Vertex attribute allows individual filtering but is inconvenient
> > I enter the code to encourage this props is not natural, I think.
> > Serialize / Deserialize will cost more.
> > The following example is an individual filtering of the ServiceName and
> > ColumnName I think.
> > Ex) g.V (). Has ( "serviceName", "gogo")
> >
> > => I think that Vertex Property uses java.util.Map, and the string
> > "serviceName" and "columName" should always be serialized together. Of
> > course, you can also use "_s" or "_c". And I worry that it will be used
> as
> > a reserved Property Key with only s2graph.
> >
> >
> > - If you put a serviceColumn in the id, it will be cumbersome to compare
> > The id value itself or to the operation like "summary".
> >
> >
> > => My English skills were not very good, so I guess it was not accurate.
> > What I was concerned about was that when I set up several vertex ids, I
> was
> > worried that gremlin would list them with the following expression:
> > Ex) g.V(new S2VertexId (1,"gogo", "userid"), new S2VertexId (2,"gogo",
> > "userid") )
> >
> > Also, I was wondering if the following operation would work in the
> summary
> > part. The idea is that the S2VertexId object needs to return the actual
> id.
> > Ex) g.V().id().sum() #tp3
> >   g.V().id().id().sum()  # s2graph (with S2VertexId)
> >
> >
> >
> > Thanks for reading
> >
> >
> >
> >
> >
> > 2016-11-24 22:57 GMT+09:00 DO YUNG YOON <sho...@gmail.com>:
> >
> > > Hi 김홍기 and Welcome to the S2Graph.
> > >
> > > It seems that you already know internal model that S2Graph is using but
> > let
> > > me explain it for others who are not familiar with it to discuss issue
> 3
> > in
> > > more detail.
> > >
> > > Instead of convert user provided Id into internal unique numeric Id,
> > > S2Graph simply composite service and column metadata with user provided
> > Id
> > > to guarantee global unique Id.
> > > Here are some important notation.
> > >
> > > 1. Service - the top level abstraction
> > >   - A convenient logical grouping of related entities
> > >   - Similar to the database abstraction that most relational databases
> > > support.
> > >
> > > 2. Column - belongs to a service.
> > >   - A set of homogeneous vertices such as users, news articles or tags.
> > >   - Every vertex has a user-provided unique ID that allows the
> efficient
> > > lookup.
> > >   - A service typically contains multiple columns.
> > >
> > > 3. Label - schema for edge
> > >   - A set of homogeneous edges such as friendships, views, or clicks.
> > >   - Relation between two columns as well as a recursive association
> > within
> >

Re: [DISCUSS] Support Apache TinkerPop and Gremlin

[DO YUNG YOON]

Hi 김홍기 and Welcome to the S2Graph.

It seems that you already know internal model that S2Graph is using but let
me explain it for others who are not familiar with it to discuss issue 3 in
more detail.

Instead of convert user provided Id into internal unique numeric Id,
S2Graph simply composite service and column metadata with user provided Id
to guarantee global unique Id.
Here are some important notation.

1. Service - the top level abstraction
  - A convenient logical grouping of related entities
  - Similar to the database abstraction that most relational databases
support.

2. Column - belongs to a service.
  - A set of homogeneous vertices such as users, news articles or tags.
  - Every vertex has a user-provided unique ID that allows the efficient
lookup.
  - A service typically contains multiple columns.

3. Label - schema for edge
  - A set of homogeneous edges such as friendships, views, or clicks.
  - Relation between two columns as well as a recursive association within
one column.
  - The two columns connected with a label may not necessarily be in the
same service, allowing us to store and query data that spans over multiple
services.


>From your suggestion, here is what I thought.

1. Put the ServiceName and columnName in the vertex property
ex) graph.addVertex(T.Id, 1, "serviceName". "gogo", columnName , "user")

2. Replace tp3 id with S2graph VertexId (ServiceName, columnName, id)
ex) graph.addVertex(T.Id, new S2VertexId(1, "gogo", "user"))

3. Use Vertex Label
ex) graph.addVertex(T.label, "gogo::user", T.id, 1 )

First of all, I think if we ignore Service and Column on vertex, then there
is no way to guarantee the global uniqueness of id 1. If my service has
user id 1 and your service has user id 1, then there is no way to distinguish
same 1 without Service and Column, so I think ignoring them is not an
option for us.

I am +1 on Use Vertex Label to map S2Graph's Service, Column notation into
tp3 in general and forcing user to provide vertex label on vertex.

Concatenate serviceName and columnName with "::" does not looks like best
for me, but it should be fine, since client users will never need to
separate serviceName and columnName from given string. existing users of
Tinkerpop should be familiar with vertex label notation so I think it is
best option.

Also I think being more explicit also make sense, so option 2 seems ok for
me too. users can be notified by thrown exception if they not provide
S2VertexId type for T.id value, but this is not as familiar as vertexLabel.

By the way, I don't quite understand the reasons you mentioned below, so
can you please elaborate them one more time?

- Using the vertex property allows individual filtering but is inconvenient
to input, and the code that forces this props is unnatural and I think it
will cost more in Serialize / Deserialize
- If you put a serviceColumn in the id, it will be cumbersome to compare
the id value itself or to perform the operation like "summary".

Thanks for your suggestion and participation in this community.

Folks, Any more thought?

On Thu, Nov 24, 2016 at 8:05 PM 김홍기 <reinhardh...@gmail.com> wrote:

> hi,
>
> I think about issue 3, as below.
>
> ServiceColumn does not exist in tp3 but exists only in s2graph.
> There are several ways to apply to tp3.
>
> - Put the ServiceName and columnName in the vertex property
> ex) graph.addVertex(T.Id, 1, "serviceName". "gogo", columnName , "user")
>
> - Replace tp3 id with S2graph VertexId (ServiceName, columnName, id)
> ex) graph.addVertex(T.Id, new S2VertexId(1, "gogo", "user"))
>
> - Use Vertex Label
> ex) graph.addVertex(T.label, "gogo::user", T.id, 1 )
>
> - Ignore ServiceColumn on Vertex because edge label contains a
> ServiceColumn relationship
> ex) greaph.addVertex(T.id, 1)
>
>
> I think VertexLabel is a good choice for some reason.
>
> - Using the vertex property allows individual filtering but is inconvenient
> to input, and the code that forces this props is unnatural and I think it
> will cost more in Serialize / Deserialize
> - If you put a serviceColumn in the id, it will be cumbersome to compare
> the id value itself or to perform the operation like "summary".
> - Ignoring the service column makes it easier to access different types of
> edges, but there is a problem of data integrity
>
>
>
>
> --
>
>
>
> From: DO YUNG YOON <sho...@gmail.com>
> To: s2graph-dev <dev@s2graph.incubator.apache.org>
> Cc:
> Date: Thu, 24 Nov 2016 03:44:36 +
> Subject: [DISCUSS] Support Apache TinkerPop and Gremlin
> Hi folks.
>
> After discussion at ApacheCon BigData Europe(sevile), I was wondering if it
&

Re: [DISCUSS] milestone for next release.

[DO YUNG YOON]

Based on lazy consensus(
https://www.apache.org/foundation/voting.html#LazyConsensus), I assumes
that others agree on our next release target. I am going to work on Basic
implementation for Tinkerpop3.

Please jump on this issue(https://issues.apache.org/jira/browse/S2GRAPH-80)
if anyone interested.
Just wondering if there is any others who are interested in Various Storage
Backend.

On Fri, Nov 4, 2016 at 9:31 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Would love to see S2Graph integrate with Zepplin just like neo4j
> https://github.com/apache/zeppelin/pull/1582.
> Let me first take time to look around what is requirement on S2Graph side
> to make this happen by go through PR and we can add Zepplin integration on
> milestone for next release.
> Thanks for your suggestion!
>
>
> On Fri, Nov 4, 2016 at 7:27 AM Hyunsung Jo <hyunsung...@gmail.com> wrote:
>
> Hi Doyung,
>
> There was a recent PR in Zeppelin to integrate with Neo4j. (
> https://github.com/apache/zeppelin/pull/1582)
> Something like this for S2Graph might interest both the dev + user
> community.
> Although, technically it would be a code contribution to Zeppelin rather
> than S2Graph.
>
> Regards,
> Jo
> On Fri, Nov 4, 2016 at 1:52 AM DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi all.
> >
> > I think it is time for us to build consensus on milestone for next
> release.
> > Let me suggest few to start this discussion.
> >
> > 1. Basic implementation for Tinkerpop3.
> >
> > Many people already asked if they can use S2Graph with tinkerpop. I have
> > played around at https://issues.apache.org/jira/browse/S2GRAPH-72 issue,
> > but never polished it yet. I am thinking about provide java client that
> > implement tinkerpop3 interface by call s2graph core, because java has
> much
> > wide range of users and it also can be used by scala users too.
> >
> > Also I have realized that we can take advantage of tinkerpop's
> > OLAP(Hadoop-Gremlin) ability by providing layer translating GraphIO
> between
> > S2Graph's format to Tinkerpop's format.
> >
> > Also I think existing userbase for gremlin-console, gremlin-server can
> take
> > benefits from this and we may hopefully increase our reach to more broad
> > audience.
> >
> > 2. Various Storage Backend.
> >
> > We have tested if our interface is pluggable for storage backend by
> playing
> > around RocksDBStorage. I think it is time for us actually provide more
> > storage backend plugins so users who do not use HBase can also be benefit
> > from S2Graph.
> >
> > Many startup users who contact me asked if they can use S2Graph with
> mysql,
> > postgresql, and redis. Actually, we have implemented RedisStorage
> > once(S2GRAPH-1), but never merged PR. Since then, our interface has been
> > changed so we need to make sure this awesome PR included into our
> codebase.
> >
> > I think working on storage backend plugin is great way to interact with
> > code base, so I encourage others(especially committers) to try out this.
> >
> > I am thinking of followings.
> > - Any system that JDBC can talk to.
> > - postgresl
> > - mysql
> > - etc...
> > - Cassandra(for big graph).
> > - Redis(S2GRAPH-1, for small graph).
> > - etc...
> >
> > Personally I think this is most important discussion for now since anyone
> > interested in S2Graph can see where we are heading and hopefully
> encourage
> > more developers to participate in S2Graph.
> >
> > Please feel free to give any feedback and comment and hope to discuss
> this
> > further with all.
> >
> > Thanks
> > DOYUNG YOON
> >
>
>

Re: Board Report

[DO YUNG YOON]

Thanks for reminding us John.
I submit our board report and updated wiki yesterday.


Following is our report for November.

S2GraphS2Graph is a distributed and scalable OLTP graph database built
on ApacheHBase to support fast traversal of extremely large
graphs.S2Graph has been incubating since 2015-11-29.Three most
important issues to address in the move towards graduation:  1. Make a
release  2. Attract users and contributors  3. Foster more and diverse
committersAny issues that the Incubator PMC (IPMC) or ASF Board
wish/need to beaware of?  NoneHow has the community developed since
the last report?  * Held two sessions on S2Graph: usecases *
Deview: https://deview.kr/2016/schedule#session/160* TechPlanet:
http://techplanet.skplanet.com/eng/speaker_track2.html#spk_trk2_5  *
Started to discuss overhauling the website layout and contentsHow has
the project developed since the last report?  * The first Apache
release has been released on 2016-11-01.  * 30 issues are created, 32
issues are resolved.Date of last release:  Apache S2Graph
0.1.0-incubating on 2016-11-01.When were the last committers or PMC
members elected?  NoSigned-off-by:  [ ](s2graph) Andrew Purtell  [
](s2graph) Seetharam Venkatesh  [ ](s2graph) Sergio
FernándezShepherd/Mentor notes:




On Thu, Nov 3, 2016 at 7:18 AM John D. Ament  wrote:

> S2Graph Podling,
>
> Please don't forget to submit your board report by end of day.
>
> John
>

[ANNOUNCE] Apache S2Graph 0.1.0-incubating release

[DO YUNG YOON]

The Apache S2Graph team is pleased to announce the release of Apache
S2Graph 0.1.0-incubating.

Apache S2Graph(incubating) is a graph database designed to handle
transactional graph processing at scale. Its REST API allows you to store,
manage and query relational information using edge and vertex
representations in a fully asynchronous and non-blocking manner.

0.1.0-incubating publishes the first set of Apache S2Graph source code,
making them readily available for our users. The initial release includes
scala client, REST server, Bulk Loader, along with the support for one
storage backend: Apache HBase.

If you'd like to download the source release, you can find it here:
http://mirror.navercorp.com/apache/incubator/s2graph/0.1.0-incubating/

More details on Apache S2Graph can be found at:
http://s2graph.incubator.apache.org/

We would like to thank all contributors who made the release possible, and
encourage anyone interested in using or contributing to the project to join
the dev mailing list(mailto:dev-subscr...@s2graph.incubator.apache.org)

Regards,
Apache S2Graph (incubating) Community


DISCLAIMER

Apache S2Graph is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.

Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects.

While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

Re: [RESULT][VOTE] Release Apache S2Graph 0.1.0-incubation RC6

[DO YUNG YOON]

Hi Sergio.
Thanks for clarifying.
Then I guess all we need to do is sending announce through mailing list for
0.1.0-incubating, then start work on next release ^^.

I checked release on
https://dist.apache.org/repos/dist/release/incubator/s2graph/, and also
checked if it is mirrored on
http://apache.mirror.cdnetworks.com/incubator/s2graph/0.1.0-incubating/

Finally I download release and follow steps on readme for build from
source(`sbt package`) then test bin/example.sh and all seems good.

Unless objection, I will send official announce tomorrow after read through
https://lists.apache.org/list.html?annou...@apache.org tonight.

Thanks
DO YUNG


On Mon, Oct 31, 2016 at 3:14 PM Sergio Fernández <
sergio.fernan...@redlink.co> wrote:

> (travelling with limited connectivity)
>
> Guys, I guess 0.1.0-incubating would be just a source release. You can't
> modify the source that have been voted to release the Maven binary
> artifacts. Therefore that needs to be done in a new release, 0.1.1 if you
> just want to address the Maven packaging with no new features, 0.2.0 if you
> want to wait for new stuff.
>
> BTW, repositoy.apache.org is synced with Maven Central. You should have
> access with you ASF accounts, so you can start to push snapshots there
> whenever the issue is fixed.
>
> On Oct 30, 2016 07:30, "Jong Wook Kim" <jongw...@nyu.edu> wrote:
>
> > S2GRAPH-115 is for the maven central upload, which is a separate problem
> > with the binary release
> >
> > The binary release is what we make using ‘sbt package’, which should make
> > easier for the first-time users to download and try out S2Graph; so I
> > thought it would be nice to put this along with the announcement.
> >
> > Anyone can run ‘sbt package’, and it should be good to go, preferably
> > after some testing on various OSX/linux platforms.
> >
> > BTW, as per S2GRAPH-115, I’m still figuring out how to do a Maven Central
> > upload, any clarification would be appreciated.
> >
> > JW
> >
> > > On Oct 30, 2016, at 1:29 AM, DO YUNG YOON <sho...@gmail.com> wrote:
> > >
> > > I just uploaded RC6 into
> > > https://dist.apache.org/repos/dist/release/incubator/s2graph/
> > > I guess we need one day waiting while mirrors set up.
> > >
> > > @JW.
> > >
> > > I created tag 'v0.1.0-incubating', and removed RC tags.
> > >
> > > Depends on if how we are going to release binary to asf nexus, I think
> we
> > > need to change build.sbt so did not changed version in build.sbt yet.
> > >
> > > Regarding to binary release, can anyone(I think JW is already helping
> > out)
> > > help me figure out how to resolve S2GRAPH-115 ?
> > >
> > > One last question is should we announce 0.1.0 release or wait until
> > binary
> > > goes to asf nexus?
> > >
> > > Thanks.
> > > DOYUNG YOON
> > >
> > > On Sat, Oct 29, 2016 at 3:28 PM Jong Wook Kim <jongw...@nyu.edu>
> wrote:
> > >
> > > Hi,
> > >
> > > I don’t think any further actions happened since the passing vote
> email.
> > >
> > > So what comes in my mind for the next steps are:
> > >
> > > - tag v0.1.0 and remove the RC tags
> > > - update the version in build.sbt to 0.1.1-SNAPSHOT
> > > - upload the source release to ASF mirrors, and the binary release as
> > well,
> > > if possible. - the instructions are here <
> > > http://incubator.apache.org/guides/releasemanagement.html#
> > understanding-distribution
> > >>
> > > - publish the binary and source JAR to the Maven Central.
> > > - announce the release and post the download links to mailing lists, at
> > the
> > > s2graph website, etc.
> > >
> > > As for the Maven Central release, we have S2GRAPH-115 <
> > > https://issues.apache.org/jira/browse/S2GRAPH-115> open for doing
> that,
> > and
> > > I have a few questions (@sergio):
> > >
> > > - I saw these instructions <
> > > http://incubator.apache.org/guides/release-java.html>, which are
> largely
> > > incomplete. We need to know how to get access for using
> > org.apache.s2graph
> > > groupId. Do we need to file a ticket to Sonatype OSSRH <
> > > http://central.sonatype.org/pages/ossrh-guide.html>, or does ASF have
> a
> > > separate mechanism for Maven Central publishing?
> > > - What are the rules that the POMs and JARs should strictly follow?
> ASF’s
> > > instruction <
> > > http://incubator.ap

Re: [RESULT][VOTE] Release Apache S2Graph 0.1.0-incubation RC6

[DO YUNG YOON]

I just uploaded RC6 into
https://dist.apache.org/repos/dist/release/incubator/s2graph/
I guess we need one day waiting while mirrors set up.

@JW.

I created tag 'v0.1.0-incubating', and removed RC tags.

Depends on if how we are going to release binary to asf nexus, I think we
need to change build.sbt so did not changed version in build.sbt yet.

Regarding to binary release, can anyone(I think JW is already helping out)
help me figure out how to resolve S2GRAPH-115 ?

One last question is should we announce 0.1.0 release or wait until binary
goes to asf nexus?

Thanks.
DOYUNG YOON

On Sat, Oct 29, 2016 at 3:28 PM Jong Wook Kim <jongw...@nyu.edu> wrote:

Hi,

I don’t think any further actions happened since the passing vote email.

So what comes in my mind for the next steps are:

- tag v0.1.0 and remove the RC tags
- update the version in build.sbt to 0.1.1-SNAPSHOT
- upload the source release to ASF mirrors, and the binary release as well,
if possible. - the instructions are here <
http://incubator.apache.org/guides/releasemanagement.html#understanding-distribution
>
- publish the binary and source JAR to the Maven Central.
- announce the release and post the download links to mailing lists, at the
s2graph website, etc.

As for the Maven Central release, we have S2GRAPH-115 <
https://issues.apache.org/jira/browse/S2GRAPH-115> open for doing that, and
I have a few questions (@sergio):

- I saw these instructions <
http://incubator.apache.org/guides/release-java.html>, which are largely
incomplete. We need to know how to get access for using org.apache.s2graph
groupId. Do we need to file a ticket to Sonatype OSSRH <
http://central.sonatype.org/pages/ossrh-guide.html>, or does ASF have a
separate mechanism for Maven Central publishing?
- What are the rules that the POMs and JARs should strictly follow? ASF’s
instruction <
http://incubator.apache.org/guides/release-java.html#jar-manifest> page is
just full of TODOs and doesn’t look very authoritative.

Thanks,
JW



> On Oct 27, 2016, at 9:23 AM, Sergio Fernández <wik...@apache.org> wrote:
>
> Do Yung, have you check the release has been already mirrored?
>
> Then it's time for announce it:
>
> * Minimum it should go to the mailing lists (dev@s2graph,
general@incubator,
> announce@apache); it's a good opportunity to reach a broader audience, so
> follow the example by others:
> https://lists.apache.org/list.html?annou...@apache.org
>
> * Also spread the work in Twitter or whatever creates some traction.
>
> Thanks.
>
>
> On Tue, Oct 25, 2016 at 8:44 AM, Sergio Fernández <wik...@apache.org>
wrote:
>
>> Good work, guys!
>>
>> Finally did you push binary maven artifacts to asf nexus? In that case
>> wait until they get mirrored http://search.maven.
>> org/#search%7Cga%7C1%7Cs2graph before doing the official announcement.
>>
>> On Tue, Oct 25, 2016 at 4:56 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>>
>>> The vote for releasing Apache S2Graph 0.1.0-incubating passed with 3
>>> binding +1s, 4 non-binding +1s, and no 0 or -1.
>>>
>>> Binding +1s:
>>> Justin Mclean
>>> Sergio Fernández
>>> Michael Stack
>>>
>>> Thanks to everyone that tested our release and voted.
>>>
>>> DOYUNG YOON
>>>
>>
>>
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925 <+43%20660%202747925>
>> e: sergio.fernan...@redlink.co
>> w: http://redlink.co
>>
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925 <+43%20660%202747925>
> e: sergio.fernan...@redlink.co
> w: http://redlink.co

[RESULT][VOTE] Apache S2Graph(incubating) 0.1.0 release RC6

[DO YUNG YOON]

Hi all.
After being opened for over 72 hours, the vote for releasing Apache S2Graph
0.1.0-incubating RC6 passed with following result.

+1 binding
- Sergio Fernández

+1 non-binding
- DO YUNG YOON
- Jong Wook Kim
- Daewon Jung
- Hwansung Yu

There was no -1 and 0.

I am going to create a vote in the general@ list.
Thanks.

[VOTE] Apache S2Graph(incubating) 0.1.0 release RC6

[DO YUNG YOON]

Hi all

This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
candidate 6.
This is the first release of S2Graph.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC6/

The tag to be voted upon is v0.1.0-incubating-rc6:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc6

The release hash is 4325ff1303ce606909bc16b5cbee53c8a5b23653:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=4325ff1303ce606909bc16b5cbee53c8a5b23653


Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md to build from source.

Following issues are resolved.

- S2GRAPH-117: Cleaner logging library usage.
- S2GRAPH-118: Fix compile error on test cases on loader project.
- S2GRAPH-120: Netty version is conflict with play 2.5.9.


The vote will be open for at least 72 hours. Unless objection I will try to
close it Sunday September 25 if we have sufficient votes.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

[CANCEL][VOTE] Apache S2Graph(incubating) 0.1.0 release RC5

[DO YUNG YOON]

This vote closed with two +1(one binding, one non binding), one 0(non
binding), one -1(non binding).

Due to following reasons, vote for 0.1.0 release RC5 canceled.

1. logging facade(S2GRAPH-117)
2. sbt “project loader” test:compile fail(S2GRAPH-118)

Detailed discussion can be found at
https://lists.apache.org/thread.html/0b890cf7a23eff4d981a42d57ce3ccc12b9d9e9b07298a832be1741f@%3Cdev.s2graph.apache.org%3E

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC5

[DO YUNG YOON]

+1 (non-binding)

I tried RC5 on ubuntu 16.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_91.

Checked followings.

1. Checksums and PGP signatures are valid
2. Release consists of source code only, no binaries
3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
and LICENSE files.
4. Check license header on files.
5. Test if I can run `bin/example.sh` after build.

Thanks.

On Tue, Oct 4, 2016 at 2:13 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi all
>
> This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
> candidate 5.
> This is the first release of S2Graph.
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC5/
>
>
> The tag to be voted upon is v0.1.0-incubating-rc5:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc5
>
> The release hash is 4b6ffc2e357afc005b194d6d45710c2b041b00cb:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=4b6ffc2e357afc005b194d6d45710c2b041b00cb
>
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
>
> Once download source, please look into README.md to build from source.
>
> Notable changes from RC4 is removing custom repo for asynchbase dependency(
> S2GRAPH-116 <https://github.com/apache/incubator-s2graph/pull/85>).
>
> The vote will be open for at least 72 hours. Unless objection I will try
> to close it Sunday September 25 if we have sufficient votes.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> please vote:
>
> [ ] +1 Release this package as 0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks,
> DOYUNG YOON.
>
>

[VOTE] Apache S2Graph(incubating) 0.1.0 release RC5

[DO YUNG YOON]

Hi all

This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
candidate 5.
This is the first release of S2Graph.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC5/


The tag to be voted upon is v0.1.0-incubating-rc5:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc5

The release hash is 4b6ffc2e357afc005b194d6d45710c2b041b00cb:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=4b6ffc2e357afc005b194d6d45710c2b041b00cb


Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md to build from source.

Notable changes from RC4 is removing custom repo for asynchbase dependency(
S2GRAPH-116 ).

The vote will be open for at least 72 hours. Unless objection I will try to
close it Sunday September 25 if we have sufficient votes.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

[Result]

This vote close with one +1(binding), and three +1(non-binding).

Even though we agree to cast RC4 on general mailing list, there were few
issues we would better resolve.
(mainly about custom repository as dependency for asynchbase).

I am to resolve above issues then create RC5 soon.

Thanks for everyone taking time to check RC4.

On Mon, Oct 3, 2016 at 3:55 PM Sergio Fernández <wik...@apache.org> wrote:

> If with that we could get 0.1.0-incubating published to Maven central, then
> it'd be worth.
>
> If so, please Do Yung, cancel this vote.
>
> On Sat, Oct 1, 2016 at 4:55 PM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi folks.
> >
> > As we have discussed on this vote thread, and here
> > <https://lists.apache.org/thread.html/221df53842697da30c2def01221023
> > 3a1b89cc4c0a3d267454713d4b@%3Cdev.s2graph.apache.org%3E>,
> > I thought it would be better to resolve custom asynchbase dependency
> > issue(S2GRAPH-115, S2GRAPH-116) before posting our RC4 on general mailing
> > list.
> >
> > Thanks to JongWook's contribution, we have finally removed custom
> > asynchbase dependency and now s2graph use only dependencies from maven
> > central.
> > I applied these changes and created RC5 at
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> > 1.0-incubating-RC5/
> >
> >
> > Unless objection, I will close this vote for RC4 and create new RC5 vote
> > thread.
> >
> > On Tue, Sep 27, 2016 at 2:59 PM Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > On Tue, Sep 27, 2016 at 5:48 AM, DO YUNG YOON <sho...@gmail.com>
> wrote:
> > > >
> > > > 2. asynchbase dependency in the POM
> > > >
> > > > Like you point out, users who want to download S2Graph as dependency
> > from
> > > > Maven central will fail.
> > > >
> > > > During incubating process, we only release our source code, not
> binary,
> > > so
> > > > I don't think it is a blocker(Please correct me if I am wrong).
> > > >
> > >
> > > Well, that's not completely right, because: Although it is true the
> > source
> > > is the single binding release, normally projects also publish binary
> > > artifacts to help on its usage/adoption. That's valid for top-level
> > > projects as well as for incubating podlings: incubating releases should
> > be
> > > 100% what you'll do after graduation, just its voting process requires
> > some
> > > more intervention by IPMC.
> > >
> > > Therefore that's a non-blocking for releasing 0.1.0 RC4, because source
> > > release can be build without using such custom dependency.
> > >
> > > BTW, what is org.hbase:asynchbase:1.7.2-S2GRAPH? Where does it come
> > from?
> > > Why is not on Maven Central? If it's a fork from AL2 code that it's
> only
> > > relevent for S2Graph, you could donate it to the S2Graph podling to
> have
> > an
> > > easier way to deal with that dependency.
> > >
> > >
> > >
> > > > Of course It would be great to find out work around for this issue,
> but
> > > > since my lack of knowledge and experience, I have no idea how to
> > resolve
> > > > this except sending PR to asynchbase upstream and hope PR get merged
> > and
> > > > next release of asynchbase contains it.
> > >
> > >
> > > Yes, it would be nice that upcoming releases would provide Maven
> > artifacts
> > > too. I've registered S2GRAPH-115 for tracking that.
> > >
> > > Cheers,
> > >
> > >
> > > --
> > > Sergio Fernández
> > > Partner Technology Manager
> > > Redlink GmbH
> > > m: +43 6602747925
> > > e: sergio.fernan...@redlink.co
> > > w: http://redlink.co
> > >
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

Hi folks.

As we have discussed on this vote thread, and here
<https://lists.apache.org/thread.html/221df53842697da30c2def012210233a1b89cc4c0a3d267454713d4b@%3Cdev.s2graph.apache.org%3E>,
I thought it would be better to resolve custom asynchbase dependency
issue(S2GRAPH-115, S2GRAPH-116) before posting our RC4 on general mailing
list.

Thanks to JongWook's contribution, we have finally removed custom
asynchbase dependency and now s2graph use only dependencies from maven
central.
I applied these changes and created RC5 at
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC5/


Unless objection, I will close this vote for RC4 and create new RC5 vote
thread.

On Tue, Sep 27, 2016 at 2:59 PM Sergio Fernández <wik...@apache.org> wrote:

> Hi,
>
> On Tue, Sep 27, 2016 at 5:48 AM, DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > 2. asynchbase dependency in the POM
> >
> > Like you point out, users who want to download S2Graph as dependency from
> > Maven central will fail.
> >
> > During incubating process, we only release our source code, not binary,
> so
> > I don't think it is a blocker(Please correct me if I am wrong).
> >
>
> Well, that's not completely right, because: Although it is true the source
> is the single binding release, normally projects also publish binary
> artifacts to help on its usage/adoption. That's valid for top-level
> projects as well as for incubating podlings: incubating releases should be
> 100% what you'll do after graduation, just its voting process requires some
> more intervention by IPMC.
>
> Therefore that's a non-blocking for releasing 0.1.0 RC4, because source
> release can be build without using such custom dependency.
>
> BTW, what is org.hbase:asynchbase:1.7.2-S2GRAPH? Where does it come from?
> Why is not on Maven Central? If it's a fork from AL2 code that it's only
> relevent for S2Graph, you could donate it to the S2Graph podling to have an
> easier way to deal with that dependency.
>
>
>
> > Of course It would be great to find out work around for this issue, but
> > since my lack of knowledge and experience, I have no idea how to resolve
> > this except sending PR to asynchbase upstream and hope PR get merged and
> > next release of asynchbase contains it.
>
>
> Yes, it would be nice that upcoming releases would provide Maven artifacts
> too. I've registered S2GRAPH-115 for tracking that.
>
> Cheers,
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: Including asynchbase in the sourcetree

[DO YUNG YOON]

Hi, Jong Wook.

1. Good point.

I think  we set column family when create GetRequest(
https://github.com/apache/incubator-s2graph/blob/master/s2core/src/main/scala/org/apache/s2graph/core/storage/hbase/AsynchbaseStorage.scala#L249)
 and Scanner(
https://github.com/apache/incubator-s2graph/blob/master/s2core/src/main/scala/org/apache/s2graph/core/storage/hbase/AsynchbaseStorage.scala#L202
).

So ColumnPaginateFilter itself is not same with storeLimit/Offset
functionality wise, but in our case, it should suffice because we only
scanning one column family at a time.

2. I think your suggestion is much simpler and +1 on avoiding touching
HBaseClient.java.

So as far as I understand, we can do following steps.

1. change custom asynchbase dependency to official asynchbase.
2. make changes on s2graph core to apply Jong Wook's suggestion.

Please give any other thought if you guys have different opinion on this.

@JongWook, Can you create JIRA issue and send PR for this?(unless object).






On Thu, Sep 29, 2016 at 4:18 AM Jong Wook Kim <jongw...@nyu.edu> wrote:

> Hi, thanks for sharing the opinions,
>
> 1.
>
> It seems that GetRequest.storeLimit/Offset applies per column family and
> ColumnPaginationFilter can be applied across multiple column families.
>
> So I’m not sure if they are functionally equivalent, but if that’s what we
> want, I guess ColumnPaginationFilter should suffice.
>
>
> 2.
>
> You added an overloaded scanNextRows(Scanner, int) that differs from
> scanNextRows(Scanner) by only a single line.
>
> Like I did here <
> https://github.com/jongwook/incubator-s2graph/blob/feature/patched-asynchbase/s2core/src/main/scala/org/hbase/async/ScannerExtra.scala#L38-L40>,
> we can avoid touching HBaseClient.java by editing
> Scanner.getNextRowsRequest. So this should be simpler; please let me know
> if I’m missing something.
>
>
> JW
>
>
> > On Sep 28, 2016, at 10:41 AM, DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > Hi Jong Wook.
> >
> > Thanks for casting this issue and working on it.
> > I took some time today, to clear the custom patches and find out
> followings.
> >
> > 1. GetRequest.setMaxResultsPerColumnFamily/setRowOffsetPerColumnFamily
> > methods.
> >
> > I think we do not actually need this method which only exist on our
> custom
> > patch.
> > Instead of using custom method on GetRequest, I think we can use
> FilterList.
> > Please check out this commit.
> >
> https://github.com/apache/incubator-s2graph/compare/master...SteamShon:asynchbase_path?expand=1
> >
> >
> > 2. Scanner.setTimeout.
> >
> > Please note that in
> >
> https://github.com/apache/incubator-s2graph/compare/master...SteamShon:asynchbase_path?expand=1
> ,
> > I commented out scanner.setTimeout.
> > Current upstream Asynchbase does not allow user to set timeout on
> scanner.
> > I am going to create issue and send following commits as a PR to
> upstream.
> > Please check out
> >
> https://github.com/OpenTSDB/asynchbase/compare/master...SteamShon:scanner_timeout?expand=1
> >
> > In my humble opinion, while we are waiting on issue on 2 discussed,
> merged,
> > and finally released by asynchbase guys, I think it is reasonable to use
> > your suggested patch for our first release.
> >
> >
> > On Wed, Sep 28, 2016 at 6:25 AM Jong Wook Kim <jongw...@nyu.edu> wrote:
> >
> >> I managed to created a version using ASM and ByteBuddy to do the
> >> patchwork:
> >>
> https://github.com/jongwook/incubator-s2graph/commit/770917e0c05228ba0855c16e417436bcc67ff412
> >> <
> >>
> https://github.com/jongwook/incubator-s2graph/commit/770917e0c05228ba0855c16e417436bcc67ff412
> >.
> >> It does:
> >>
> >> - Use ASM to remove the final modifiers of GetRequest and Scanner, and
> >> make all of their methods public
> >> - Dynamically create a subclass of GetRequest, that supports the
> >> limit/offset by adding the bean properties and intercepting serialize()
> >> method.
> >> - Dynamically create a subclass of Scanner, that adds a bean property
> “int
> >> rpcTimeout” and sets its value in the intercepted getNextRowsRequest().
> >>
> >> Now the modifications are only about 300 lines as opposed to the
> previous
> >> ones thousands.
> >>
> >> JW
> >>
> >>
> >>> On Sep 27, 2016, at 3:07 AM, Jong Wook Kim <jongw...@nyu.edu> wrote:
> >>>
> >>> That would be ideal, but asynchbase is being developed according to
> >> OpenTSDB’s own schedules that we don’t have control over

Re: Including asynchbase in the sourcetree

[DO YUNG YOON]

Hi Jong Wook.

Thanks for casting this issue and working on it.
I took some time today, to clear the custom patches and find out followings.

1. GetRequest.setMaxResultsPerColumnFamily/setRowOffsetPerColumnFamily
methods.

I think we do not actually need this method which only exist on our custom
patch.
Instead of using custom method on GetRequest, I think we can use FilterList.
Please check out this commit.
https://github.com/apache/incubator-s2graph/compare/master...SteamShon:asynchbase_path?expand=1


2. Scanner.setTimeout.

Please note that in
https://github.com/apache/incubator-s2graph/compare/master...SteamShon:asynchbase_path?expand=1,
I commented out scanner.setTimeout.
Current upstream Asynchbase does not allow user to set timeout on scanner.
I am going to create issue and send following commits as a PR to upstream.
Please check out
https://github.com/OpenTSDB/asynchbase/compare/master...SteamShon:scanner_timeout?expand=1

In my humble opinion, while we are waiting on issue on 2 discussed, merged,
and finally released by asynchbase guys, I think it is reasonable to use
your suggested patch for our first release.


On Wed, Sep 28, 2016 at 6:25 AM Jong Wook Kim  wrote:

> I managed to created a version using ASM and ByteBuddy to do the
> patchwork:
> https://github.com/jongwook/incubator-s2graph/commit/770917e0c05228ba0855c16e417436bcc67ff412
> <
> https://github.com/jongwook/incubator-s2graph/commit/770917e0c05228ba0855c16e417436bcc67ff412>.
> It does:
>
> - Use ASM to remove the final modifiers of GetRequest and Scanner, and
> make all of their methods public
> - Dynamically create a subclass of GetRequest, that supports the
> limit/offset by adding the bean properties and intercepting serialize()
> method.
> - Dynamically create a subclass of Scanner, that adds a bean property “int
> rpcTimeout” and sets its value in the intercepted getNextRowsRequest().
>
> Now the modifications are only about 300 lines as opposed to the previous
> ones thousands.
>
> JW
>
>
> > On Sep 27, 2016, at 3:07 AM, Jong Wook Kim  wrote:
> >
> > That would be ideal, but asynchbase is being developed according to
> OpenTSDB’s own schedules that we don’t have control over.
> >
> > They don’t release snapshot artifacts and we needed to make a custom
> artifact anyway, and given the fact that their releases are usually only
> once a year I’m not sure if such PR can be merged in the foreseeable future.
> >
> > So this patch (as well as the custom artifact and all that jazz) is a
> temporary measure until there is the next Asynchbase release that contains
> the features we need.
> >
> > I remember that Doyoung made such PR sometime in the past, but I
> couldn’t locate it now.
> >
> >
> > JW
> >
> >> On Sep 27, 2016, at 2:57 AM, Sergio Fernández 
> wrote:
> >>
> >> As far as I understood, such changes affect mainly configuration
> (timeouts,
> >> limits, offsets, etc), right?
> >> Would not be better to submit a PR to the upstream project to allow to
> >> customize such configurations without modifying the code?
> >>
> >> On Tue, Sep 27, 2016 at 8:49 AM, Jong Wook Kim 
> wrote:
> >>
> >>> Related to the recent comments raised in the vote thread, I’d like to
> >>> revisit the asynchbase issue.
> >>>
> >>> Now their fixes on NSRE are tagged in the recently fixed 1.7.2 on Maven
> >>> Central, the remaining differences between our custom version and the
> >>> official version are:
> >>>
> >>> - RPC-wise timeout setting in Scanner
> >>> - limit and offset setting in GetRequest
> >>>
> >>> I made a small patch, as seen in here  >>> incubator-s2graph/commit/ad5c7f89e46ddbd5dfd9b8721737aa22f94b4002>,
> which
> >>> includes GetRequest.java and Scanner.java in the s2core tree along
> with a
> >>> utility that forces loading the bytecode from s2core’s classpath.
> >>>
> >>> Having two ~1000-line java files which are duplicates might be a bad
> >>> practice, but it eliminates the need to maintain a separate codebase
> and
> >>> maven repository for those small patches.
> >>>
> >>> To be more aesthetically satisfying, I’ve fiddled a little bit with
> >>> bytebuddy  to make runtime modification of
> the
> >>> behaviors of those classes, but the modifications are kindof scattered
> >>> making it harder to write the dynamic proxy.
> >>>
> >>> I’d appreciate any comments on the patch above.
> >>>
> >>> JW
> >>
> >>
> >>
> >>
> >> --
> >> Sergio Fernández
> >> Partner Technology Manager
> >> Redlink GmbH
> >> m: +43 6602747925
> >> e: sergio.fernan...@redlink.co
> >> w: http://redlink.co
> >
>
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

 Maven repository.
> >
> > This can be fixed by manually adding the url as an additional Maven
> resolver in the SBT settings, but generally it is not a good idea to use
> the Maven central only rather than adding a custom repo.
> >
> > This might not be a problem if we primarily focus on the S2Graph server
> application in this release, but if we are uploading the S2Graph artifacts
> to the Maven Central, e.g. to support the custom batch job development,
> this needs to be fixed.
> >
> >
> >
> >
> > 3. SBT root project depends on others but only aggregates s2core and
> s2rest_play
> >
> > Currently the root SBT project only aggregates s2core and s2rest_play,
> and thus any sbt command in the root directory, like compile, test, and
> publish, will be only applied to those two.
> >
> >
> >
> >
> > 4. Travis CI fails to resolve SBT dependencies
> >
> > This is most likely a Travis CI issue; it fails while resolving some SBT
> plugins: https://travis-ci.org/jongwook/incubator-s2graph/builds <
> https://travis-ci.org/jongwook/incubator-s2graph/builds>
> >
> >
> >
> >
> > Jong Wook
> >
> >
> >
> >> On Sep 26, 2016, at 9:27 AM, DO YUNG YOON <sho...@gmail.com  sho...@gmail.com>> wrote:
> >>
> >> Hi all.
> >>
> >> So far, we got 1(+1 binding) and 3(+1 non-binding).
> >> Thanks for taking time to try out RC4.
> >> But I think we need more +1.
> >>
> >> Please take time to try out our RC4 then give any feedback and vote.
> >> I will wait more days before closing out this vote thread until either
> >> objection or sufficient votes.
> >>
> >>
> >>
> >>
> >> On Fri, Sep 23, 2016 at 3:00 PM Sergio Fernández <wik...@apache.org
> <mailto:wik...@apache.org>> wrote:
> >>
> >>> On Fri, Sep 23, 2016 at 12:51 AM, Jong Wook Kim <jongw...@nyu.edu
> <mailto:jongw...@nyu.edu>> wrote:
> >>>
> >>>> I wrote that section in the README.md in mind that the majority will
> >>>> download the binary distribution which will contain the content in the
> >>>> subdirectory,
> >>>>
> >>>> The section “Building from the source” specifies that the distribution
> >>>> will be created in target/apache-s2graph-$version-incubating-bin.
> >>>>
> >>>> So I don’t think this is a blocker, but I agree that README.md can be
> >>> even
> >>>> more specific and it would be nice if start-s2graph.sh prints a
> helpful
> >>>> message if it is launched in the source root.
> >>>>
> >>>
> >>> No no, the mistake was completely on my side, I just wanted to provide
> >>> feedback from outside of the project development. Of course this is not
> >>> blocking the release, it's just a comment.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>>> On Sep 22, 2016, at 6:02 AM, Sergio Fernández <wik...@apache.org
> <mailto:wik...@apache.org>>
> >>> wrote:
> >>>>>
> >>>>> On Thu, Sep 22, 2016 at 11:56 AM, Kim, Min-Seok <mskim@gmail.com
> <mailto:mskim@gmail.com>>
> >>>> wrote:
> >>>>>>
> >>>>>> To Sergio,
> >>>>>>
> >>>>>> The commands will work on
> >>>>>>
> >>> `/path/to/incubator-s2graph/target/apache-s2graph-0.1.0-incubating-bin`
> >>>>>> after `sbt package`.
> >>>>>>
> >>>>>
> >>>>> Of course!
> >>>>>
> >>>>> Then the README needs to remark that to avoid people to get confused,
> >>>> like
> >>>>> it happened to me.
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> --
> >>>>> Sergio Fernández
> >>>>> Partner Technology Manager
> >>>>> Redlink GmbH
> >>>>> m: +43 6602747925
> >>>>> e: sergio.fernan...@redlink.co <mailto:sergio.fernan...@redlink.co>
> >>>>> w: http://redlink.co <http://redlink.co/>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Sergio Fernández
> >>> Partner Technology Manager
> >>> Redlink GmbH
> >>> m: +43 6602747925
> >>> e: sergio.fernan...@redlink.co <mailto:sergio.fernan...@redlink.co>
> >>> w: http://redlink.co <http://redlink.co/>
> >>>
> >
>
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

Hi Sergio.

Good to know the process.
I am going to move this vote to general@incubator.

Thanks for your guide.


On Mon, Sep 26, 2016 at 10:58 PM Sergio Fernández <wik...@apache.org> wrote:

> Do Yung, after passing 72 hours you can move this vote to general@incubator
> (referencing this internal vote), where others (including IPMC members and
> other mentors) can further check the release and get the minimum 3 binding
> +1's.
>
>
> On Mon, Sep 26, 2016 at 3:27 PM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi all.
> >
> > So far, we got 1(+1 binding) and 3(+1 non-binding).
> > Thanks for taking time to try out RC4.
> > But I think we need more +1.
> >
> > Please take time to try out our RC4 then give any feedback and vote.
> > I will wait more days before closing out this vote thread until either
> > objection or sufficient votes.
> >
> >
> >
> >
> > On Fri, Sep 23, 2016 at 3:00 PM Sergio Fernández <wik...@apache.org>
> > wrote:
> >
> > > On Fri, Sep 23, 2016 at 12:51 AM, Jong Wook Kim <jongw...@nyu.edu>
> > wrote:
> > >
> > > > I wrote that section in the README.md in mind that the majority will
> > > > download the binary distribution which will contain the content in
> the
> > > > subdirectory,
> > > >
> > > > The section “Building from the source” specifies that the
> distribution
> > > > will be created in target/apache-s2graph-$version-incubating-bin.
> > > >
> > > > So I don’t think this is a blocker, but I agree that README.md can be
> > > even
> > > > more specific and it would be nice if start-s2graph.sh prints a
> helpful
> > > > message if it is launched in the source root.
> > > >
> > >
> > > No no, the mistake was completely on my side, I just wanted to provide
> > > feedback from outside of the project development. Of course this is not
> > > blocking the release, it's just a comment.
> > >
> > >
> > >
> > >
> > >
> > > > > On Sep 22, 2016, at 6:02 AM, Sergio Fernández <wik...@apache.org>
> > > wrote:
> > > > >
> > > > > On Thu, Sep 22, 2016 at 11:56 AM, Kim, Min-Seok <
> mskim@gmail.com
> > >
> > > > wrote:
> > > > >>
> > > > >> To Sergio,
> > > > >>
> > > > >> The commands will work on
> > > > >>
> > > `/path/to/incubator-s2graph/target/apache-s2graph-0.1.0-incubating-bin`
> > > > >> after `sbt package`.
> > > > >>
> > > > >
> > > > > Of course!
> > > > >
> > > > > Then the README needs to remark that to avoid people to get
> confused,
> > > > like
> > > > > it happened to me.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > --
> > > > > Sergio Fernández
> > > > > Partner Technology Manager
> > > > > Redlink GmbH
> > > > > m: +43 6602747925
> > > > > e: sergio.fernan...@redlink.co
> > > > > w: http://redlink.co
> > > >
> > > >
> > >
> > >
> > > --
> > > Sergio Fernández
> > > Partner Technology Manager
> > > Redlink GmbH
> > > m: +43 6602747925
> > > e: sergio.fernan...@redlink.co
> > > w: http://redlink.co
> > >
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

Hi all.

So far, we got 1(+1 binding) and 3(+1 non-binding).
Thanks for taking time to try out RC4.
But I think we need more +1.

Please take time to try out our RC4 then give any feedback and vote.
I will wait more days before closing out this vote thread until either
objection or sufficient votes.




On Fri, Sep 23, 2016 at 3:00 PM Sergio Fernández  wrote:

> On Fri, Sep 23, 2016 at 12:51 AM, Jong Wook Kim  wrote:
>
> > I wrote that section in the README.md in mind that the majority will
> > download the binary distribution which will contain the content in the
> > subdirectory,
> >
> > The section “Building from the source” specifies that the distribution
> > will be created in target/apache-s2graph-$version-incubating-bin.
> >
> > So I don’t think this is a blocker, but I agree that README.md can be
> even
> > more specific and it would be nice if start-s2graph.sh prints a helpful
> > message if it is launched in the source root.
> >
>
> No no, the mistake was completely on my side, I just wanted to provide
> feedback from outside of the project development. Of course this is not
> blocking the release, it's just a comment.
>
>
>
>
>
> > > On Sep 22, 2016, at 6:02 AM, Sergio Fernández 
> wrote:
> > >
> > > On Thu, Sep 22, 2016 at 11:56 AM, Kim, Min-Seok 
> > wrote:
> > >>
> > >> To Sergio,
> > >>
> > >> The commands will work on
> > >>
> `/path/to/incubator-s2graph/target/apache-s2graph-0.1.0-incubating-bin`
> > >> after `sbt package`.
> > >>
> > >
> > > Of course!
> > >
> > > Then the README needs to remark that to avoid people to get confused,
> > like
> > > it happened to me.
> > >
> > > Thanks!
> > >
> > > --
> > > Sergio Fernández
> > > Partner Technology Manager
> > > Redlink GmbH
> > > m: +43 6602747925
> > > e: sergio.fernan...@redlink.co
> > > w: http://redlink.co
> >
> >
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

+1 (non-binding)

I tried RC4 on ubuntu 14.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_91.

I checked followings.

1. Checksums and PGP signatures are valid
2. Release consists of source code only, no binaries
3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
and LICENSE files.
4. Check license header on files.
5. Test if I can run `bin/example.sh` after build.

Thanks.

On Thu, Sep 22, 2016 at 10:24 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi all,
>
> This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
> candidate 4.
> This is the first release of S2Graph.
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC4/
>
>
> The tag to be voted upon is v0.1.0-incubating-rc4:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc4
>
> The release hash is c50d43a06a2044320c4e695b487fe5ee3fc48f91:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=c50d43a06a2044320c4e695b487fe5ee3fc48f91
>
>
> Release artifacts are signed with the following key:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
>
> Once download source, please look into README.md to build from source.
>
> There are 3 issues has been resolved since RC3.
>
> 1. Added missing license headers on files (S2GRAPH-113, S2GRAPH-114).
> 2. Add more committer's public keys on KEYS file (S2GRAPH-110).
>
> The vote will be open for at least 72 hours. Unless objection I will try
> to close it Sunday September 25 if we have sufficient votes.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> please vote:
>
> [ ] +1 Release this package as 0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks,
> DOYUNG YOON.
>
>
>
>
>
>

[VOTE] Apache S2Graph(incubating) 0.1.0 release RC4

[DO YUNG YOON]

Hi all,

This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
candidate 4.
This is the first release of S2Graph.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC4/


The tag to be voted upon is v0.1.0-incubating-rc4:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc4

The release hash is c50d43a06a2044320c4e695b487fe5ee3fc48f91:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=c50d43a06a2044320c4e695b487fe5ee3fc48f91


Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md to build from source.

There are 3 issues has been resolved since RC3.

1. Added missing license headers on files (S2GRAPH-113, S2GRAPH-114).
2. Add more committer's public keys on KEYS file (S2GRAPH-110).

The vote will be open for at least 72 hours. Unless objection I will try to
close it Sunday September 25 if we have sufficient votes.

Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC3

[DO YUNG YOON]

Hi folks.
This vote close with one -1(binding) and one -1(non-binding).

I am going address license header issue then prepare RC4.

Even though vote is canceled, Please give more feedback on RC3 so we can
address as much issues as possible for RC4.


On Tue, Sep 20, 2016 at 6:39 PM Sergio Fernández <wik...@apache.org> wrote:

> -1 (binding): there are files (e.g., bin/example.sh) without proper license
> headers.
>
> On Tue, Sep 13, 2016 at 3:41 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi all,
> >
> > This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
> > candidate 3.
> > This is the first release of S2Graph.
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1
> > .0-incubating-RC3/
> >
> > The tag to be voted upon is v0.1.0-incubating-rc3:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc3
> >
> > The release hash is b32c74242cbe4fcde05f77000989df2f1f0f36c0:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=commit;h=b32c74242cbe4fcde05f77000989df2f1f0f36c0
> >
> > Release artifacts are signed with the following key:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
> >
> > Once download source, please look into README.md and BUILD.md to build
> from
> > source.
> >
> > Please refer sub-tasks of S2GRAPH-86(
> > https://issues.apache.org/jira/browse/S2GRAPH-86) to check addressed
> > issues
> > from RC2(S2GRAPH-104/105/106/109/12/112/111).
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > please vote:
> >
> > [ ] +1 Release this package as 0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks,
> > DOYUNG YOON.
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC3

[DO YUNG YOON]

Hi Sergio.

Thanks for your feedback and appreciate following RC.
I was about to ask if it is possible to extend due date of this vote, since
I believe that most of committers(including myself) were on national
holidays, which just ended yesterday.

I checked RC3 on ubuntu 14.04, SBT 0.13.9, SCALA 2.11.7, OpenJDK 1.8.0_60.

Followings what I have checked.

1. Checksums and PGP signatures are valid
2. Release consists of source code only, no binaries
3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
and LICENSE files.
4. Check license header on files.
5. Warning while packaging.
6. Test if I can run `bin/example.sh` after build(by sbt package).

One thing I found out was `bin/example.sh` does not contain license header.

So my vote for RC3 is -1(non-binding).

Please take a look at this release candidates then give feedbacks.


On Tue, Sep 20, 2016 at 3:46 PM Sergio Fernández <wik...@apache.org> wrote:

> Just arrived back from my vacations; I'm gonna check RC3 later, once I got
> under control some more urgent things at work.
> I wonder why nobody has checked this vote in one week...
> Remember that both mentors (binding) and committers (non-binding) have
> responsibilities within the project releases.
> Checking a release (including the RM) helps you to make better releases in
> the future.
>
>
> On Tue, Sep 13, 2016 at 3:41 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi all,
> >
> > This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
> > candidate 3.
> > This is the first release of S2Graph.
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1
> > .0-incubating-RC3/
> >
> > The tag to be voted upon is v0.1.0-incubating-rc3:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc3
> >
> > The release hash is b32c74242cbe4fcde05f77000989df2f1f0f36c0:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=commit;h=b32c74242cbe4fcde05f77000989df2f1f0f36c0
> >
> > Release artifacts are signed with the following key:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
> >
> > Once download source, please look into README.md and BUILD.md to build
> from
> > source.
> >
> > Please refer sub-tasks of S2GRAPH-86(
> > https://issues.apache.org/jira/browse/S2GRAPH-86) to check addressed
> > issues
> > from RC2(S2GRAPH-104/105/106/109/12/112/111).
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > please vote:
> >
> > [ ] +1 Release this package as 0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks,
> > DOYUNG YOON.
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC2

[DO YUNG YOON]

Hi folks.
Vote close with one -1(binding).

Hi Sergio.
Thanks again all your feedback.
I think I am going to work on followings for RC3.

1. S2GRAPH-104
2. S2GRAPH-105
3. remove lots of warning while package.
4. add other committers signing key on KEYS file.
5. document release process.

Other than above, can you please suggest anything else?

On Thu, Sep 1, 2016 at 11:02 PM Sergio Fernández <wik...@apache.org> wrote:

> Please Do Yung, cancel RC2 vote accordingly.
>
> On Thu, Sep 1, 2016 at 3:36 PM, Sergio Fernández <wik...@apache.org>
> wrote:
>
> > Hi Do Yung,
> >
> > On Thu, Sep 1, 2016 at 3:07 PM, DO YUNG YOON <sho...@gmail.com> wrote:
> >>
> >> Thanks for the quick feedback.
> >>
> >
> > The quicker the better, specially the timing for me.
> >
> > After look up, I found out following dependency version are missing from
> >> maven central.
> >> I tried to add these lines on commonSettings in root project's
> build.sbt.
> >>
> >> libraryDependencies ++= Seq(
> >> "org.scalaz.stream" % "scalaz-stream_2.11" % "0.7.2",
> >> "com.typesafe.netty" % "netty-http-pipelining" % "1.1.4"
> >>   )
> >>
> >> Can you please check if this works?
> >>
> >
> > Yes, patching the build.sbt  with that made the package task work for me:
> >
> > [info] Done packaging.
> > [info] Package for distribution located at /home/wikier/tmp/s2graph/apach
> > e-s2graph-0.1.0-incubating/target/apache-s2graph-0.1.0-incubating-bin
> > [info] creating a tarball...
> > tar: Removing leading `/' from member names
> > [info] Tarball is located at /home/wikier/tmp/s2graph/apach
> > e-s2graph-0.1.0-incubating/target/apache-s2graph-0.1.0-incub
> > ating-bin.tar.gz
> > [success] Total time: 171 s, completed Sep 1, 2016 3:18:10 PM
> >
> >
> > In addition to S2GRAPH-104 to fixed the reported issue, checking this
> > release I also found another issue in the generated tarball
> (S2GRAPH-105).
> >
> > Hope that helps.
> >
> > Cheers,
> >
> >
> > On Thu, Sep 1, 2016 at 7:43 PM Sergio Fernández <wik...@apache.org>
> wrote:
> >>
> >> > Hi Do Yung,
> >> >
> >> > thanks for casting a new release candidate. As I said during the
> >> previous
> >> > RC, I want to insist the very first release is very important
> milestone
> >> for
> >> > a podling.
> >> >
> >> > Here my vote: -1 (binding)
> >> >
> >> > I can't build from the sources given a missing dependency:
> >> >
> >> > [info] Packaging
> >> >
> >> > /home/wikier/tmp/s2graph/apache-s2graph-0.1.0-incubating/s2r
> >> est_netty/target/scala-2.11/s2rest_netty_2.11-0.1.0.jar
> >> > ...
> >> > [info] Done packaging.
> >> > sbt.ResolveException: unresolved dependency:
> >> > org.scalaz.stream#scalaz-stream_2.11;0.7a: not found
> >> >
> >> > For want I've check
> >> >
> >> > http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.scalaz
> >> .stream%22%20AND%20a%3A%22scalaz-stream_2.11%22
> >> > only version 0.8.4a looks to be available from Maven Central.
> >> >
> >> > I tried to build the RC sources in a clean environment: SBT 0.13.9,
> >> Scala
> >> > 2.11.6, OpenJDK 1.8.0_91 64-Bit, Debian amd64
> >> >
> >> > So far I've successfully checked:
> >> >
> >> > * signatures and digests
> >> > * source releases file layouts
> >> > * matched git tags and commit ids
> >> > * incubator suffix and disclaimer, NOTICE and LICENSE files
> >> > * license headers,
> >> >
> >> > Thanks for addressing all my comments to RC1 <
> https://s.apache.org/oarA
> >> >.
> >> > In addition, some minor comments that would be great to improve:
> >> >
> >> > * I can see quite many warning ("discarding unmoored doc comment", "a
> >> type
> >> > was inferred to be `Any`; this may indicate a programming error",
> >> "Adapting
> >> > argument list by creating a 4-tuple: this may not be what you want",
> >> > etc) during build that would be better to solve.
> >> > * More people should add theirs GPG keys to the project file, just in
> >> case
> >> > anybody else acts as RM in new releases
> &g

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC2

[DO YUNG YOON]

Hi Sergio.

Thanks for the quick feedback.

After look up, I found out following dependency version are missing from
maven central.
I tried to add these lines on commonSettings in root project's build.sbt.

libraryDependencies ++= Seq(
"org.scalaz.stream" % "scalaz-stream_2.11" % "0.7.2",
"com.typesafe.netty" % "netty-http-pipelining" % "1.1.4"
  )

Can you please check if this works?



On Thu, Sep 1, 2016 at 7:43 PM Sergio Fernández <wik...@apache.org> wrote:

> Hi Do Yung,
>
> thanks for casting a new release candidate. As I said during the previous
> RC, I want to insist the very first release is very important milestone for
> a podling.
>
> Here my vote: -1 (binding)
>
> I can't build from the sources given a missing dependency:
>
> [info] Packaging
>
> /home/wikier/tmp/s2graph/apache-s2graph-0.1.0-incubating/s2rest_netty/target/scala-2.11/s2rest_netty_2.11-0.1.0.jar
> ...
> [info] Done packaging.
> sbt.ResolveException: unresolved dependency:
> org.scalaz.stream#scalaz-stream_2.11;0.7a: not found
>
> For want I've check
>
> http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.scalaz.stream%22%20AND%20a%3A%22scalaz-stream_2.11%22
> only version 0.8.4a looks to be available from Maven Central.
>
> I tried to build the RC sources in a clean environment: SBT 0.13.9, Scala
> 2.11.6, OpenJDK 1.8.0_91 64-Bit, Debian amd64
>
> So far I've successfully checked:
>
> * signatures and digests
> * source releases file layouts
> * matched git tags and commit ids
> * incubator suffix and disclaimer, NOTICE and LICENSE files
> * license headers,
>
> Thanks for addressing all my comments to RC1 <https://s.apache.org/oarA>.
> In addition, some minor comments that would be great to improve:
>
> * I can see quite many warning ("discarding unmoored doc comment", "a type
> was inferred to be `Any`; this may indicate a programming error", "Adapting
> argument list by creating a 4-tuple: this may not be what you want",
> etc) during build that would be better to solve.
> * More people should add theirs GPG keys to the project file, just in case
> anybody else acts as RM in new releases
>
> If you point me how to sort-out the issue with the missing dependency, I'm
> more than happy to revise my vote. But, as I pointer in another email,
> remember I'd only have 24 hours from now until I'll go on vacations.
>
> Thanks.
>
> Cheers,
>
>
> On Thu, Sep 1, 2016 at 11:53 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi all,
> >
> > This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
> > candidate 2.
> > This is the first release of S2Graph.
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> > 1.0-incubating-RC2/
> >
> > The tag to be voted upon is v0.1.0-incubating-rc2:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc2
> >
> > The release hash is c2f3fc21b40bf21611e242c63146e847de28f5e5:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> > git;a=commit;h=c2f3fc21b40bf21611e242c63146e847de28f5e5
> >
> > Release artifacts are signed with the following key:
> > https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
> >
> > Once download source, please look into README.md and BUILD.md to build
> from
> > source.
> >
> > Please refer sub-tasks of S2GRAPH-86(
> > https://issues.apache.org/jira/browse/S2GRAPH-86) to check addressed
> > issues
> > from RC1.
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > please vote:
> >
> > [ ] +1 Release this package as 0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks,
> > DOYUNG YOON.
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

[VOTE] Apache S2Graph(incubating) 0.1.0 release RC2

[DO YUNG YOON]

Hi all,

This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
candidate 2.
This is the first release of S2Graph.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC2/

The tag to be voted upon is v0.1.0-incubating-rc2:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc2

The release hash is c2f3fc21b40bf21611e242c63146e847de28f5e5:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=c2f3fc21b40bf21611e242c63146e847de28f5e5

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md and BUILD.md to build from
source.

Please refer sub-tasks of S2GRAPH-86(
https://issues.apache.org/jira/browse/S2GRAPH-86) to check addressed issues
from RC1.

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

[VOTE] Apache S2Graph(incubating) 0.1.0 release RC1

[DO YUNG YOON]

Hi all,

This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
candidate 1. This is the first release of S2Graph.

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.1.0-incubating-RC1/

The tag to be voted upon is v0.1.0-incubating-rc1:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc1

The release hash is d52881e2deb6d16f815ebf4f018a23edaf11575a:
https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=commit;h=d52881e2deb6d16f815ebf4f018a23edaf11575a

Release artifacts are signed with the following key:
https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS

Once download source, please look into README.md and BUILD.md to build from
source.

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
please vote:

[ ] +1 Release this package as 0.1.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Thanks,
DOYUNG YOON.

Re: Podling Report Reminder - August 2016

[DO YUNG YOON]

Hi guys.
I just updated wiki for August report.
Please review this at https://wiki.apache.org/incubator/August2016.


following is just copy & paste of report on wiki.

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

Three most important issues to address in the move towards graduation:

  1. Make a release
  2. Attract users and contributors
  3. Foster more and diverse committers

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None

How has the community developed since the last report?

  * Held a session on S2Graph: Internal at Apache Big Data NA

  * Made various networking efforts at Apache Big Data NA, Vancouver and
Druid Meet-up, Seoul

  * Made plans to integrate with Apache TinkerPop in order to reach a wider
audience (S2GRAPH-72)

  * Discussion with Apache Zepplin regarding joint meet-ups at Seoul

  * 3 inquiries from user mailing list

  * Submit paper to INFOCOM 2017

How has the project developed since the last report?

  * We decided project logo.

  * Project website is up.

  * Working on issues on providing package for distribution.

  * 20 issues are created, 18 issues are resolved.

  * Working on first release(S2GRAPH-86)

Date of last release:

  No yet

When were the last committers or PMC members elected?

  No

Signed-off-by:

  [ ](s2graph) Andrew Purtell
  [ ](s2graph) Venkatesh Seetharam
  [ ](s2graph) Sergio Fernández

On Mon, Aug 1, 2016 at 3:04 PM Sergio Fernández <wik...@apache.org> wrote:

> np, thx!
>
> On Mon, Aug 1, 2016 at 8:03 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>
> > Hi Sergio.
> > sorry for being late, I have been busy these days.
> > I will try to update wiki tonight!
> > Thanks for heads up!
> >
> >
> > On Mon, Aug 1, 2016 at 2:56 PM Sergio Fernández <wik...@apache.org>
> wrote:
> >
> > > ping
> > > the report should be online in the wiki in two days...
> > >
> > > On Wed, Jul 27, 2016 at 3:29 PM, Sergio Fernández <wik...@apache.org>
> > > wrote:
> > >
> > > > volunteers?
> > > >
> > > > On Wed, Jul 27, 2016 at 1:47 PM, <johndam...@apache.org> wrote:
> > > >
> > > >> Dear podling,
> > > >>
> > > >> This email was sent by an automated system on behalf of the Apache
> > > >> Incubator PMC. It is an initial reminder to give you plenty of time
> to
> > > >> prepare your quarterly board report.
> > > >>
> > > >> The board meeting is scheduled for Wed, 17 August 2016, 10:30 am
> PDT.
> > > >> The report for your podling will form a part of the Incubator PMC
> > > >> report. The Incubator PMC requires your report to be submitted 2
> weeks
> > > >> before the board meeting, to allow sufficient time for review and
> > > >> submission (Wed, August 03).
> > > >>
> > > >> Please submit your report with sufficient time to allow the
> Incubator
> > > >> PMC, and subsequently board members to review and digest. Again, the
> > > >> very latest you should submit your report is 2 weeks prior to the
> > board
> > > >> meeting.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> The Apache Incubator PMC
> > > >>
> > > >> Submitting your Report
> > > >>
> > > >> --
> > > >>
> > > >> Your report should contain the following:
> > > >>
> > > >> *   Your project name
> > > >> *   A brief description of your project, which assumes no knowledge
> of
> > > >> the project or necessarily of its field
> > > >> *   A list of the three most important issues to address in the move
> > > >> towards graduation.
> > > >> *   Any issues that the Incubator PMC or ASF Board might wish/need
> to
> > be
> > > >> aware of
> > > >> *   How has the community developed since the last report
> > > >> *   How has the project developed since the last report.
> > > >>
> > > >> This should be appended to the Incubator Wiki page at:
> > > >>
> > > >> http://wiki.apache.org/incubator/August2016
> > > >>
> > > >> Note: This is manually populated. You may need to wait a little
> before
> > > >> this page is created from a template.
> > > &g

Re: Podling Report Reminder - August 2016

[DO YUNG YOON]

Hi Sergio.
sorry for being late, I have been busy these days.
I will try to update wiki tonight!
Thanks for heads up!


On Mon, Aug 1, 2016 at 2:56 PM Sergio Fernández  wrote:

> ping
> the report should be online in the wiki in two days...
>
> On Wed, Jul 27, 2016 at 3:29 PM, Sergio Fernández 
> wrote:
>
> > volunteers?
> >
> > On Wed, Jul 27, 2016 at 1:47 PM,  wrote:
> >
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC. It is an initial reminder to give you plenty of time to
> >> prepare your quarterly board report.
> >>
> >> The board meeting is scheduled for Wed, 17 August 2016, 10:30 am PDT.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2 weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, August 03).
> >>
> >> Please submit your report with sufficient time to allow the Incubator
> >> PMC, and subsequently board members to review and digest. Again, the
> >> very latest you should submit your report is 2 weeks prior to the board
> >> meeting.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >>
> >> --
> >>
> >> Your report should contain the following:
> >>
> >> *   Your project name
> >> *   A brief description of your project, which assumes no knowledge of
> >> the project or necessarily of its field
> >> *   A list of the three most important issues to address in the move
> >> towards graduation.
> >> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> >> aware of
> >> *   How has the community developed since the last report
> >> *   How has the project developed since the last report.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> http://wiki.apache.org/incubator/August2016
> >>
> >> Note: This is manually populated. You may need to wait a little before
> >> this page is created from a template.
> >>
> >> Mentors
> >> ---
> >>
> >> Mentors should review reports for their project(s) and sign them off on
> >> the Incubator wiki page. Signing off reports shows that you are
> >> following the project - projects that are not signed may raise alarms
> >> for the Incubator PMC.
> >>
> >> Incubator PMC
> >>
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: [Discuss] license file for dependencies.

[DO YUNG YOON]

-protocol:1.0.1
[info] org.apache.hbase:hbase-common:1.0.1
[info] org.apache.htrace:htrace-core:3.1.0-incubating
[info] commons-io:commons-io:2.4
[info] commons-collections:commons-collections:3.2.1
[info] commons-lang:commons-lang:2.6
[info] commons-codec:commons-codec:1.9
[info] commons-logging:commons-logging:1.2
[info] org.apache.hbase:hbase-annotations:1.0.1
[info] log4j:log4j:1.2.17
[info] com.google.guava:guava:12.0.1
[info] com.google.code.findbugs:jsr305:1.3.9
[info] com.fasterxml.jackson.core:jackson-databind:2.3.2
[info] com.fasterxml.jackson.core:jackson-core:2.3.2
[info] com.fasterxml.jackson.core:jackson-annotations:2.3.2
[info]
[info] The BSD License
[info] xmlenc:xmlenc:0.52

http://www.apache.org/legal/resolved.html#category-b

[info] CDDL 1.0
[info] org.mortbay.jetty:jsp-2.1:6.1.14
[info] org.mortbay.jetty:servlet-api-2.5:6.1.14
[info]
[info] CDDL 1.1
[info] com.sun.jersey.contribs:jersey-guice:1.9
[info] com.sun.jersey:jersey-json:1.9
[info] com.sun.xml.bind:jaxb-impl:2.2.3-1
[info] javax.xml.bind:jaxb-api:2.2.2
[info] com.sun.jersey:jersey-server:1.9
[info] com.sun.jersey:jersey-core:1.9
[info]
[info] Common Development and Distribution License (CDDL) v1.0
[info] javax.activation:activation:1.1
[info]
[info] Common Public License Version 1.0
[info] junit:junit:4.11
[info]
[info] Eclipse Public License - v 1.0
[info] ch.qos.logback:logback-classic:1.1.2
[info] ch.qos.logback:logback-core:1.1.2
[info]
[info] MPL 2.0 or EPL 1.0
[info] com.h2database:h2:1.4.192
[info]
[info] Mozilla Public License Version 1.1
[info] org.jamon:jamon-runtime:2.3.1
[info]
[info] Public Domain
[info] aopalliance:aopalliance:1.0
[info] org.tukaani:xz:1.0

http://www.apache.org/legal/resolved.html#category-x

[info] GNU General Public Library
[info] javax.xml.stream:stax-api:1.0-2
[info]
[info] The GNU General Public License, Version 2
[info] mysql:mysql-connector-java:5.1.28


In summary I think dependencies with "cateogory-x" have following
dependency tree.

1. javax.xml.stream:stax-api:1.0-2 comes from
org.apache.hbase:hbase-hadoop2-compat:1.2.1 ->
org.apache.hadoop:hadoop-common:2.5.1 -> com.sun.jersey:jersey-json:1.9 ->
com.sun.xml.bind:jaxb-impl:2.2.3-1 -> javax.xml.bind:jaxb-api:2.2.2
2. javax.servlet.jsp:jsp-api:2.1 comes from
org.apache.hbase:hbase-hadoop2-compat:1.0.1
3. javax.servlet:servlet-api:2.5 comes from
org.apache.hadoop:hadoop-yarn-common:2.5.1
4. mysql:mysql-connector-java:5.1.28.
5. also we have custom patched asynchbase(LGPL v2.1). this Asynchbase jar
is unmanaged(it is on s2core/lib directory).


1,2,3 comes from haddop and hbase so I guess it is ok. however 4 should be
removed and ask user to download third party dependencies. Also 5 should be
addressed as well. we should ask user to download 4,5 or we should change
s2graph not to use 4,5.

I am thinking about provide script download thirdparty dependencies on
package. what do you guys think?

Also I will take a look around on other incubator project releases
especially whats included in LICENSE, NOTICE, DISCLAIMER and follow up with
our LICENSE, NOTICE, DISCLAIMER.

Please advice me if anyone has concerns.

Best Regards.
DOYUNG YOON


On Tue, Jul 5, 2016 at 12:15 AM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi folks.
>
> I was working on creating LICENSE file for our release and following is
> what I have got from `sbt dependencyLicenseInfo` on branch-0.1.0.
>
> I am not sure why bunch of jar are specified as `No license specified`.
> Any help on figure out this?
> I am following below references to decide which dependencies are ok to be
> included.
>
> http://www.apache.org/legal/resolved.html#category-a
>
> [info] Apache 2
> [info] com.typesafe.netty:netty-http-pipelining:1.1.2
> [info] com.typesafe.play:twirl-api_2.11:1.0.2
> [info] org.joda:joda-convert:1.7
> [info] joda-time:joda-time:2.5
> [info]
> [info] Apache License
> [info] commons-httpclient:commons-httpclient:3.1
> [info]
> [info] Apache License 2.0
> [info] com.ning:async-http-client:1.8.15
> [info]
> [info] Apache License Version 2
> [info] org.mortbay.jetty:jetty-sslengine:6.1.26
> [info]
> [info] Apache License, Version 2.0
> [info] com.typesafe.akka:akka-slf4j_2.11:2.3.4
> [info] io.netty:netty:3.9.9.Final
> [info] com.github.danielwegener:logback-kafka-appender:0.0.4
> [info] org.scalikejdbc:scalikejdbc_2.11:2.1.4
> [info] org.scalikejdbc:scalikejdbc-interpolation_2.11:2.1.4
> [info] org.scalikejdbc:scalikejdbc-interpolation-macro_2.11:2.1.4
> [info] org.scalikejdbc:scalikejdbc-core_2.11:2.1.4
> [info] net.java.dev.jets3t:jets3t:0.9.0
> [info] com.jamesmurty.utils:java-xmlbuilder:0.4
> [info] com.github.stephenc.findbugs:findbugs-annotations:1.3.9-1
> [info] com.typesafe.akka:akka-actor_2.11:2.3.4
> [info] com.typesafe:config:1.2.1
> [info]
> [info] Apache-2.0
> [info] com.typesafe.play:filters-helpers_2.11:2.3.10
> [info] com

New release branch 0.1.0

[DO YUNG YOON]

I've just created new release branch for our first 0.1.0 release. Please
continue committing to main branch as usual, I'll cherry-pick commits to
branch-0.1.0 on per needed basis.

Thanks.

https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.git;a=shortlog;h=refs/heads/branch-0.1.0


Thanks

DOYUNG YOON

Work on first release has started!

[DO YUNG YOON]

Hi guys.
We are staring the process to prepare for S2Graph first release.
I have opend JIRA(https://issues.apache.org/jira/browse/S2GRAPH-86) to
cover the tasks under our first release.
If you have any JIRA in progress and would like to include it in this
release, please follow the process to do so.
Feel free to comment on the JIRA if you have any comments/suggestions.

Best Regards.
DOYUNG YOON

Re: Simplify write-write conflict resolving logic.

[DO YUNG YOON]

I also applied changes from above issue on separate branch on gitbook to
explain details.
Anyone who is interested, the details can be found at
https://steamshon.gitbooks.io/s2graph-book/content/v/S2GRAPH-83/request_state_diagram.html
(resolve
https://issues.apache.org/jira/browse/S2GRAPH-83?jql=project%20%3D%20S2GRAPH
)

On Sat, May 28, 2016 at 3:35 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi JunKi.
>
> I had free time today, and start working on
> https://issues.apache.org/jira/browse/S2GRAPH-68.
> You can find out where this is going to on
> https://github.com/apache/incubator-s2graph/pull/53.
> Any feedback and question would be appreciated.
>
> On Thu, Apr 28, 2016 at 12:33 AM DO YUNG YOON <sho...@gmail.com> wrote:
>
>> Hi Jun Ki.
>> I just created https://issues.apache.org/jira/browse/S2GRAPH-68 and
>> start to work on this.
>> I will ask your opinion while I am working on this, so please gives any
>> feedback and let's continue discussion.
>>
>>
>> On Fri, Apr 22, 2016 at 9:10 AM Jun Ki Kim <wishop...@gmail.com> wrote:
>>
>>> OK, I see what you said. Sorry for my mis-understanding.
>>> More comments makes more readability. That will be very helpful to me.
>>> After the your job, I may also try to make another suggestion.
>>>
>>> Thanks for your correction!
>>>
>>> Best regards,
>>> Junki Kim
>>> 2016년 4월 21일 (목) 오후 11:58, DO YUNG YOON <sho...@gmail.com>님이 작성:
>>>
>>> > Apology on my bad explanation. it is always hard to explain concepts
>>> > clearly.
>>> >
>>> > Point is current logic is over complicated so make others hard to
>>> > understand.
>>> > What I am planning is start from writing comments with explanation and
>>> > assertion. Then ask others if it makes sense, then go for
>>> implementation.
>>> > JunKi, How about this?
>>> >
>>> > What's others opinion on this?
>>> >
>>> > Best Regards.
>>> > DO YUNG YOON
>>> >
>>> > On Wed, Apr 20, 2016 at 5:37 PM Jun Ki Kim <wishop...@gmail.com>
>>> wrote:
>>> >
>>> > > Conflict management is the hardest logic to understand how it works.
>>> I
>>> > > think many people may agree my opinion.
>>> > > I don't know well about core module and don't understand well what
>>> you
>>> > > suggested too. However I totally agree with refactoring the core
>>> logic! I
>>> > > very welcome to make more readable to me and more comments.
>>> > > I will try to understand and refactor the core logic. Please give me
>>> more
>>> > > wisdom. ^^;
>>> > >
>>> > > Regards,
>>> > > Junki Kim
>>> > > 2016년 4월 20일 (수) 오전 9:15, DO YUNG YOON <sho...@gmail.com>님이 작성:
>>> > >
>>> > > > Current implementation to resolve conflicts on same snapshotEdge is
>>> > > > overwhelmingly complicated.
>>> > > > I am suggesting refactor this part so we can understand what is
>>> going
>>> > on
>>> > > > for consistency.
>>> > > >
>>> > > > More importantly, with positive fail probability for
>>> > > > RPC(hbase.fail.prob=0.01), test cases actually fail.
>>> > > > we can reproduce failure by running `sbt "project s2core"
>>> > > > -Dconfig.file=s2rest_play/conf/test.conf test`.
>>> > > > What we intended initially here is guarantee to resolve conflicts
>>> even
>>> > > some
>>> > > > RPC into storage fail.
>>> > > >
>>> > > > I was fixing this issue and quickly realize current code base is
>>> way
>>> > too
>>> > > > complicated and not efficient.
>>> > > >
>>> > > > here is brief explanation(
>>> > > >
>>> > > >
>>> > >
>>> >
>>> https://steamshon.gitbooks.io/s2graph-book/content/request_state_diagram.html
>>> > > > ).
>>> > > >
>>> > > > the big picture for this process goes like below.
>>> > > >
>>> > > > - retry on failure
>>> > > >   -- fetch snapshotEdge as oldSN.
>>> > > > --- merge oldSN and requesting edges and build newSN containing
>>> > > updated
>>> > > > stat

Re: Podling Report Reminder - May 2016

[DO YUNG YOON]

I find out
http://mail-archives.apache.org/mod_mbox/incubator-general/201605.mbox/%3ccaoqetn-vd17vur0lw-9cntjf0cg_f4qgk+3+iu47+1jfxcc...@mail.gmail.com%3E
.

According to this link, I think we can disregard the reminders for May.
Any thought?

On Wed, Jun 1, 2016 at 10:38 PM DO YUNG YOON <sho...@gmail.com> wrote:

> Hi folks.
>
> I was about to add report draft on wiki but I can't find S2GRAPH on
> http://wiki.apache.org/incubator/June2016.
> Should I add it? I am wondering because last time, the template has entry
> for S2GRAPH and this time it does not have one.
> Anyway following is the draft for June report, Please review.
>
>
> S2Graph is a distributed and scalable OLTP graph database built on Apache
>
> HBase to support fast traversal of extremely large graphs.
>
>
> S2Graph has been incubating since 2015-11-29.
>
>
> Three most important issues to address in the move towards graduation:
>
>
>   1. Make a release
>
>   2. Attract users and contributors
>
>   3. Foster more and diverse committers
>
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>
> aware of?
>
>
> None
>
>
> How has the community developed since the last report?
>
>
>   * Held a session on S2Graph: Internal at Apache Big Data NA
>
>   * Made various networking efforts at Apache Big Data NA, Vancouver and
> Druid Meet-up, Seoul
>
>   * Made plans to integrate with Apache TinkerPop in order to reach a
> wider audience (S2GRAPH-72)
>
>   * Discussion with Apache Zepplin regarding joint meet-ups at Seoul
>
>
> How has the project developed since the last report?
>
>
>   * We decided project logo.
>
>   * Project website is up.
>
>   * Working on issues on providing package for distribution.
>
>   * 14 issues are created, no issues are resolved, no commits merged since
> last report at May.
>
>
> Date of last release:
>
>
>   No yet
>
>
> When were the last committers or PMC members elected?
>
>
>   No
>
>
> Signed-off-by:
>
>
>   [ ](s2graph) Andrew Purtell
>
>   [ ](s2graph) Seetharam Venkatesh
>
>   [ ](s2graph) Sergio Fernández
>
>
> Shepherd/Mentor notes:
>
>
>
>
> On Fri, May 27, 2016 at 4:02 PM Sergio Fernández <wik...@apache.org>
> wrote:
>
>> Volunteers?
>>
>> On Thu, May 26, 2016 at 4:33 AM, <johndam...@apache.org> wrote:
>>
>> > Dear podling,
>> >
>> > This email was sent by an automated system on behalf of the Apache
>> > Incubator PMC. It is an initial reminder to give you plenty of time to
>> > prepare your quarterly board report.
>> >
>> > The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
>> > The report for your podling will form a part of the Incubator PMC
>> > report. The Incubator PMC requires your report to be submitted 2 weeks
>> > before the board meeting, to allow sufficient time for review and
>> > submission (Wed, June 1st).
>> >
>> > Please submit your report with sufficient time to allow the Incubator
>> > PMC, and subsequently board members to review and digest. Again, the
>> > very latest you should submit your report is 2 weeks prior to the board
>> > meeting.
>> >
>> > Thanks,
>> >
>> > The Apache Incubator PMC
>> >
>> > Submitting your Report
>> >
>> > --
>> >
>> > Your report should contain the following:
>> >
>> > *   Your project name
>> > *   A brief description of your project, which assumes no knowledge of
>> > the project or necessarily of its field
>> > *   A list of the three most important issues to address in the move
>> > towards graduation.
>> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>> > aware of
>> > *   How has the community developed since the last report
>> > *   How has the project developed since the last report.
>> >
>> > This should be appended to the Incubator Wiki page at:
>> >
>> > http://wiki.apache.org/incubator/May2016
>> >
>> > Note: This is manually populated. You may need to wait a little before
>> > this page is created from a template.
>> >
>> > Mentors
>> > ---
>> >
>> > Mentors should review reports for their project(s) and sign them off on
>> > the Incubator wiki page. Signing off reports shows that you are
>> > following the project - projects that are not signed may raise alarms
>> > for the Incubator PMC.
>> >
>> > Incubator PMC
>> >
>>
>>
>>
>> --
>> Sergio Fernández
>> Partner Technology Manager
>> Redlink GmbH
>> m: +43 6602747925
>> e: sergio.fernan...@redlink.co
>> w: http://redlink.co
>>
>

Re: Podling Report Reminder - May 2016

[DO YUNG YOON]

Hi folks.

I was about to add report draft on wiki but I can't find S2GRAPH on
http://wiki.apache.org/incubator/June2016.
Should I add it? I am wondering because last time, the template has entry
for S2GRAPH and this time it does not have one.
Anyway following is the draft for June report, Please review.


S2Graph is a distributed and scalable OLTP graph database built on Apache

HBase to support fast traversal of extremely large graphs.


S2Graph has been incubating since 2015-11-29.


Three most important issues to address in the move towards graduation:


  1. Make a release

  2. Attract users and contributors

  3. Foster more and diverse committers


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be

aware of?


None


How has the community developed since the last report?


  * Held a session on S2Graph: Internal at Apache Big Data NA

  * Made various networking efforts at Apache Big Data NA, Vancouver and
Druid Meet-up, Seoul

  * Made plans to integrate with Apache TinkerPop in order to reach a wider
audience (S2GRAPH-72)

  * Discussion with Apache Zepplin regarding joint meet-ups at Seoul


How has the project developed since the last report?


  * We decided project logo.

  * Project website is up.

  * Working on issues on providing package for distribution.

  * 14 issues are created, no issues are resolved, no commits merged since
last report at May.


Date of last release:


  No yet


When were the last committers or PMC members elected?


  No


Signed-off-by:


  [ ](s2graph) Andrew Purtell

  [ ](s2graph) Seetharam Venkatesh

  [ ](s2graph) Sergio Fernández


Shepherd/Mentor notes:




On Fri, May 27, 2016 at 4:02 PM Sergio Fernández  wrote:

> Volunteers?
>
> On Thu, May 26, 2016 at 4:33 AM,  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, June 1st).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > http://wiki.apache.org/incubator/May2016
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>