accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1375) Update README files in proxy module.
Date Tue, 07 May 2013 02:37:15 GMT


Hudson commented on ACCUMULO-1375:

Integrated in Accumulo-1.5-Hadoop-2.0 #100 (See [])
    ACCUMULO-1375 Pull the changes from 1.4 (which came from 1.6) to 1.5 (Revision 1479124)
ACCUMULO-1375 Some more cleanup on the proxy/README (Revision 1478625)

     Result = SUCCESS
elserj : 
Files : 
* /accumulo/branches/1.5/proxy/README

elserj : 
Files : 
* /accumulo/branches/1.5/proxy/README

> Update README files in proxy module.
> ------------------------------------
>                 Key: ACCUMULO-1375
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: David Medinets
>            Assignee: David Medinets
>            Priority: Critical
>             Fix For: 1.5.0, 1.6.0, 1.4.4
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> I looked at the proxy/README today and some things were unclear to me. When I compile
Accumulo from the top level, isn't the proxy submodule included? Why would it need to be built
separately? In order to build the proxy module from within the proxy directory, I needed to
run 'mvn install' at the top level because of a dependency. The file which
needs to be edited is not the one in the build directory, it's the one in the installation
directory. Also, the 'accumulo proxy' command should be run from the installation directory.
> I also got a chance to look at the proxy/python/README file. Perhaps it's just that I
know very little about python but "PYTHONPATH=path/to/generated/api:path/to/thrift/libs python" does not look right. Should there be a ';' before the python command? Will
python people know what the 'path/to/generated/api' and 'path/to/thrift/libs' are?
> My last note - does thrift really need to be installed?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message