tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jihoon Son <jihoon...@apache.org>
Subject Re: [DISCUSSION] Portable remote client APIs
Date Thu, 12 Mar 2015 08:38:43 GMT
+1 for Hyunsik's suggestion.
I totally agree with you.

Warm regards,
Jihoon
2015년 3월 12일 (목) 오후 5:35, Hyunsik Choi <hyunsik@apache.org>님이 작성:

> Here is my suggestion.
>
> I prefer REST API. I think that it would be better than other due to
> the following reasons:
>
>  * No dependency - most of script languages do not need any dependency
> for this approach. Also, C and C++ just needs json library for this
> approach. Please look at JSON for Modern C++
> (https://github.com/nlohmann/json). It just requires to include one
> header and one source file. As a result, there is no dependency
> problem.
>
>  * Portability - most of script languages basically support REST and
> JSON. They don't need client implementation. They can just use REST
> and JSON features in order to access Tajo. If necessary, we can make
> easily some helper libraries for other languages.
>
>  * Secure - It is easy to provide the secure channel and
> authentication method too. Basically, many HTTP API provides HTTP over
> SSL.
>
> Jihoon Kang already started REST API work. If others start to develop
> clients for other languages like C/C++ client over REST API after his
> work, it would be best for us.
>
> Best regards,
> Hyunsik
>
> On Thu, Mar 12, 2015 at 1:32 AM, Hyunsik Choi <hyunsik@apache.org> wrote:
> > Hi folks,
> >
> > Recently, there are three trials to add new remote client APIs.
> >
> > * C/C++ Client over Thrift - https://issues.apache.org/
> jira/browse/TAJO-1264
> > * Add REST Client API - https://issues.apache.org/jira/browse/TAJO-1331
> > * Tajo Python Native Client - https://issues.apache.org/
> jira/browse/TAJO-1367
> >
> > In some aspect, I'm very happy to discuss such an issue. I haven't
> > expected that we are discuss and vote for duplicated efforts.
> >
> > BTW, it would be great if we do not spend our resource on duplicated
> works.
> >
> > In order to rearrange this duplicated works, we need some discussion
> > about their pros and cons. I hope that we consent our direction after
> > this discussion. Otherwise, we can call for a vote for the approach.
> >
> > Best regards,
> > Hyunsik
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message