Return-Path: X-Original-To: apmail-atlas-dev-archive@minotaur.apache.org Delivered-To: apmail-atlas-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E97EE19B00 for ; Fri, 1 Apr 2016 09:25:17 +0000 (UTC) Received: (qmail 97784 invoked by uid 500); 1 Apr 2016 09:25:17 -0000 Delivered-To: apmail-atlas-dev-archive@atlas.apache.org Received: (qmail 97737 invoked by uid 500); 1 Apr 2016 09:25:17 -0000 Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.incubator.apache.org Delivered-To: mailing list dev@atlas.incubator.apache.org Received: (qmail 97726 invoked by uid 99); 1 Apr 2016 09:25:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 09:25:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0B295C0225 for ; Fri, 1 Apr 2016 09:25:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.18 X-Spam-Level: * X-Spam-Status: No, score=1.18 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, KAM_WEIRDTRICK1=1.5, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, TVD_FW_GRAPHIC_NAME_MID=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id OBU5ElI6XUwC for ; Fri, 1 Apr 2016 09:25:14 +0000 (UTC) Received: from e28smtp03.in.ibm.com (e28smtp03.in.ibm.com [125.16.236.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id C6F025F1D5 for ; Fri, 1 Apr 2016 09:25:13 +0000 (UTC) Received: from localhost by e28smtp03.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 1 Apr 2016 14:55:12 +0530 Received: from d28relay04.in.ibm.com (9.184.220.61) by e28smtp03.in.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 1 Apr 2016 14:55:10 +0530 X-IBM-Helo: d28relay04.in.ibm.com X-IBM-MailFrom: venkataramana.m@in.ibm.com X-IBM-RcptTo: dev@atlas.incubator.apache.org Received: from d50lp31.co.us.ibm.com (d50lp31.boulder.ibm.com [9.17.249.32]) by d28relay04.in.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u319OMdB13631992 for ; Fri, 1 Apr 2016 14:54:24 +0530 Message-Id: <201604010924.u319OMdB13631992@d28relay04.in.ibm.com> Received: from localhost by d50lp31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 1 Apr 2016 03:25:07 -0600 Received: from smtp.notes.na.collabserv.com (192.155.248.67) by d50lp31.co.us.ibm.com (192.168.2.141) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256/256) Fri, 1 Apr 2016 03:25:03 -0600 X-IBM-Helo: smtp.notes.na.collabserv.com X-IBM-MailFrom: venkataramana.m@in.ibm.com X-IBM-RcptTo: dev@atlas.incubator.apache.org Received: from /spool/local by smtp.notes.na.collabserv.com with smtp.notes.na.collabserv.com ESMTP for from ; Fri, 1 Apr 2016 09:25:02 -0000 Received: from us1a3-smtp02.a3.dal06.isc4sb.com (10.106.154.159) by smtp.notes.na.collabserv.com (10.106.227.16) with smtp.notes.na.collabserv.com ESMTP; Fri, 1 Apr 2016 09:25:00 -0000 Received: from us1a3-mail58.a3.dal09.isc4sb.com ([10.142.3.114]) by us1a3-smtp02.a3.dal06.isc4sb.com with ESMTP id 2016040109245921-132405 ; Fri, 1 Apr 2016 09:24:59 +0000 MIME-Version: 1.0 In-Reply-To: <56FD3DA2.6090800@nanthrax.net> Subject: Re: [PROPOSAL] Java/Scala API on top of the REST API ? To: dev@atlas.incubator.apache.org From: "Venkata R Madugundu" Date: Fri, 1 Apr 2016 14:54:49 +0530 References: <56FD2F96.60303@nanthrax.net> <201603311459.u2VEx0Ix36241454@d28relay04.in.ibm.com> <56FD3DA2.6090800@nanthrax.net> X-KeepSent: C250B7DE:79380284-00257F88:00330D49; type=4; name=$KeepSent X-Mailer: IBM Notes Release 9.0.1SHF211 December 19, 2013 X-LLNOutbound: False X-Disclaimed: 15191 X-TNEFEvaluated: 1 Content-type: multipart/related; Boundary="0__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9" x-cbid: 16040109-0009-0000-0000-00000BB9C430 X-IBM-ISS-SpamDetectors: Score=0.371236; FL=0; FP=0; FZ=0; HX=0; KW=0; PH=0; SC=0.371236; ST=0; TS=0; UL=0; ISC= X-IBM-ISS-DetailInfo: BY=3.00005104; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000156; SDB=6.00681689; UDB=6.00312945; UTC=2016-04-01 09:25:02 x-cbparentid: 16040109-5938-0000-0000-000002D9BBE7 --0__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9 Content-type: multipart/alternative; Boundary="1__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9" --1__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9 Content-Transfer-Encoding: quoted-printable Content-type: text/plain; charset=ISO-8859-1 Here is the Swagger JIRA - https://issues.apache.org/jira/browse/ATLAS-328 By the way, per my last observation, the Atlas REST documentation is a bit dated. To keep it really upto date, generating a Swagger driven documentation which builds off the Java REST API definition will always keep it in sync. For now, to know the exact REST end point, I have only been consulting the Atlas code (java REST resources like TypesResource.java, EntityResource.java, MetadataDiscoveryResource.java, HiveLineageResource.java etc.,) To see what all clients Swagger can generate, go to http://editor.swagger.io/#/ and click on the menu "Generate Client" on the very top. It shows you 30 odd languages in which a client can be generated, and Java/Scala/Python/Javascript are few among them. Thanks Venkat From: Jean-Baptiste Onofr=E9 To: dev@atlas.incubator.apache.org Date: 31/03/16 08:39 PM Subject: Re: [PROPOSAL] Java/Scala API on top of the REST API ? Hi Venkata, tanks, I missed this when taking a look on the code. I will test the integration then, and I will work on the Swagger integration. I don't find a Jira about that, should I create one ? Thanks ! Regards JB On 03/31/2016 04:59 PM, Venkata R Madugundu wrote: > There is an AtlasClient.java which wraps around the REST API if you want > to take a look at. > \client\src\main\java\org\apache\atlas\AtlasClient.java > > Also take a look at > \webapp\src\main\java\org\apache\atlas\examples\QuickStart.java to see > how AtlasClient can be used. > > There is a JIRA open for Swagger integration so that one can generate > typed API bindings to interact with Atlas REST API. > As Atlas REST is JAX RS compliant, one can actually make Swagger > generate bindings for different languages (atleast we did > it for Javascript and Python) > > For java based REST calls, we have used google gson for JSON > serialization/deserialization and Apache HttpClient to dispatch REST > requests. > > > Inactive hide details for Jean-Baptiste Onofr=E9 ---31/03/2016 07:44:31 > PM---Hi guys, I like the Atlas REST API, and the way it'sJean-Baptiste > Onofr=E9 ---31/03/2016 07:44:31 PM---Hi guys, I like the Atlas REST API, > and the way it's documented. > > From: Jean-Baptiste Onofr=E9 > To: dev@atlas.incubator.apache.org > Date: 31/03/16 07:44 PM > Subject: [PROPOSAL] Java/Scala API on top of the REST API ? > > ------------------------------------------------------------------------ > > > > Hi guys, > > I like the Atlas REST API, and the way it's documented. > > In some case, to simplify the integration of Atlas in third party > applications, maybe it would be great to provide a Java and Scala APIs > on top of the REST API (wrapping the transport, and adding some > "control" and DataObject/JSON). > For instance, I'm PoCing some shell & Karaf commands to manipulate Atlas > (as we did in Falcon for instance). In that case, even if REST API is > convenient, it's not as straight forward as a turnkey API. > For instance, it's what we did in Syncope: we provide syncope-client on > top of the Syncope REST API. > > Thoughts ? > > Regards > JB > -- > Jean-Baptiste Onofr=E9 > jbonofre@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > > -- Jean-Baptiste Onofr=E9 jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com --1__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9 Content-Transfer-Encoding: quoted-printable Content-type: text/html; charset=ISO-8859-1 Content-Disposition: inline

Here is the Swagger JIRA - https://issues.apache.org/jira/browse/ATLAS-328<= /a>
By the way, per my last observation, the Atlas REST documentation is= a bit dated. To keep it really upto date, generating a Swagger driven docu= mentation which builds off the Java REST API definition will always keep it= in sync. For now, to know the exact REST end point, I have only been consu= lting the Atlas code (java REST resources like TypesResource.java, EntityRe= source.java, MetadataDiscoveryResource.java, HiveLineageResource.java etc.,= )

To see what all clients Swagger can generate, go to http://editor.swagger.io/#/ and click on the= menu "Generate Client" on the very top. It shows you 30 odd lang= uages in which a client can be generated, and Java/Scala/Python/Javascript = are few among them.

Thanks
Venkat

3D"InactiveJean-Baptiste Onofr=E9 ---31/03/2016 08:39:47 PM---Hi = Venkata, tanks, I missed this when taking a look on the code.
From: Je= an-Baptiste Onofr=E9 <jb@nanthrax.net>
To: dev@atlas.incubator.apach= e.org
Date: 31/03/16 08:39 PM
Subject: Re: [PROPOSAL] Java/Scala API on t= op of the REST API ?




Hi Venkata,

tanks= , I missed this when taking a look on the code.

I will test the inte= gration then, and I will work on the Swagger
integration. I don't find = a Jira about that, should I create one ?

Thanks !
Regards
JB
On 03/31/2016 04:59 PM, Venkata R Madugundu wrote:
> There is a= n AtlasClient.java which wraps around the REST API if you want
> to t= ake a look at.
> \client\src\main\java\org\apache\atlas\AtlasClient.j= ava
>
> Also take a look at
> \webapp\src\main\java\org\a= pache\atlas\examples\QuickStart.java to see
> how AtlasClient can be = used.
>
> There is a JIRA open for Swagger integration so that = one can generate
> typed API bindings to interact with Atlas REST API= .
> As Atlas REST is JAX RS compliant, one can actually make Swagger<= br>> generate bindings for different languages (atleast we did
> i= t for Javascript and Python)
>
> For java based REST calls, we = have used google gson for JSON
> serialization/deserialization and Ap= ache HttpClient to dispatch REST
> requests.
>
>
> = Inactive hide details for Jean-Baptiste Onofr=E9 ---31/03/2016 07:44:31
= > PM---Hi guys, I like the Atlas REST API, and the way it'sJean-Baptiste=
> Onofr=E9 ---31/03/2016 07:44:31 PM---Hi guys, I like the Atlas RES= T API,
> and the way it's documented.
>
> From: Jean-Bapt= iste Onofr=E9 <jb@nanthrax.net>
> To: dev@atlas.incubator.apach= e.org
> Date: 31/03/16 07:44 PM
> Subject: [PROPOSAL] Java/Scal= a API on top of the REST API ?
>
> ----------------------------= --------------------------------------------
>
>
>
>= ; Hi guys,
>
> I like the Atlas REST API, and the way it's docu= mented.
>
> In some case, to simplify the integration of Atlas = in third party
> applications, maybe it would be great to provide a J= ava and Scala APIs
> on top of the REST API (wrapping the transport, = and adding some
> "control" and DataObject/JSON).
> F= or instance, I'm PoCing some shell & Karaf commands to manipulate Atlas=
> (as we did in Falcon for instance). In that case, even if REST API= is
> convenient, it's not as straight forward as a turnkey API.
&= gt; For instance, it's what we did in Syncope: we provide syncope-client on=
> top of the Syncope REST API.
>
> Thoughts ?
>> Regards
> JB
> --
> Jean-Baptiste Onofr=E9
> = jbonofre@apache.org
> h= ttp://blog.nanthrax.net
> Talend - http://www.talend.com
>
>>

--
Jean-Baptiste Onofr=E9
jbonofre@apache.org
<= tt>http://blog.nanthrax.net
Talend - http://www.talend= .com



--1__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9-- --0__=8FBBF51BDFA08BD98f9e8a93df938690918c8FBBF51BDFA08BD9--