Compiled Term Hightlighter

Hello guys. I'm not a java developer, so I'm getting stuck on compiling the Term Highlighter of source files acquired from the Lucene Sandbox. I got some errors, well, I guess I'm not using the correct command line (it was javac c:\dir\*.java, something like that). Can someone post me the compil

Re: Compiled Term Hightlighter

Cool! Thanks. About the highlighter+fuzzy, after you wrote that, I checked my code. It was wrong: Wrong one: objQuery.rewrite(objIndexReader) Then I fixed to: objQuery = objQuery.rewrite(objIndexReader) []s Cesar Daniel Naber-10 wrote: > > On Samstag, 9. Februar 2008, Cesar Ro

Re: Indexing accented characters, then searching by any form

Ops! Found a situation here Karl: If the content is stored without accents, everything is OK. But, as my content is stored with accents, and I noticed the ISOFilter just removes the accent from the search terms, it is not returning to my Hits collection. Any idea how to fix it? -- View this mes

RE: Delete problems O.O

Cool man. The Hits.id(int) worked fine. Thanks for the detailed info. And hopefully your answer is going to usefull for future Google searches. ;) Cesar Steven A Rowe wrote: > > Hi Cesar, > > On 02/11/2008 at 2:19 PM, Cesar Ronchese wrote: >> I'm running problems

Delete problems O.O

Hey All. I'm running problems with document deletion. I tried to use DeleteDocuments() and DeleteDocument() methods, both are with problems, according explained below: 1) DeleteDocuments(term) This simply doesn't delete anything from the Index. //see the code sample: //"theFieldName" was pre

Re: Indexing accented characters, then searching by any form

Hey, Erick. You inferred right. I analized your code and it looks like a common Indexing and Searching code. Are you sure you pasted the correct code? :P Anyways, is the concept about doubling storing data, one content with accents and other without? If yes, I did it earlier, but once I search i

Re: Indexing accented characters, then searching by any form

> One more thing, > are you aware of that you are supposed to apply that filter on the > query too? I don't know how to set that filter to Query object. I've searched to see if it is possible, but I can't find references. If it is possible, do you have a quick example? I'm searching this way:

Re: Indexing accented characters, then searching by any form

Hey Karl. Thanks for the response. I have some doubts more: 1) About the ISOLatin1AccentFilter class: > What is the problem you have with this? Are they not unique enough? I need to store the words in the way it was written. So, if the text to be indexed contains the word "usuário", my user expe

Re: Indexing accented characters, then searching by any form

Woot, Karl. It worked like a charm! It even worked with the Highlighter. THANKS! karl wettin-3 wrote: > > > 11 feb 2008 kl. 18.16 skrev Cesar Ronchese: > >> I don't know how to set that filter to Query object. > > It is a TokenStream you filter, no

Re: Indexing accented characters, then searching by any form

xpressions, and the results is satisfactory. Thanks all for the brainstorming ^^ Cesar Erick Erickson wrote: > > See below... > > > On Feb 11, 2008 12:17 PM, Cesar Ronchese <[EMAIL PROTECTED]> wrote: > >> >> Hey, Erick. You inferred right. >> >>

Indexing accented characters, then searching by any form

Hello, guys. I've searching the google to make the lucene performs accent-insensitive searches. All I could find is about the ISOLatin1AccentFilter class, which as far I could understand, it just removes the accented chars so I can store it in its unaccented form. What I would like to know is,

Lucene multiple field search performance

I was doing normal queries happily, seeing the results statistics come in about 0.02 seconds. But then, I added a extra field to seach togheter with the normal query, then the statistic pulled up to 0.35 seconds. That was a lot. example: normal query: some test (it returns quick) extra field que

Re: Lucene multiple field search performance

already. > > -M > > On Feb 12, 2008 7:42 PM, Cesar Ronchese <[EMAIL PROTECTED]> wrote: > >> >> I was doing normal queries happily, seeing the results statistics come in >> about 0.02 seconds. >> >> But then, I added a extra field to seach tog

Retrieving parsed query string terms

Hey, its me again :P I've been looking a way to retrieve all parsed terms from a given query string, but no success till now. For example, I need convert: word01 "word02 word03" AND word04 theField:(xyz) mod_date:[20020101 TO 20030101] (abc OR xyp) into: word01 "word02 word03"