[
https://issues.apache.org/jira/browse/SQOOP-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003320#comment-15003320
]
Hudson commented on SQOOP-2667:
-------------------------------
SUCCESS: Integrated in Sqoop2 #947 (See
[https://builds.apache.org/job/Sqoop2/947/])
SQOOP-2667. Sqoop2: RESTiliency: Refactore the one line try-catch
(hshreedharan:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=60f54b624b3ebffb10dfa6f5de58b6f42ecedff6])
*
test/src/test/java/org/apache/sqoop/integration/server/InvalidRESTCallsTest.java
> Sqoop2: Improve documentation
> -----------------------------
>
> Key: SQOOP-2667
> URL: https://issues.apache.org/jira/browse/SQOOP-2667
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
>
> We've put together roots of current documentation system more then 3 years
> ago for our first 1.99.1 cut of Sqoop 2. We've only incrementally added few
> pages since then. I recently looked into the docs more carefully as I wanted
> to improve HDFS connector and I would like to propose quite huge overhaul -
> few of the things that immediately came to my mind:
> * I'm really missing a table of context on each page to navigate though the
> entire documentation suite (in some side menu or something)
> * On any formatting error, we print out exception to the documentation and
> won't fail the build.
> * We build the docs in all profiles, even though that it make sense only for
> {{binary}} profile.
> * The connector docs are really, really old - bunch of newly added arguments
> are not mentioned there.
> * In terms of connectors - it seems to me that the docs are focusing on dev
> rather then end user, so I would like to add more context there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
