Have you investigated using Terracotta / Compass? We need real-time updates
across the index using multiple web servers. I recently got this up and
running and we're going to be doing some performance testing. It's very
easy, essentially you just replace your FSDirectoryProvider with a
Terracott
5 seconds seems short to me also but this is what our client wants and so I
need to get as close to this number as possible :) It's a system that
records live video 24x7 and up to date information is extremely important.
I have the hibernate search in action book as well. I didn't see other
alter
We are using hibernate search that is an abstraction on top of lucene. Has
anyone used this in a clustered environment? There is built-in JMS ( master
/ slave ) support for this but the assumption is that the slaves get updates
every 30 minutes or more from the master. Our application requires t
more I'm unclear what the behavior for
> a document without the reporter field is..
>
> But I do know that you can't do what your example does
>
> FWIW
> Erick
>
>
> On Mon, Dec 8, 2008 at 10:24 AM, no spam <[EMAIL PROTECTED]> wrote:
>
> >
ently. Furthermore I'm unclear what the behavior for
> a document without the reporter field is..
>
> But I do know that you can't do what your example does
>
> FWIW
> Erick
>
>
> On Mon, Dec 8, 2008 at 10:24 AM, no spam <[EMAIL PROTECTED]> wrote:
>
> last I knew) enabled by default
>
> <<>>
>
> from
>
>
>
> http://wiki.apache.org/jakarta-lucene/LuceneFAQ#head-4d62118417eaef0dcb87f4370583f809848ea695
>
> Best
> Erick
>
> On Mon, Dec 8, 2008 at 10:24 AM, no spam <[EMAIL PROTECTED]>
The reason our users want to do this is because they want to search for
instances where certain negative conditions are true. My client is the news
industry and this is metadata for things like reporter, type, etc.
Sometimes you want -reporter:mark for example and this is the only criteria
to sea
We are converting a User Interface query to lucene on the back end. It has
recently come up that users want to do some negative only queries like NOT
"jakarta apache". What is an efficient way to do this? We do know what field
they are specifying, ie -field1:jakarta
On Mon, Jun 23, 2008 at 2:53 AM
We are converting a User Interface query to lucene on the back end. It has
recently come up that users want to do some negative only queries like NOT
"jakarta apache". What is an efficient way to do this? We do know what
field they are specifying, ie -field1:jakarta
On Mon, Jun 23, 2008 at 2:
terms in the index. If you haven't
indexed the term, you won't find it, so your Field.Index.NO is really
hurting you here.
Best
Erick
On 2/24/07, no spam <[EMAIL PROTECTED]> wrote:
>
> I didn't fully understand your last post and why I wanted to do
> IndexReader.te
I just dug my book out. Chapter six shows a custom sort that implements a
SortComparatorSource combined with a TermQuery. I like the way that works
but I guess what I really need to do is a RangeQuery as well.
I have another large index that has 1.2 million docs. I use a query along
with a hit
s almost
exactly
what you want, see section 6.1
Erick
On 2/27/07, no spam <[EMAIL PROTECTED]> wrote:
>
> I have a very small index of 500 docs with an index size of < 100k on
disk
> so far. I want to whip through the docs and get only the ones within a
> lat/lon within radius.
I have a very small index of 500 docs with an index size of < 100k on disk
so far. I want to whip through the docs and get only the ones within a
lat/lon within radius. I realize this isn't how lucene wants to do things
(normally query search first) but how can I do this in an efficient manner?
Yes correct, I'll be using the new updateDocument() api call!
Erick thanks for correcting my poor use of termdocs :)
On 2/27/07, Doron Cohen <[EMAIL PROTECTED]> wrote:
"Erick Erickson" <[EMAIL PROTECTED]> wrote on 25/02/2007 07:05:21:
> Yes, I'm pretty sure you have to index the field (UN_TOK
I didn't fully understand your last post and why I wanted to do
IndexReader.terms() then IndexReader.termDocs(). Won't something like this
work?
for (Business biz : updates)
{
Term t = new Term("id", biz.getId()+"");
TermDocs tDocs = reader.termDocs(t);
I have an index where I'm storing the primary key of my database record as
an unindexed field. Nightly I want to update my search index with any
database changes / additions.
I don't really see an efficient way to update these records besides doing
something like this which I'm worried with thr
e documents. Because these comparisons are done outside
of
Lucene as integer comparisons, it is pretty fast. With 13000 results, the
seach time with distance sort is about 200 msec (compared to 30 ms for a
simple non-radius, date-sorted keyword search).
Peter
On 1/27/07, no spam <[EMAIL PRO
Isn't this extremely ineffecient to do the euclidean distance twice?
Perhaps not a huge deal if a small search result set. I at times have
13,000 results that match my search terms of an index with 1.2 million docs.
Can't you do some simple radian math first to ensure it's way out of bounds,
the
Truly I am new to Lucene. That's the missing part ... I'm looking at the
stored values and not the indexed terms.
Mark
On 9/17/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
1) maybe you didn't really use StandardAnalyzer when the index was built?
2) keep in mind there is a differnece between
That question was badly worded. I was trying to ask that when I write an
index using the StandardAnalyzer, the docs are transformed using that
analyzer then written to the index post transformation. So stop words or
things like apostrophes would be removed.
"Scott's Lawn and Garden Care" bec
"The guys"
have
been generous with many posters in looking at actual code..
Best
Erick.
P.S. Please post whatever the resolution is, I'm pretty curious what you
find.
On 9/17/06, no spam <[EMAIL PROTECTED]> wrote:
>
> I am new to Lucene so I'll admit I am confu
I am new to Lucene so I'll admit I am confused by a few things. I'm using
an index which was built with the StandardAnalyzer. I have verified this by
using an IndexReader to read the docs back out ... Antiques is not Antiq in
the index. So according to this note in the Lucene docs I would assu
When I use "french AND antiques" I get documents like this :
score: 1.0, boost: 1.0, cont: French Antiques
score: 0.23080501, boost: 1.0, cont: FRENCH SEPTIC
score: 0.23080501, boost: 1.0, cont: French & French Septic
score: 0.20400475, boost: 1.0,id: 25460, cont: French & Associates
As in the f
Why does my query "french AND antiques" work the way I expect using this
code:
stemParser = new QueryParser("contents", stemmingAnalyzer);
Query query = stemParser.parse(searchTerms);
Hits docHits = searcher.search(query);
Debug from query shows: contents:french contents:antiqu ... I would h
24 matches
Mail list logo
