Hi folks,
I have just joined the list with the purpose of volunteering ideas,
design and development (and whatever else in lifecycle)
related to development of the Python client for accumulo.
I have developed several RESTful clients and libraries before using
web.py and I am about to write anothe
Neither. Looking over the README, it contains information for developers
and users. So, we have a README, user and developer manuals, and a wiki.
This information is clearly for developers, maybe it should go in the
developer manual or on the web site in the developer guide section[1].
It a
I'd like to get a vote by the contributors on which approach to use.
I'll start the voting:
A) +1 because I don't know how much information might be needed and
the information might change for different versions of Accumulo. Also
the README might wind up with many OS-specific sections. And, lastly
[
https://issues.apache.org/jira/browse/ACCUMULO-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423491#comment-13423491
]
Keith Turner commented on ACCUMULO-703:
---
Now that this command is more accessible,
I'm sorry to harp on this topic. What 'thift changes' could exist if I
had just pulled a new copy of trunk?
On Thu, Jul 26, 2012 at 1:08 PM, John Vines wrote:
> It will only regenerate them if there are thrift changes and you have
> thrift installed.
>
> John
>
> On Thu, Jul 26, 2012 at 1:06 PM,
It will only regenerate them if there are thrift changes and you have
thrift installed.
John
On Thu, Jul 26, 2012 at 1:06 PM, David Medinets wrote:
> If the thrift-generated files are already in svn, is there a way for
> 'mvn package -P assemble' to not generate them? Or put another way,
> gener
If the thrift-generated files are already in svn, is there a way for
'mvn package -P assemble' to not generate them? Or put another way,
generate those files via a script and remove the thift-generation from
the maven packaging process?
I built thrift 0.8.0 from source from the tarball available off the
thrift.apache.org web page.
I configured it with:
$ ./configure --prefix=/local/$USER/Installed/local
$ ln -s /local/$USER/Installed/local/bin/thrift ~/bin/thrift
My md5 sum matches the one posted on the webpage.
~/bin is in
[
https://issues.apache.org/jira/browse/ACCUMULO-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423203#comment-13423203
]
Keith Turner commented on ACCUMULO-702:
---
Instead of having a README_UBUNTU file, I
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/6138/#review9499
---
/trunk/core/src/main/java/org/apache/accumulo/core/client/admin/Table
[
https://issues.apache.org/jira/browse/ACCUMULO-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423138#comment-13423138
]
Keith Turner commented on ACCUMULO-703:
---
I applied the patch
> Ad
[
https://issues.apache.org/jira/browse/ACCUMULO-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423125#comment-13423125
]
Keith Turner commented on ACCUMULO-703:
---
I am not sure we should put it in the use
[
https://issues.apache.org/jira/browse/ACCUMULO-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423130#comment-13423130
]
Keith Turner commented on ACCUMULO-703:
---
I think the new patch looks good
Josh Elser created ACCUMULO-704:
---
Summary: Change the target maven lifecycle for user manual pdf
creation
Key: ACCUMULO-704
URL: https://issues.apache.org/jira/browse/ACCUMULO-704
Project: Accumulo
[
https://issues.apache.org/jira/browse/ACCUMULO-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423023#comment-13423023
]
Josh Elser commented on ACCUMULO-702:
-
Yes/no. I'm worried that because you included
15 matches
Mail list logo
