Re: Meet and chat in Seoul area?

[Hwansung Yu]

Hi,

I'm so happy to hear from you.
How about late September after thanksgiving?

Best regards,

Hwansung


2019년 8월 27일 (화) 오후 9:05, Woonsan Ko 님이 작성:

> Hi,
>
> I'm going to stay in South Korea in Sept. and Oct. If anyone is
> willing to meet and chat (perhaps over beer), let me know. I'd be very
> happy. ;-)
>
> Kind regards,
>
> Woonsan
>

[ANNOUNCE] New Committer: Jongwook kim

[Hwansung Yu]

Let us welcome Jongwook kim as a new Committer of S2Graph.
He has contributed to solve a lot of issues.
He also shows active participation on the mailing list and enters input
from outside of Kakao corp which increase our diversity.

Following is issues that resolved by JongWook Kim

- S2GRAPH-70: Automate the process of building a distribution package
- S2GRAPH-116: using ASM and ByteBuddy to add a proxy to Asynchbase's
Scanner.
- S2GRAPH-117: Cleaner logging library usage.
- S2GRAPH-73: Add an SBT task and relevant scripts to construct a package
for distribution.
- S2GRAPH-74: Add a script that starts/stops a local hbase server.
- S2GRAPH-75: Use an embedded database as the default metadata storage.
- S2GRAPH-88: Add DISCLAIMER, LICENSE, NOTICE on packaging process.
- S2GRAPH-94: Add description for project layout on README.
- S2GRAPH-112: Additional refinements in README.md
- S2GRAPH-111: typo fix: getServiceLable -> getServiceLabel

@dev
https://markmail.org/search/?q=s2graph-dev#query:s2graph-dev%20list%3Aorg.apache.s2graph.dev%20from%3A%22Jong%20Wook%20Kim%20(JIRA)%22+page:1+mid:l4bbzcnudt7smfb5+state:results

Please join me in congratulating Jongwook.

Re: [DISCUSS]: asking about future of s2graph

[Hwansung Yu]

Hi,

Thank you for Justin.
I opened discussion on the @private.

https://lists.apache.org/thread.html/e2562a2eb8eb68e204d8a76ab1a5e3dc571fe8889cf0723d50d48750@%3Cprivate.s2graph.apache.org%3E

If there are no PPMC objections, is it the next step to let our mentor add
committers?

Thanks,
Hwansung

2018년 11월 6일 (화) 오전 5:39, Justin Mclean 님이 작성:

> Hi,
>
> Here is the original discussion [1] on the private list (over 2 years
> ago!). I'm surprised these people have kept on with the project. While not
> as formal as what some projects do (having a formal VOTE thread), it's up
> to each PPMC to decide (and hopefully document) on how to appoint
> committers and it looks like the consensus was to add the people discussed.
> I suggest you have a discussion on the @private list and if there's no PPMC
> objections (seem unlikely) just go ahead and add them as committers perhaps
> with an apology for taking so long.
>
> Thanks,
> Justin
>
> 1.
> https://lists.apache.org/thread.html/1160237c8961daa72f45fd87b2b3c3b3185ba8bbb2c05f7982ea0d02@%3Cprivate.s2graph.apache.org%3E
>
>

Re: [DISCUSS]: asking about future of s2graph

[Hwansung Yu]

Hi,

I totally agree with Justin's opinion.

I think it is most important to add a new committer and ppmc to grow our
community.

I think there are two candidates for the conditions.
They are Jongwook Kim and Hyunsung Jo.
They were involved in several issues.
In particular, Hyunsung Jo worked for the community building at the Apache
conference.

In the previous mailing issue, there was a thread to add Hyunsung Jo as
committer, but no action was taken after Voting.

We do not know how to do it because we have no experience in adding
commiters.

Justin, can you tell us how we can add Committer or PPMC?

Thanks.

2018년 11월 4일 (일) 오전 8:14, Justin Mclean 님이 작성:

> HI,
>
> I think the biggest issue you face is adding new committers and PPMCs
> members. I find it hard to believe that in the 3 years of incubation that
> your PPMC haven't found a single candidate to make a committer or PPMC
> member. Without growing your community in that way it's unlikely you would
> graduate from the incubator even if everything else was in order.
>
> Thanks,
> Justin
>

Re: Podling Report Reminder - September 2018

[Hwansung Yu]

