Re: searching using the CJKAnalyzer

Jon Schuster wrote: I didn't need to make any changes to Entities to get Japanese searches working. Are you using the CJKAnalyzer when you perform the search, not only when building the index? Yes, I use CJKAnalyzer all around. When searching I translate character-entities in order to find

Re: Indexing Strategy for 20 million documents

--- Christoph Kiehl [EMAIL PROTECTED] wrote: Otis Gospodnetic wrote: I would try putting everything in a single index first, and split it up only if I see performance issues. Why would put everything into a single index? I found some benchmark results on the list (starting with

Re: searching using the CJKAnalyzer

CJKAnalyser not support single byte-stream, front end interface and backend indexing process need to transform source into double byte charactor-stream properly before search/index. Please tell me know the output of http://www.chedong.com/tech/HelloUnicode.java with javac -encoding=gb2312 and

Multisearcher question

Hi, Index side information: No. of indexes: Two (to explain better I call these as index_a and index_b). Fields in index_a: x and y. Fields in index_b: y and z. I have written a multisearch code like this. Searcher search_a = new IndexSearcher(LOCATION_OF_INDEX_A); Searcher search_b = new

Special field values

Hi everybody, I am thinking about extending the Lucene search with metadata in the following way Field Value --- Title (n1, n2, n3, ..., nm) | ni element of {0,1} and m amount of distinct metadata values for title

Re: Special field values

Hello Michael, This is something you'd have to code on your own. Otis --- Michael Hartmann [EMAIL PROTECTED] wrote: Hi everybody, I am thinking about extending the Lucene search with metadata in the following way Field Value

Re: Multisearcher question

Hello Sreedhar, This is the expected behaviour. The query is run against each index, and it won't have any matches in either index, because neither index has both fields. Otis --- Sreedhar, Dantam [EMAIL PROTECTED] wrote: Hi, Index side information: No. of indexes: Two (to explain

RE: Multisearcher question

Thanks Otis for you reply. If I want to solve the problem that I have defined in my previous mail, what is the suggested approach? Thanks, -Sreedhar -Original Message- From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 6:35 PM To: Lucene Users List

SearchBlox J2EE Search Component Version 2.0 released

SearchBlox is a J2EE Search Component that delivers out-of-the-box search functionality for fast and easy implementation with your websites, applications, intranets and portals. SearchBlox uses the Lucene Search API and incorporates integrated HTTP/HTTPS and File System crawlers, support for

Re: indexing numeric entities?

Yes You need to parse the entities Yourself. I implemented an HTML entity parser as a part of http://objectledge.org project. You may use it if it will fit Your needs. It is in a ledge-components project module. See http://objectledge.org/modules/ledge-components/index.html Have fun, -- Damian

RE: indexing numeric entities?

-Original Message- From: Damian Gajda [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 10:23 AM To: Lucene Users List Subject: Re: indexing numeric entities? Yes You need to parse the entities Yourself. I implemented an HTML entity parser as a part of http://objectledge.org

Re: Special field values

On Tuesday 12 October 2004 15:02, Otis Gospodnetic wrote: Hello Michael, This is something you'd have to code on your own. Otis --- Michael Hartmann [EMAIL PROTECTED] wrote: Hi everybody, I am thinking about extending the Lucene search with metadata in the following way Field

Re: Multisearcher question

I think what Sreedhar is asking for is the capability to form a join across multiple indices - and if so, I could sure use that capability myself. However, I think Lucene's logic focuses only on a single query, so I doubt if that's easily done. - Original Message - From: Otis

Re: Special field values

On Tuesday 12 October 2004 19:27, Paul Elschot wrote: IndexReader.open(indexName).termDocs(new Term(term, field)).skipTo(documentNr) returns the boolean indicating that. Well, almost. When it returns true one still needs to check the TermDocs for being at the documentNr. Paul Elschot

sorting and score ordering

If I use a Sort instance on my searcher, what will have priority? Score or Sort? Assuming I have a pages with .9, .9, and .5 scores, ... if the .5 has a higher 'sort' value, will it return higher than one of the .9 lucene score values if they are lower? --

Problem indexing

Hi, i have problem indexing in the rout C:\TXT\DOC\ But i indexing in the rout C:\TXT is OK Why is the problem ?? P.D Anybody speak spanish in the list please reply P.D. Si alguien habla español por favor respodame gracias.. -- Miguel Angel Angeles R. Asesoria en Conectividad y

Re: sorting and score ordering

As far as my testing showed, the sort will take priority, because it's basically an opt-in sort as opposed to the defaulted score sort. So you're basically displaying a sorted set over all your results as opposed to sorting the most relevant results. Hope this helps Nader Henein Chris