sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1515) VersionRequestHandler - fixes
Date Mon, 27 Oct 2014 18:03:34 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185520#comment-14185520
] 

ASF subversion and git services commented on SQOOP-1515:
--------------------------------------------------------

Commit fde0eb177d73c5bd6902f601048854dfd8c630df in sqoop's branch refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=fde0eb1 ]

SQOOP-1515: VersionRequestHandler - fixes

(Veena Basavaraj via Jarek Jarcec Cecho)


> VersionRequestHandler - fixes
> -----------------------------
>
>                 Key: SQOOP-1515
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1515
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>         Attachments: SQOOP-1515.patch
>
>
> We have different kinds of versions in the Sqoop system. here is a list of them
> 1. Every configurable has a version that it maintains ( driver has its own version, connectors
have their own version, these are persisted in the Repository in the SQ_CONFIGURABLE and is
exposed in the respective connector and driver apis
> 2. We store all the SQOOP entities in the repository which we today support it using
the bare bones Derby schema. This version is also maintained in the SQ_SYSTEM table and it
tells the current schema version we are now in ( the current schema version is controlled
by the SQOOP code)
> 3. Next we have the actual server version - which is the release version of the SQOOP
such as 1.99.3 or 1.99.4
> 4. REST API protocol_version - which is v1 today , will be v2 if we significantly change
the apis in next version that are not backwards compatible
> 5. SHELL /CLIENT version ( not applicable to the  clients making web requests, we should
be sending client version only when this request is from CLI possibly)
> Before
> FROM REST API
> {code}
> {
> revision: "52d5446af0cb63b739c9773efe1d2534ebe20100",
> protocols: [
> "1"
> ],
> date: "Fri Oct 24 08:09:24 PDT 2014",
> user: "vbasavaraj",
> url: "git://vbasavaraj.local/Users/vbasavaraj/Projects/sqoop2/common",
> version: "2.0.0-SNAPSHOT"
> }
> {code}
> FROM shell
> {code}
> sqoop:000> show version -all 
> client version:
>   Sqoop 2.0.0-SNAPSHOT revision 52d5446af0cb63b739c9773efe1d2534ebe20100 
>   Compiled by vbasavaraj on Fri Oct 24 08:09:24 PDT 2014
> server version:
>   Sqoop 2.0.0-SNAPSHOT revision 52d5446af0cb63b739c9773efe1d2534ebe20100 
>   Compiled by vbasavaraj on Fri Oct 24 08:09:24 PDT 2014
> Protocol version:
>   [1]
> sqoop:000> 
> {code}
> The new JSON has the following things 
> {code}
> //todo
> {code}



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

Mime
View raw message