Bug ? unique id

Hello, we have been using Solr for a month now and we are running into a lot of trouble . one of the issues is a problem with the unique id field. can this field have analyzer, filters and tokenizers on it ?? because when we use filters or tokenizers on our unique id field, we get duplicate i

Re: Bug ? unique id

because we want to be able to search our unique id's :) and we would like to use the Latin character filter and the Lowercase filter so our searches dont have to be case sensitive and stuff. thanks for the quick response! grts,m Erik Hatcher <[EMAIL PROTECTED]> 16/03/2007 12:09 Please respo

Re: Bug ? unique id

yes, that is exactly what we are doing now ... copyfield with the filters ... we figured that much :) but we are talking about a couple of million records, so the less data we copy the better ... but can someone please answer my question :'( is it illegal to put filters on the unique id ? or is

Re: Bug ? unique id

thanks for your reply... it kind of solved our problem ! we were in fact using Tokenizers that produce multiple tokens ... so i guess there is no other way for us then to use the copyfield workaround. it would maybe be a good idea to have Lucene check the *stored* value for duplicate keys ...

Re: Bug ? unique id

ok, i'm starting to see the light :)) at this moment, we are running this for our uniqueID : field : and everything is working well ... so i dont explicitly say indexed='true' ... i guess indexed is default true ... i'll be sure do to do some testing with stored=false and indexed=false but tha

Re: How to assure a permanent index.

the documents are only deleted when you do a commit ... so you should never have an empty index (or at least not for more then a couple of seconds) note that you dont have to delete all documents you can just upload new documents with the same UniqueID and Solr will delete the old document

Re: Problems with special characters

hey, we had the same problem with the Solr Java Client ... they forgot to put UTF-8 encoding on the stream ... i posted our fix on http://issues.apache.org/jira/browse/SOLR-20 it's this post : http://issues.apache.org/jira/browse/SOLR-20#action_12478810 Frederic Hennequin [07/Mar/07 08:27 AM]

Re: Problems with special characters

we didnt use it, but i took a quick look : you need to implement the "hl=on" attribute in the getquerystring() method of the solrqueryImpl the resultdocs allready contain highlighting, that's why you found processHighlighting in the Resultparser good luck ! m "Thierry Collogne" <[EMAIL PRO

Re: How to assure a permanent index.

well, yes indeed :) but i do think it is easier to put up synchronisation for deleted documents as well clearing the whole index is kind of overkill when you do this : * delete all documents * submit all documents * commit you should also keep in mind that Solr will do an autocommit after a ce

Re: Problems with special characters

nice one ! "Thierry Collogne" <[EMAIL PROTECTED]> 22/03/2007 09:00 Please respond to solr-user@lucene.apache.org To solr-user@lucene.apache.org cc Subject Re: Problems with special characters Thanks. I made some modifications to SolrQuery.java to allow highlighting. I will post the c

Re: Problems with special characters

No, i didn't try to use it (on account of the fact that we dont use Solr to display the results) the only thing our Solr server returns are ID's ... so there is nothing to put highlights on but the code doesnt look half bad :) lets hope the Client Developers pick up on it :) "Thierry Collogn

Re: multiple indexes

> Why not create a multivalued field that stores the customer perms? > add has_access:cust1 has_access:cust2, etc to the document at index > time, and turn this into a filter query at query time? that is what we are doing at the moment, and i must say, it works very and does not slow the server d

Re: Reposting unABLE to match

what exactly is the problem ? seems like you end up with the same term text in both query and index analyzer ... you should have found a match... Shridhar Venkatraman <[EMAIL PROTECTED]> 27/03/2007 14:08 Please respond to solr-user@lucene.apache.org To solr-user@lucene.apache.org cc Subj

Re: Reposting unABLE to match

the only thing i can think of is the fact that in the index analysis the term-type is "word" and in the query analysis the term-type is "alphanumeric" you should be getting a match if that doesnt matter ... you get exactly the same term texts ... Shridhar Venkatraman <[EMAIL PROTECTED]> 27

Item Search Database

hi, i have a performance question... we need to implement a feature called 'Item Search Database', which basically means we have to limit the documents a user can search ... example : Item1 is in database1 item2 is in database2 item3 is in database1 and database2 and the client can only see the

Re: C# API for Solr

Well, i think there will be a lot of people who will be very happy with this C# client. grts,m "Jeff Rodenburg" <[EMAIL PROTECTED]> 31/03/2007 18:00 Please respond to solr-user@lucene.apache.org To solr-user@lucene.apache.org cc Subject C# API for Solr We built our first search sys

Re: Solr logo poll

i would use the first one, much more professional "Yonik Seeley" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 06/04/2007 19:51 Please respond to solr-user@lucene.apache.org To solr-user@lucene.apache.org cc Subject Solr logo poll Quick poll... Solr 2.1 release planning is underway,

Leading wildcards

hi, we have been trying to get the leading wildcards to work. we have been looking around the Solr website, the Lucene website, wiki's and the mailing lists etc ... but we found a lot of contradictory information. so we have a few question : - is the latest version of lucene capable of handlin

Re: AW: Leading wildcards

thanks, this worked like a charm !! we built a custom "QueryParser" and we integrated the *foo** in it, so basically we can now search leading, trailing and both ... only crappy thing is the max Boolean clauses, but i'm going to look into that after the weekend for the next release of Solr : d

Re: AW: Leading wildcards

hey, i'm sorry for the confusion : our "custom query parser" is not a Lucene query parser it is something we built for the client-side of Solr ... it basically transforms some search arguments into an Solr query URL example : method query( searchID, searchQuery, category, ) returns h

Re: AW: Leading wildcards

hey, we've stumbled on something weird while using wildcards we enabled leading wildcards in solr (see previous message from Christian Burkamp) when we do a search on a nonexisting field, we get a SolrException: undefined field (this was for query "nonfield:test") but when we use wildcards

Collection Distirbution in windows

i know this is a stupid question, but are there any collection distribution scripts for windows available ? thanks !

Re: Collection Distirbution in windows

damn, there goes the platform independance ... is there anybody with a lillte more experience when it comes to collection distribution on Windows ? tnx in advance ! "Bill Au" <[EMAIL PROTECTED]> 02/05/2007 15:09 Please respond to solr-user@lucene.apache.org To solr-user@lucene.apache.org