Appreciate it.
On Fri, Apr 22, 2016 at 11:02 AM Hwansung Yu wrote:
> 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 wrote:
>
> > Hi Hwansung.
> >
> > Seems like it is validati
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 wrote:
> Hi Hwansung.
>
> Seems like it is validation check issue on 'experiment' routes on s2rest.
> I think it is better to throw explicit
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 co
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 i