incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Billie Rinaldi <>
Subject Re: Adding Accumulo to Ambari
Date Tue, 18 Jun 2013 23:53:49 GMT

You will create a patch and attach it to the appropriate ticket.  We will
review the patch, giving you feedback and probably requesting revisions,
and you keep making new patches and adding them to the ticket until the
community is happy.  At that point, a committer will commit the patch for

A patch can contain an entire new sub-tree.  If you use svn, "svn status"
shows you the files that have changed in the current directory.  Ones that
are entirely new have a question mark next to them.  To add them to the
patch, use "svn add <fileOrDirectory>".  If you add a directory it
recursively adds all the files in the directory.  To create the patch, use
for example "svn diff > AMBARI-1930-1.patch", then after a first round of
revisions, "svn diff > AMBARI-1930-2.patch".  The one-up numbering isn't
strictly necessary, but it makes it easier to see what is the most recent
patch that needs to be reviewed.

If you want to use git instead, the commands are slightly different.  I can
help you with those as well, if you'd prefer.


On Tue, Jun 18, 2013 at 4:19 PM, Andres Danter <> wrote:

> Hi Billie,
> I was about to start working on adding Accumulo to the Ambari stack
> definition, as outlined on the Ambari wiki.  I have to admit that I'm being
> a bit shy with getting started on this.  I'm mostly worried about
> submitting changes that will clobber something and cause headaches for
> everyone.  I did read the "How to Commit" section on the wiki, but I still
> have a couple of questions regarding the submission of patches.
> 1.  Since I'm not an authorized committer, would you be the one that
> actually commits the patches?  Or will I do it with your approval?
> 2.  Since adding Accumulo to the stack definition involves the creation of
> a new directory structure under ambari-server/src/main/resources/, is it
> considered a patch?  How should I make the work available to the community
> for review?  I can write a document with the details of the service and a
> zip file that contains the new sub-tree.  Would that be sufficient?
> I guess what I'm worried about here is how to proceed once I have a
> finished piece that can be committed, whether it is a completely new
> addition or a patch to existing source.
> Thanks for the help.
> Andres

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message