As Doyung said in previous report emails, three things are important for
graduation.

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

The third release is what we have to discuss and do in the community.

Increasing user and contirubutor and activating community seem like the
same issue on board.

Previously (in November 2016, when I looked up the mail) there was a
discussion to add a new committer, but the committer was not added. how you
think about finishing this discussion and adding a committer.

I think most graph database projects has small community compared to other
major apache projects.
So I think it is not easy to make new users or developers feel attractive.
But small communities are not always meaningless projects.

What are some ways to activate our community? Can you help me?

2018년 9월 10일 (월) 14:52, Sergio Fernández 님이 작성:

> signed-off
>
> I think we should discuss the future of the podling sooner than later. I
> can see the graduation farther than ever.
>
> On Sun, Sep 2, 2018, 20:33 DO YUNG YOON  wrote:
>
> > 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 

Re: Podling Report Reminder - September 2018

[Hwansung Yu]

Hi folks.


As Doyung said in previous report emails, three things are important for
graduation.

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

The third release is what we have to discuss and do in the community.

Increasing user and contirubutor and activating community seem like the
same issue on board.

Previously (in November 2016, when I looked up the mail) there was a
discussion to add a new committer, but the committer was not added. how you
think about finishing this discussion and adding a committer.

I think most graph database projects has small community compared to other
major apache projects.
So I think it is not easy to make new users or developers feel attractive.
But small communities are not always meaningless projects.

What are some ways to activate our community? Can you help me?



On Mon, Sep 10, 2018 at 2:52 PM Sergio Fernández  wrote:

> signed-off
>
> I think we should discuss the future of the podling sooner than later. I
> can see the graduation farther than ever.
>
> On Sun, Sep 2, 2018, 20:33 DO YUNG YOON  wrote:
>
> > 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
> > > ---
> > >
> > > 

[jira] [Created] (S2GRAPH-239) Support various query and its examples in graphql

[Hwansung Yu (JIRA)]

Hwansung Yu created S2GRAPH-239:
---

 Summary: Support various query and its examples in graphql
 Key: S2GRAPH-239
 URL: https://issues.apache.org/jira/browse/S2GRAPH-239
 Project: S2Graph
  Issue Type: Improvement
Reporter: Hwansung Yu


Graphql is more familiar to people than s2graph.
Most of the existing s2graph queries need to be provided as graphql queries.
Providing a variety of s2graph queries to graphql will help the community and 
newbies.
For example, in the rest api of s2graph, it is possible to filter the result 
using the where clause, but I do not know how it is supported in graphql.
And, as queries are added, more examples need to be added.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (S2GRAPH-226) Provide example spark jobs to explain how to utilize WAL log.

