One pattern of creating keys might be to do so in a loop. Inside the loop, you may wish to reuse these buffers... or you may wish to create new buffers each you cycle. If the first case, you'll want to ensure that Key copies the bytes. In the second case, it's okay if Key just uses the bytes you give it, since you won't reuse the buffer yourself.
What you wouldn't want to do is create new buffers yourself each time in the loop, and then have the Key constructor copy them into its own buffers. That would be double the work, and an unnecessary performance hit if you're creating a lot of Keys. Side note: I'm not sure if you can control the content of the footer in your email (it might be appended automatically by your employer's mail server or something), but please understand that this list is a public mailing list, and will be distributed to all subscribers, and archived at various websites which monitor these lists. Everything on list is completely open to the public (worldwide). So, the "intended recipient" is "all persons worldwide", and the content of your footer really doesn't apply. It's just noise on a mailing list like this. On Thu, Apr 18, 2019 at 6:33 AM Resnik, Donald J <[email protected]> wrote: > > So I did my first pull request > > https://github.com/apache/accumulo/pull/1105/commits > > Please let me know if there are any issues. > > Just so I understand...what is the value of the option to copy the byte > arrays or not in the Key? > > Thanks, > > Don Resnik > > ________________________________ > > The preceding message (including attachments) is covered by the Electronic > Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for > the person or entity to which it is addressed, and may contain information > that is confidential, protected by attorney-client or other privilege, or > otherwise protected from disclosure by law. If you are not the intended > recipient, you are hereby notified that any retention, dissemination, > distribution, or copying of this communication is strictly prohibited. Please > reply to the sender that you have received the message in error and destroy > the original message and all copies.
