Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase, mail # user - HBase type support


Copy link to this message
-
Re: HBase type support
Doug Meil 2013-03-18, 19:16

Sorry I'm late to this thread but I was the guy behind HBASE-7221 and the
algorithms specifically mentioned were MD5 and Murmur (not SHA-1).  And
implementation of Murmur already exists in Hbase, and the MD5
implementation was the one that ships with Java.

The intent was to include hashing appropriate for use with key
distribution of rowkeys in tables as is often suggested on the dist-lists.
 SHA-1 is probably overkill for the rowkey case, but I wouldn't want to
stop anybody from using SHA-1 if it was appropriate for their needs.

On 3/18/13 8:02 AM, "Michel Segel" <[EMAIL PROTECTED]> wrote:

>Andrew,
>
>I was aware of you employer, which I am pretty sure that they have
>already dealt with the issue of  exporting encryption software and
>probably hardware too.
>
>Neither of us are lawyers and what I do know of dealing with the
>government bureaucracies, it's not always as simple of just filing the
>correct paperwork. (Sometimes it is, sometimes not so much, YMMV...)
>
>Putting the hooks for encryption is probably a good idea. Shipping the
>encryption w the release or making it part of the official release, not
>so much. Sorry, I'm being a bit conservative here.
>
>IMHO I think fixing other issues would be of a higher priority, but
>that's just me;-)
>
>Sent from a remote device. Please excuse any typos...
>
>Mike Segel
>
>On Mar 17, 2013, at 12:12 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
>
>>> This then leads to another question... suppose Apache does add
>>>encryption
>> to Hadoop. While the Apache organization does have the proper paperwork
>>in
>> place, what then happens to Cloudera, Hortonworks, EMC, IBM, Intel, etc
>>?
>>
>> Well I can't put that question aside since you've brought it up now
>> twice and encryption feature candidates for Apache Hadoop and Apache
>>HBase
>> are something I have been working on. Its a valid question but since as
>>you
>> admit you don't know what you are talking about, perhaps stating
>>uninformed
>> opinions can be avoided. Only the latter is what I object to. I think
>>the
>> short answer is as an Apache contributor I'm concerned about the Apache
>> product. Downstream repackagers can take whatever action needed
>>including
>> changes, since it is open source, or feedback about it representing a
>> hardship. At this point I have heard nothing like that. I work for Intel
>> and can say we are good with it.
>>
>> On Sunday, March 17, 2013, Michael Segel wrote:
>>
>>> Its not a question of FUD, but that certain types of
>>>encryption/decryption
>>> code falls under the munitions act.
>>> See: http://www.fas.org/irp/offdocs/eo_crypt_9611_memo.htm
>>>
>>> Having said that, there is this:
>>> http://www.bis.doc.gov/encryption/encfaqs6_17_02.html
>>>
>>> In short, I don't as a habit export/import encryption technology so I
>>>am
>>> not up to speed on the current state of the laws.
>>> Which is why I have to question the current state of the US encryption
>>> laws.
>>>
>>> This then leads to another question... suppose Apache does add
>>>encryption
>>> to Hadoop. While the Apache organization does have the proper
>>>paperwork in
>>> place, what then happens to Cloudera, Hortonworks, EMC, IBM, Intel,
>>>etc ?
>>>
>>> But lets put that question aside.
>>>
>>> The point I was trying to make was that the core Sun JVM does support
>>>MD5
>>> and SHA-1 out of the box, so that anyone running Hadoop and using the
>>> 1.6_xx or the 1.7_xx versions of the JVM will have these packages.
>>>
>>> Adding hooks that use these classes are a no brainer.  However, beyond
>>> this... you tell me.
>>>
>>> -Mike
>>>
>>> On Mar 16, 2013, at 7:59 AM, Andrew Purtell <[EMAIL PROTECTED]>
>>>wrote:
>>>
>>>> The ASF avails itself of an exception to crypto export which only
>>> requires
>>>> a bit of PMC housekeeping at release time. So "is not [ok]" is FUD. I
>>>> humbly request we refrain from FUD here. See
>>>> http://www.apache.org/dev/crypto.html. To the best of our knowledge we
>>>> expect this to continue, though the ASF has not updated this policy