[Hwansung Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/S2GRAPH-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hwansung Yu updated S2GRAPH-226:

Priority: Minor  (was: Major)

> Provide example spark jobs to explain how to utilize WAL log.
> -
>
> Key: S2GRAPH-226
> URL: https://issues.apache.org/jira/browse/S2GRAPH-226
> Project: S2Graph
>  Issue Type: New Feature
>  Components: s2core, s2jobs
>Reporter: DOYUNG YOON
>Assignee: DOYUNG YOON
>Priority: Minor
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Even though s2graph publish all incoming vertex/edge into Kafka, there is no 
> example showing how to use this WAL log.
> I suggest adding a simple example showing how to process WAL and let me 
> explain what use cases this example can benefit.
> At kakao, s2graph have been used as the fact storage, which store all user's 
> activities such as click content, buy a product, search query.
> {noformat}
> [{
>   "timestamp": 1,
>   "elem": "e",
>   "from": "steamshon",
>   "to": "s2graph",
>   "label": "search_query",
>   "props": {}
> }, {
>   "timestamp": 10,
>   "elem": "e",
>   "from": "steamshon",
>   "to": "github.com/apache/incubator-s2graph",
>   "label": "content_click",
>   "props": {}
> }, {
>   "timestamp": 12,
>   "elem": "v",
>   "id": "steamshon",
>   "serviceName": "s2graph",
>   "columnName": "user",
>   "props": {
>   "gender": "M"
>   }
> }]
> {noformat}
> Each activity, label in s2graph words, consisting of their own graph, but 
> when they are all connected together, then it gives much more information. 
> Above edges can be aggregated as Vertex.
> It is up to users how to connect each graph, but in our case, we used `user` 
> to merge multiple graphs. for example, we made each activity such as click 
> content, buy a product, search query all use the same `userId` for the same 
> `user`. 
> Below is simple example data.
> {noformat}
> {
>   "timestamp": 10,
>   "elem": "v",
>   "id": "steamshon",
>   "serviceName": "s2graph",
>   "columnName": "user",
>   "props": {
>   "gender": "M",
>   "edges": [{
>   "timestamp": 1,
>   "to": "s2graph",
>   "label": "search_query",
>   "props": {}
>   }, {
>   "timestamp": 10,
>   "to": "github.com/apache/incubator-s2graph",
>   "label": "content_click",
>   "props": {}
>   }]
>   }
> }
> {noformat}
> This connected graph can be used not only for OLTP but also OLAP.
> I believe s2graph WAL log is good way to integrate OLTP and OLAP, and adding 
> this example can help for user to understand how to leverage it.
> [desing doc(work in 
> progress)|https://docs.google.com/document/d/12vsJFWTKoDrYxD-NhOoCaJdvFg8it2wYqIABA0DXYeA/edit?usp=sharing]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (S2GRAPH-238) Replace common.sh file path in movielens example

[Hwansung Yu (JIRA)]

Hwansung Yu created S2GRAPH-238:
---

 Summary: Replace common.sh file path in movielens example  
 Key: S2GRAPH-238
 URL: https://issues.apache.org/jira/browse/S2GRAPH-238
 Project: S2Graph
  Issue Type: Wish
Reporter: Hwansung Yu


Most of the movie lens example include common.sh in the shell script.
However, common.sh is a very common name and path is ambiguous.
For example, if you have the common.sh file of other project in 
"/usr/local/bin", it will not be included in the shell script as you wish.
Therefore, you need to replace the path with an absolute path through a 
variable.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (S2GRAPH-237) Refactor unused variable on AnnoyIndexBuildSink class

[Hwansung Yu (JIRA)]

Hwansung Yu created S2GRAPH-237:
---

 Summary: Refactor unused variable on AnnoyIndexBuildSink class
 Key: S2GRAPH-237
 URL: https://issues.apache.org/jira/browse/S2GRAPH-237
 Project: S2Graph
  Issue Type: Bug
Reporter: Hwansung Yu
Assignee: Hwansung Yu



{code:java}
val df = repartition(preprocess(inputDF), 
inputDF.sparkSession.sparkContext.defaultParallelism)

if (inputDF.isStreaming) throw new IllegalStateException("AnnoyIndexBuildSink 
can not be run as streaming.")
else {
  ALSModelProcess.buildAnnoyIndex(conf, inputDF)
}
{code}

In "write" method of AnnoyIndexBuildSink class, variable "df" is never used.
So, repartition does not working .
I think that second parameter of buildAnnoyIndex shoule be "df", not "inputDF".





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (S2GRAPH-236) Set up a convention of configurations between projects.

[Hwansung Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/S2GRAPH-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hwansung Yu updated S2GRAPH-236:

Priority: Trivial  (was: Major)

> Set up a convention of configurations between projects.
> ---
>
> Key: S2GRAPH-236
> URL: https://issues.apache.org/jira/browse/S2GRAPH-236
> Project: S2Graph
>  Issue Type: Improvement
>        Reporter: Hwansung Yu
>Priority: Trivial
>
> The configurations are not uniform among several projects.
> For example, for h2 db, some projects use file url and others use tcp url.
> {code:java}
> "db.default.url":"jdbc:h2:tcp://localhost/./var/metastore;MODE=MYSQL"
> "db.default.url":"jdbc:h2:file:./var/metastore;MODE=MYSQL"
> {code}
> This causes a crash when running example in the project.
> It is impossible all the settings at once.
> Therefore, I want to try to solve some of the conflicts while running the 
> example for important settings like db setting.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (S2GRAPH-236) Set up a convention of configurations between projects.

[Hwansung Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/S2GRAPH-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593111#comment-16593111
 ] 

Hwansung Yu commented on S2GRAPH-236:
-

[~steamshon]

I misunderstood.
I tried it again and it works fine. I will close the issue.

> Set up a convention of configurations between projects.
> ---
>
> Key: S2GRAPH-236
> URL: https://issues.apache.org/jira/browse/S2GRAPH-236
> Project: S2Graph
>  Issue Type: Improvement
>        Reporter: Hwansung Yu
>Priority: Major
>
> The configurations are not uniform among several projects.
> For example, for h2 db, some projects use file url and others use tcp url.
> {code:java}
> "db.default.url":"jdbc:h2:tcp://localhost/./var/metastore;MODE=MYSQL"
> "db.default.url":"jdbc:h2:file:./var/metastore;MODE=MYSQL"
> {code}
> This causes a crash when running example in the project.
> It is impossible all the settings at once.
> Therefore, I want to try to solve some of the conflicts while running the 
> example for important settings like db setting.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (S2GRAPH-236) Set up a convention of configurations between projects.

[Hwansung Yu (JIRA)]

Hwansung Yu created S2GRAPH-236:
---

 Summary: Set up a convention of configurations between projects.
 Key: S2GRAPH-236
 URL: https://issues.apache.org/jira/browse/S2GRAPH-236
 Project: S2Graph
  Issue Type: Improvement
Reporter: Hwansung Yu


The configurations are not uniform among several projects.

For example, for h2 db, some projects use file url and others use tcp url.
{code:java}
"db.default.url":"jdbc:h2:tcp://localhost/./var/metastore;MODE=MYSQL"
"db.default.url":"jdbc:h2:file:./var/metastore;MODE=MYSQL"
{code}
This causes a crash when running example in the project.

It is impossible all the settings at once.
Therefore, I want to try to solve some of the conflicts while running the 
example for important settings like db setting.

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (S2GRAPH-235) Fix typo errors in S2GraphQL MD

[Hwansung Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/S2GRAPH-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hwansung Yu updated S2GRAPH-235:

Description: 
S2Graph MD is out of update.

So, it is need to update document and fix typo errors.

  was:Correction of typographical errors on commands that do not work due to 
typos.


> Fix typo errors in S2GraphQL MD
> ---
>
> Key: S2GRAPH-235
> URL: https://issues.apache.org/jira/browse/S2GRAPH-235
> Project: S2Graph
>  Issue Type: Improvement
>        Reporter: Hwansung Yu
>Priority: Trivial
>
> S2Graph MD is out of update.
> So, it is need to update document and fix typo errors.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (S2GRAPH-235) Fix typo errors in S2GraphQL MD

[Hwansung Yu (JIRA)]

Hwansung Yu created S2GRAPH-235:
---

 Summary: Fix typo errors in S2GraphQL MD
 Key: S2GRAPH-235
 URL: https://issues.apache.org/jira/browse/S2GRAPH-235
 Project: S2Graph
  Issue Type: Improvement
Reporter: Hwansung Yu


Correction of typographical errors on commands that do not work due to typos.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (S2GRAPH-164) Update s2graph website for new release (0.2.0)

[Hwansung Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/S2GRAPH-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141024#comment-16141024
 ] 

Hwansung Yu commented on S2GRAPH-164:
-

I updated download page,(include 0.2.0 release)
and also add link for maven artifact.



> Update s2graph website for new release (0.2.0)
> --
>
> Key: S2GRAPH-164
> URL: https://issues.apache.org/jira/browse/S2GRAPH-164
> Project: S2Graph
>  Issue Type: Task
>        Reporter: Hwansung Yu
>        Assignee: Hwansung Yu
>Priority: Minor
>
> As the second release, the website also needs to be updated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Hwansung Yu]

+1 (non-binding)

I tried RC2 on Mac OS 10.12.5 , SBT 0.13.9, SCALA 2.12.1, Java(TM) SE
Runtime Environment (build 1.8.0_121-b13).

I tested the same as others tested.
All tests passed.

Thanks.

Hwansung

On Mon, Aug 7, 2017 at 6:37 PM, Min-Seok Kim  wrote:

> +1 (non-binding)
>
> The followings are tried on macOS Sierra, SBT 0.13.9, SCALA 2.11.7,
> Java(TM) SE Runtime Environment (build 1.8.0_121-b13).
>
> 1. Checksums and PGP signatures are valid
> 2. Release consists of source code only, no binaries(find . -type f -exec
> file {} \; | grep -v text)
> 3. DISCLAIMER is correct, filenames include "incubating", top level NOTICE
> and LICENSE files.
> 4. Check license header on files by following DEVELOPMENT.md.
> 5. `sbt package` then, run `bin/example.sh` on
> `target/apache-s2graph-0.2.0-incubating-bin/` is passed.
> 6. `sbt compile 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
>
> Minseok
>
> 2017-08-07 17:13 GMT+09:00 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  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: [DISCUSSION] second release schedule and scope

[Hwansung Yu]

 > > 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 specified number of partition by prefix
> > > salt. This is optimization step so can be revisited once we have
> > > functionality working.
> > >
> > > Note that composite index is only for comparing equality so following
> > > traversal can't take advantage of index.
> > >
> > > ```
> > > g.V().has('name', 'hercules').has('age', inside(20, 50))
> > > ```
> > >
> > > 2. mixed
> > >
> > > Mixed indexes retrieve vertices or edges by any combination of
> previously
> > > added property keys. full text search can be powered by mixed index,
> but
> > it
> > > may slower than composite index since it include external index backend
> > > search(lucene, solr, elasticsearch, ...).
> > >
> > > this example is how user can create mixed index on titan.
> > >
> > > ```
> > >
> > >
> > mgmt.buildIndex('nameAndAge',Vertex.class).addKey(name,
> Mapping.TEXT.getParameter()).addKey(age,Mapping.TEXT.getParameter()).
> buildMixedIndex("search")
> > > ```
> > > user can decide use tokenizer when search engine index(named search) by
> > > specifing Mapping(String or TEXT, default TEXT provide full text
> search).
> > >
> > > then following traversal take benefit from `nameAndAge` index.
> > >
> > > ```
> > > g.V().has('name', textContains('hercules')).has('age', inside(20, 50))
> > > g.V().has('name', textContains('hercules'))
> > > g.V().has('age', lt(50))
> > > ```
> > >
> > > we can use elasticsearch/lucene/solr as index backend for this type of
> > > index and actual tasks can be splitted by as following.
> > >
> > > If there is no objection, then I will create index task and list above
> > > subtasks under it.
> > >
> > > One possible tasks list can be described as following.
> > >
> > > 1. Management Client:
> > > - add option to speficy index type on creating ServiceColumn/Label.
> > > 2. Storage:
> > > - add method to build mutation for storage backend when set of
> > > vertexs/edges are given.
> > > - add method to call index backend with built mutation.
> > > 3. Serializer/Deserializer:
> > > - serializer: when a edge/vertex is given, build SKeyValue which can be
> > > used by storage methods.
> > > - deserializer: when byte array is given, build a Vertex/Edge that can
> be
> > > used by storage methods.
> > > 4. ProviderOptimization
> > > - tinkerpop ask provider to translate given traversal into
> implementation
> > > specific functions.
> > > - not sure if this is necessary with my limited knowledge so far, but
> > need
> > > to check once S2Graph internal provid

Re: [DISCUSSION] second release schedule and scope

[Hwansung Yu]

Sorry for late reply.

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  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  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
> >
> >
>

Re: [DISCUSS] decide actual contents on our web site.

[Hwansung Yu]

I totally agree your opinion.
Making our web site is as important as making S2Graph.
I think it is enough that you mentioned above.
I can contribute easily to create download page and release note.

Who could contribute to other things in list?

On Wed, Nov 2, 2016 at 10:37 AM, DO YUNG YOON  wrote:

> Hi folks.
>
> We have not discussed the contents of our website yet, and I think it is
> time to discuss it in details.
>
> Following is my suggestions and please feel free to comment on them.
>
> 1. create download pages and put release note there.
> 2. Separate `Use` and `Learn`.
> 2.1 `Use`
> - Overview: introduction to model.
> - Quickstart: getting started manual.
> - Examples: more examples can help user to undestand usecases.
> 2.2 `Learn`
> - Basic Concept: Snapshot/Index Edge, Index, Query, Bulk Loader, Super
> Node, Consistency, Storage Backend, etc.
> - Resources: Presentation materials
> 3. Contribute
>   - Contribution Guide: how to get involved.
> - Work In Progress: list up starter tasks, feature branches so any new
> contributor can easily contribute.
> - Mailling Lists
> - Source Repository
> - Issue Tracking
>
> 4. Project
>   - Meetings
> - F.A.Q
> I am sure above suggestion is very arguable, but I just want to begin this
> discussion because I think it is important.
> Please give any feedback and hopefully want others to get involve to make
> our site better shape.
>
> Thanks.
> DOYUNG YOON
>

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

[Hwansung Yu]

I managed @s2graph account at twitter.
In my opinion, first we need to write release note at our website(
http://s2graph.incubator.apache.org/),
and then accounce to twitter is better.
So, I'm preparing release note. (Sorry for late)

How about you?



On Wed, Nov 2, 2016 at 6:12 PM, Sergio Fernández  wrote:

> who manages the @s2graph account at twitter?
> https://twitter.com/s2graph looks pretty abandoned
> it'd be cool to have there 0.1.0-incubating announcement ;-)
>
> On Mon, Oct 31, 2016 at 7:48 AM, DO YUNG YOON  wrote:
>
> > 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"  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 
> 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 
> > > 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
> > > 

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

[Hwansung Yu]

+1 (non-binding)

I checked S2Graph queries everything looks great!

Test ENV.
- OS X 10.11.6
- openjdk 1.8.0_65

On Tue, Oct 11, 2016 at 11:09 PM, daewon  wrote:

> +1 (non-binding)
>
> I tested this on stretch/sid(debian) with openjdk version "1.8.0_91"
>
> * Can run s2graph with no error.
> * Test success on exampe.sh
>
>
> On Tue, Oct 11, 2016 at 8:24 PM Sergio Fernández 
> wrote:
>
> > +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_91, Scala, 2.11.7, SBT 0.13.9, Debian amd64)
> >
> >
> > I've got quite some new warning packing s2rest_play, just that you're
> > aware.
> >
> > Good work, guys!
> >
> >
> >
> > On Mon, Oct 10, 2016 at 2:30 PM, DO YUNG YOON  wrote:
> >
> > > 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.
> > >
> >
> >
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925 <+43%20660%202747925>
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>

[jira] [Commented] (S2GRAPH-3) Create the project website

[Hwansung Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/S2GRAPH-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329255#comment-15329255
 ] 

Hwansung Yu commented on S2GRAPH-3:
---

Thanks.


> Create the project website
> --
>
> Key: S2GRAPH-3
> URL: https://issues.apache.org/jira/browse/S2GRAPH-3
> Project: S2Graph
>  Issue Type: Task
>Reporter: Hyunsik Choi
>        Assignee: Hwansung Yu
>Priority: Minor
> Fix For: 0.1.0
>
>
> We need the project site. The website guide is available at 
> http://incubator.apache.org/guides/sites.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Which is better to locate "find service name by label name" in core classes?

[Hwansung Yu]

I think 'Label' class is better.

I'm not sure how your implementaion, but it looks label's utility.


Best regards.

On Tue, May 17, 2016 at 5:58 PM, Jun Ki Kim  wrote:

> Hi, folks.
>
> I want to add model utility function to find service name by given label
> name in s2core.
> I know this is very simple utility implementation.
> However, It it better to choose suitable the location for our code
> usability.
> That's why I am sending  email to guys.
>
> `Service` class? or `Label' class? or ... Graph?
>
> Please give me any suggestion or your thoughts, and then I want to make
> sure the location.
>
> Thanks.
>
> Best regards,
> Junki kIm
>

Re: Website for s2graph.

[Hwansung Yu]

Thank you for your help.

I created JIRA issue.

https://issues.apache.org/jira/browse/INFRA-11806


Regards.

On Wed, May 4, 2016 at 10:58 AM, Hyunsung Jo <hyunsung...@gmail.com> wrote:

> Hwansung,
>
> Please take a look at the following JIRA:
> https://issues.apache.org/jira/browse/INFRA-8972
>
> It seems like we should
> 1. request for a SVN directory
> 2. check in the source code to the SVN repo
> 3. request for deployment via https://infra.apache.org/officers/webreq
> (only
> officers and members seem to have access for this)
>
> So why don't you go ahead and open a JIRA request for creation of SVN
> directory http://svn.apache.org/repos/asf/incubator/s2graph/site/ ?
>
> Regards,
>
> Jo
>
>
> On Wed, May 4, 2016 at 10:26 AM Hwansung Yu <deejayf...@gmail.com> wrote:
>
> > I want create website for s2graph.
> >
> > According to the guide(http://www.apache.org/dev/infra-contact), I
> should
> > upload code to svn and request to webreq(
> > https://infra.apache.org/officers/webreq).
> >
> > However I have no access.
> >
> > Webreq is opened to only officer and commiter.
> >
> > So, I need help about belows.
> >
> > 1. How can I create svn repo?
> > 2. Please, reqeust to webreq.
> >
> > Best regrards.
> >
>

Re: About s2ab query needs status code in result.

[Hwansung Yu]

I agree to throw explicit exception.
I created an issue.

https://issues.apache.org/jira/browse/S2GRAPH-67



On Wed, Mar 23, 2016 at 2:49 PM, DO YUNG YOON <sho...@gmail.com> wrote:

> Hi Hwansung.
>
> Seems like it is validation check issue on 'experiment' routes on s2rest.
> I think it is better to throw explicit exception(dedicated exception or
> BadQueryException which currently exist).
> Not only this cases, but also I think there is lots to work on regarding
> exception handling on controller at s2rest.
> Can you create issue on exception handling on rest? I am definitely up for
> this and willing to work on this.
>
>
> On Wed, Mar 23, 2016 at 2:22 PM Hwansung Yu <deejayf...@gmail.com> wrote:
>
> > When  I query with invalid json by s2ab,
> > s2graph doesn't any notice for user.
> >
> > For example,
> >
> > curl -X POST -H "Content-Type: application/json" -d '{
> >  "[[user_id]]": "A"
> >  "[[filter]]" : "(1,2,3)"
> > }'
> >
> >
> 'localhost:9000/graphs/experiment/f1f2a18e-b83e-4828-9441-746e674907e2/test/test
> >
> > Above json body is invalid, because it is missing comma after "A".
> >
> >
> > Below is s2graph result.
> >
> > {
> >   "size": 0,
> >   "degrees": [],
> >   "results": [],
> >   "isEmpty": true
> > }
> >
> > Users of s2graph are hard to find mistakes, because any errors doesn't
> > occur.
> >
> > I have two ideas in this case.
> >
> > First, experiment controller outputs an error instead of sending json
> body
> > to query controller.
> > Seconds, s2graph result contains status field. (like, "status" : "invalid
> > json")
> >
> >
> > Is there any idea?
> >
> >
> >
> > Regards.
> > Hwansung Yu
> >
>

[jira] [Created] (S2GRAPH-67) Experiment route invalid json error handling.

[Hwansung Yu (JIRA)]

Hwansung Yu created S2GRAPH-67:
--

 Summary: Experiment route invalid json error handling.
 Key: S2GRAPH-67
 URL: https://issues.apache.org/jira/browse/S2GRAPH-67
 Project: S2Graph
  Issue Type: Task
Reporter: Hwansung Yu
Priority: Minor


This issue about when query with invalid json on experiment route, s2rest 
doesn't any notice for user.


For example, 

curl -X POST -H "Content-Type: application/json" -d '{
 "[[user_id]]": "A"
 "[[filter]]" : "(1,2,3)"
}' 
'localhost:9000/graphs/experiment/f1f2a18e-b83e-4828-9441-746e674907e2/test/test

Above json body is invalid, because it is missing comma after "A".


Below is s2rest result.

{
  "size": 0,
  "degrees": [],
  "results": [],
  "isEmpty": true
}

Users of s2graph are hard to find mistakes, because any errors doesn't occur.

So experiment controller should outputs an error when query with invalid json.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

About s2ab query needs status code in result.

[Hwansung Yu]

When  I query with invalid json by s2ab,
s2graph doesn't any notice for user.

For example,

curl -X POST -H "Content-Type: application/json" -d '{
 "[[user_id]]": "A"
 "[[filter]]" : "(1,2,3)"
}'
'localhost:9000/graphs/experiment/f1f2a18e-b83e-4828-9441-746e674907e2/test/test

Above json body is invalid, because it is missing comma after "A".


Below is s2graph result.

{
  "size": 0,
  "degrees": [],
  "results": [],
  "isEmpty": true
}

Users of s2graph are hard to find mistakes, because any errors doesn't
occur.

I have two ideas in this case.

First, experiment controller outputs an error instead of sending json body
to query controller.
Seconds, s2graph result contains status field. (like, "status" : "invalid
json")


Is there any idea?



Regards.
Hwansung Yu

Logo is needed

[Hwansung Yu]

Hello, forlks.

I think that it is also important to create enough nice logo to create a
nice code.

So, how about make logo for s2graph?


Regards,
Hwansung Yu