That should be fixable. In a past life, I generated a perfect hash to fold case for Unicode in a locale-neutral manner and it was very fast. If I remember right, there are only about 2500 Unicode characters that can be case folded at all. So the generated, collision-free hash function was very small and fast and the lookup table was small.
I used Bob Jenkins' tool suite for a C application. http://burtleburtle.net/bob/hash/perfect.html But there are a number of other open source tools available. Bob Jenkins currently recommends this one by Botelho and Ziviani: http://homepages.dcc.ufmg.br/~nivio/papers/cikm07.pdf -----Original Message----- From: Nir Barel [mailto:ni...@checkpoint.com] Sent: Thursday, July 09, 2015 4:35 AM To: solr-user@lucene.apache.org Subject: RE: Do I really need copyField when my app can do the copy? Hi, I wants to add a question regarding copyField and LowerCaseFilterFactory We notice that LowerCaseFilterFactory takes huge part of the CPU ( via profiling ) for the text filed Can we avoid it or improve that implementation? ( keeping the insensitive case search ) Best Regards, Nir Barel -----Original Message----- From: Petersen, Robert [mailto:robert.peter...@rakuten.com] Sent: Thursday, July 09, 2015 1:59 AM To: solr-user@lucene.apache.org Subject: RE: Do I really need copyField when my app can do the copy? Perhaps some people like maybe those using DIH to feed their index might not have that luxury and copyfield is the better way for them. If you have an application you can do it either way. I have done both ways in different situations. Robi -----Original Message----- From: Steven White [mailto:swhite4...@gmail.com] Sent: Wednesday, July 08, 2015 3:38 PM To: solr-user@lucene.apache.org Subject: Do I really need copyField when my app can do the copy? Hi Everyone, What good is the use of copyField in Solr's schema.xml if my application can do it into the designated field? Having my application do so helps me simplify the schema.xml maintains task thus my motivation. Thanks Steve &j)ly˫y " ************************************************************************* This e-mail may contain confidential or privileged information. If you are not the intended recipient, please notify the sender immediately and then delete it. TIAA-CREF *************************************************************************
