Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of simon.willnauer@googlemail.com
 designates 209.85.216.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:content-type:content-transfer-encoding;
        b=pmLB8VyLt5YszSw8IHAisW9q6+z7yDRAxdSixoQrkhOY+A2GR8vJ3nXgqPnS33sZgE
         lLnpNj+GQEWOHXklZsZErfa+UcuSjcI6gPBTMN+clybqyoi33Br5mbSnid8YPcgTkDyG
         LU1vxpq4IxgrEC2T2L761CpddS5oc5RiQWWrs=
MIME-Version: 1.0
Reply-To: simon.willnauer@gmail.com
In-Reply-To: <AANLkTintJwiTayXUNbEAZ2BX9CKEpt6ahi38DZbBsL=_@mail.gmail.com>
References: <AANLkTimxyHcd1z-ZsqGot4a=okN3OAfNYHFnz94or50x@mail.gmail.com>
	<AANLkTim1wf1FLoY7SM55bhGW7Ge2KCirZXLaAuc2BRLu@mail.gmail.com>
	<AANLkTi=WKAGj2X9JZQ_qY2mYawHQjHTBQUCuFbQ3A6=b@mail.gmail.com>
	<AANLkTim6+Q1nTJDZJqJxh-9D5V488eZ9ZCG-+h=mDCye@mail.gmail.com>
	<AANLkTim9MZWxBdN9G__a4Vurx_maOXnEeffX8QEwFS_Y@mail.gmail.com>
	<0a0fe7d8-4e88-420e-870a-2eac021ba939@email.android.com>
	<AANLkTikEoao80ExsvMNW3nUEoeY4tEZ09ehXjNJ0jMJw@mail.gmail.com>
	<AANLkTintJwiTayXUNbEAZ2BX9CKEpt6ahi38DZbBsL=_@mail.gmail.com>
Date: Sat, 25 Dec 2010 17:30:24 +0100
Message-ID: <AANLkTin_RUBxkSq-uz2Wyg_Rv1s2X4VASDjJyK=e1zw2@mail.gmail.com>
Subject: Re: LuceneTestCase.threadCleanup incorrectly reports left running
 threads
From: Simon Willnauer <simon.willnauer@googlemail.com>
To: dev@lucene.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Dec 25, 2010 at 3:05 PM, Earwin Burrfoot <earwin@gmail.com> wrote:
> I think we can take some public algos like lookup3 / murmurhash2/3,
> and stuff them into Lucene utils.
>
> Java implementations (very simple and fast ones) exist for both of these.
>
> I.e. lookup3 done by Yonik (http://people.apache.org/~yonik/code/hash/),
> murmurhash2 - by Andrzej Bialecki (
> http://www.getopt.org/murmur/MurmurHash.java ) used in Hadoop?
> non-compatible with original?,
> a version by Derek Young (
> http://dmy999.com/article/50/murmurhash-2-java-port ),
> a version by Ted Dunning for Mahout,
> a random version off Google by Viliam Holub (
> http://d3s.mff.cuni.cz/~holub/sw/javamurmurhash/ )
>
> lookup3 defines versions returning 32/64bit hashes, murmurhash2 -
> 32/64bit, murmurhash3 - 32/64/128bit

Earwin, I like your suggestion - that seems to be very straight
forward and will work on every JVM as far as I can see. No need to
rely on anything else or include a whole crypto lib.

simon
>
> They are just generally useful for many text-processing apps.
>
> On Sat, Dec 25, 2010 at 16:20, Robert Muir <rcmuir@gmail.com> wrote:
>> On Sat, Dec 25, 2010 at 4:04 AM, Uwe Schindler <uwe@thetaphi.de> wrote:
>>> Md5 is guaranteed to be there (like utf8 as charset). This is documente=
d in crypto Api, which algorithms are available for digest.
>>>
>>
>> where is this documented? its not in the javadocs.
>>
>> anyway, we shouldn't be doing this:
>> * this algorithm might not exist on J2ME etc (still java), you need to
>> install an extra crypto add-on.
>> * we shouldnt start up an expensive PKI infrastructure on mac os X,
>> including spawning a new thread, just to hash a string. thats absurd.
>> * we pay all these costs ... for md5! its not even a good hash!
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
>
>
> --
> Kirill Zakharenko/=D0=9A=D0=B8=D1=80=D0=B8=D0=BB=D0=BB =D0=97=D0=B0=D1=85=
=D0=B0=D1=80=D0=B5=D0=BD=D0=BA=D0=BE (earwin@gmail.com)
> Phone: +7 (495) 683-567-4
> ICQ: 104465785
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org