Case Sensitivity

Hi All, I have noticed that I can not search using capital letters for some reason. If I try to do a search on "SPINAL CORD" and if I use a query like SPI* AND COR*, I get no results back. If I use lowercase (spi* AND cor*) however, I get the results back. I am using a standard analyzer. Does anyo

Case Sensitivity

What can I do to configure Lucene to make in case insensitive? Thanks, Alan -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: Case Sensitivity

> I have noticed that I can not search using capital letters for some reason. > If I try to do a search on "SPINAL CORD" and if I use a query like SPI* AND > COR*, I get no results back. If I use lowercase (spi* AND cor*) however, I > get the results back. I am using a standard analyzer. Does anyo

RE: Case Sensitivity

havan [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 2:05 PM > To: Lucene Users List > Subject: Case Sensitivity > > > Hi All, > I have noticed that I can not search using capital letters > for some reason. > If I try to do a search on "SPINAL CORD&

Re: Case Sensitivity

> Wildcard queries are case sensitive, while other queries depend on the > analyzer used for the field searched. The standard analyzer lowercases, so > lowercased terms are indexed. Thus your "SPINAL CORD" query is lowercased > and matches the indexed terms "spinal" and "cord". However, since p

RE: Case Sensitivity

uppercase. -Original Message- From: Alan Weissman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 1:26 PM To: Lucene Users List Subject: Case Sensitivity What can I do to configure Lucene to make in case insensitive? Thanks, Alan -- To unsubscribe, e-mail: <mailto:[EM

RE: Case Sensitivity

uch > as ANDs and ORs to uppercase again because lucene expects those to be > uppercase. > > -Original Message- > From: Alan Weissman [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 03, 2002 1:26 PM > To: Lucene Users List > Subject: Case Sensitivity > >

RE: Case Sensitivity

Hi, I am using StandardAnalyzer - the problem was with wildcard queries being case sensitive. Even with Standard Analyzer, you have to worry about case sensitivity in this case. Thanks for the tip on example Analyzer, I will take a peek. -Original Message- From: Joshua O'Mada

Re: Case Sensitivity

You can use the standard analyzer. This lower cases all the words (it uses the lowerCaseFilter). Note this also uses the stop word filter so your results may vary. Also when you index, be sure to use text instead of keyword as the field type since the keyword doesn't go through the filter. --Pe

case sensitivity confusion

G'day One and all, I'm have some problems getting lucene to do case-insensitive searches. I have looked through the list archives and found that using the standardAnalyser should do the trick, however I'm already using this analyser on both the indexer and searching and still no case-insensitive

Re: case sensitivity confusion

Searches are case insensitive. Showing your indexing and your searching code would help. Prefix queries are case sensitive. Otis --- Stephen Eaton <[EMAIL PROTECTED]> wrote: > G'day One and all, > > I'm have some problems getting lucene to do case-insensitive > searches. I > have looked throu

RE: case sensitivity confusion

are you running the query through the standard analyzer? -doug > -Original Message- > From: Stephen Eaton [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 04, 2003 8:14 AM > To: [EMAIL PROTECTED] > Subject: case sensitivity confusion > > > G'day On

Another Indexing Question: Case Sensitivity

>From reading the docs, my understanding is that you want to enable both case sensitive and insensitive searches that you must have two indexes, one that uses a case-insensitive analyzer, and one that uses a case sensitive one--is this correct? Thanks, E. -- . . . . . . . . . . . . . . . . . .

Re: Case Sensitivity - and more

plications. Regards, Michal - Original Message - From: "Brian Goetz" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Tuesday, January 22, 2002 12:12 AM Subject: Re: Case Sensitivity > > Wildcard queries are case sensitive, w

RE: Case Sensitivity - and more

> From: Michal Plechawski > > I think that Brian's idea is more flexible and extendable. In my > application, I need three or more kinds of analyzers: for > counting tfidf > statistics, for indexing (compute more, e.g. summaries) and > for document > classification (compute document-to-class ass

Re: Case Sensitivity - and more

> Currently it is easy to use different analyzers for different purposes, no? > I'm not sure how Brian's proposal (bi-modal analyzers: tokenize only & > tokenize+normalize) addresses your needs. Ok, maybe I misled a point a bit. But Brian's proposal as I see it was to _group_ two tokenizers that

Re: Case Sensitivity - and more

> Ok, maybe I misled a point a bit. But Brian's proposal as I see it was to > _group_ two tokenizers that differ in a single thing. I don't think that's what I was proposing... I was recognizing that sometimes the analysis process is a composite one, and I was advocating that the composition be

Re: Case Sensitivity - and more

different token streams in 1.2, that was the real problem in 1.0. Michal - Original Message - From: "Brian Goetz" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Friday, January 25, 2002 11:24 AM Subject: Re: Case Sensitivity - and more

RE: QueryParser question - case-sensitivity

Hi Otis, On both the indexing side and creation of the query parser, I'm using the StandardAnalyzer class. Seems like it would be symmetrical w/r to case sensitivity, but it's apparently not related to the problem or it's a bug...I suspect the former. I'll start lookin

Re: QueryParser question - case-sensitivity

AIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Thursday, May 09, 2002 11:28 AM Subject: RE: QueryParser question - case-sensitivity > > Hi Otis, > > On both the indexing side and creation of the query parser, I'm using the > StandardAnalyz

RE: QueryParser question - case-sensitivity

eader); } else { return standard.tokenStream(field, reader); } } } Then pass this into QueryParser. Doug > -Original Message- > From: Landon Cox > [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 09, 2002 9:52 AM > To: [EMAIL PROTECTED] > Subject: Q

RE: QueryParser question - case-sensitivity

ed, even though I'm using StandardAnalyzer on both indexing and querying, when indexed it's not going through the lower case filter of StandardAnalyzer and therefore is stored fully respecting case-sensitivity. On the flipside, the query doesn't really know the same thing (term names mapped to f

RE: QueryParser question - case-sensitivity

o pass through unscathed. I'm sure I'll add others over time which is why hash seemed convenient and fast. Anyway, this all tested out as expected and now the analyzer has the 'smarts' needed for case-sensitivity on different fieldnames. /* * DCRAnalyzer.java * * Created

RE: QueryParser question - case-sensitivity

> To: [EMAIL PROTECTED] > Subject: QueryParser question - case-sensitivity > > > > I have a QueryParser/Query question. These classes (not sure > which) is > apparently converting my term values into lowercase even though Term's > values are by default case-s

RE: Another Indexing Question: Case Sensitivity

Question: Case Sensitivity >From reading the docs, my understanding is that you want to enable both case sensitive and insensitive searches that you must have two indexes, one that uses a case-insensitive analyzer, and one that uses a case sensitive one--is this correct? Thanks,

Rollback (was: Case Sensitivity - and more)

> > ...one may commit/rollback > > all changes made > > during last session. Would it be hard? > > That is in fact what is done in 1.2. Ok, I have looked over Lucene 1.2 API and see no rollback() method. Does it work like that - if I do not close IndexWriter, it does not saves changes? How it beh