As long as somebody can do the fixup, that should be fine. But this person better be one of hbase committers. I know how (sometimes) response from [email protected] could be. By that time, anybody can retrieve the sensitive information from google's index cache.
Cheers On Jun 25, 2011, at 11:23 AM, Andrew Purtell <[email protected]> wrote: > No, I proposed (and Todd seconded I believe) turning off the ability to edit > comments in the JIRA configuration for the HBase project. > > But if there is a comment that has a legal issue, it would still be possible > to have the JIRA administrator remove it. > > Best regards, > > - Andy > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein (via > Tom White) > From: Ted Yu <[email protected]> > To: [email protected]; [email protected] > Sent: Saturday, June 25, 2011 3:21 AM > Subject: Re: editing JIRA comments > > One side note, I reserve my right to edit JIRA comments / contents if the > comments or contents of the JIRA reveal my company (or other company)'s IP. > > Aaron has done a good job of presenting redacted log in his JIRA. But > sometimes people were in a hurry. > > I hope the above is a legitimate exception to the general rule. > > Thanks > > On Fri, Jun 24, 2011 at 3:11 PM, Ted Yu <[email protected]> wrote: > I will refrain from doing this again. > > > On Fri, Jun 24, 2011 at 3:07 PM, Andrew Purtell <[email protected]> wrote: > -1 on allowing edits of issue comments. > > We had this feature disabled on the HBase project for a while but obviously > it is allowed again. > > Issues are external memory of a project. If they are volatile, that memory is > volatile, which I find unacceptable, if the record can be selectively or > conveniently edited. > > - Andy > > > Subject: [jira] [Issue Comment Edited] (HBASE-451) Remove HTableDescriptor > > from HRegionInfo > > > > >
