[ 
https://issues.apache.org/jira/browse/HBASE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734901#action_12734901
 ] 

stack commented on HBASE-1685:
------------------------------

I don't see a contrib/stargate/bin.  You going to add it?

On WAR, I can help with that. I just tried it under tomcat.  At a minimum, 
missing hadoop, hbase, and zk jars.  They are not bundled up in the WAR nor do 
we really want to do that.  In doc. we could say, drop WAR where container 
expects it but then you need to add hbase, hadoop, and zk jars into the shared 
deploy directory or something.

WAR heads usually can figure this stuff out so I don't think it too critical.

The start/stop script would be good to have though.

On hbase-1690, generally, basic authentication (as opposed to "BASIC AUTH") and 
access checking is a feature supplied by the container (jetty or tomcat).    
For example, regards basic authentication, its just a config. in the container 
stipulating 'BASIC AUTH' over SSL, etc., hurdle for user to clear before they 
get access to the deployed webapp.  Whatever about read/write hbase perms, 
because you are REST, you can specify which users can POST/PUT and who can GET 
and have the container do the checks for you (See container 'realms' and the 
servlet spec).  I don't think hbase-1690 need be done for 0.20.0, especially if 
gross webapp access is good enough.


> [stargate] package and wiki documentation
> -----------------------------------------
>
>                 Key: HBASE-1685
>                 URL: https://issues.apache.org/jira/browse/HBASE-1685
>             Project: Hadoop HBase
>          Issue Type: Task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.20.0
>
>
> Write package and wiki documentation for the Stargate contrib.
> * Convert spec and transaction examples into package javadoc.
> * Render package javadoc into wiki markup.
> * Write up instructions for starting the service in standalone mode and as a 
> servlet.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to