I my opinion.
Set up two IndexSearcher, say #1 contain the old index data for query when
#2 is updating. and
turn query to #2 where updating is completed.
2008/9/26 Asbjørn A. Fellinghaug <[EMAIL PROTECTED]>
> Ganesh:
> > Hello all,
> >
> > I need to do warmup the searcher object from my JSP page
Hi Eric,
Thanks a bunch for your pointers. I will need to find out the analyzers at
index and query time. But is it critical to have the same analyzers during
these two times?
I had tested with lucli from some of my local segment data and they appeared
working fine (i.e., their result sets are r
Hi Dan,
Thanks for your suggestion. I will definitely check that out.
-student_t
Daniel Naber-10 wrote:
>
> On Freitag, 26. September 2008, student_t wrote:
>
>> A. query1 = +(content:(Pepsi))
>
> I guess this is the string input you use for your queries, isn't it? It's
> more helpful to
I will try the other stuff and will let you know.
This is how we do the search ,
we will get the Hits in one call and we will make another call to get the
data from lucene.
My guess is when it gets the matching Hits it getting from master and when
it tries to retrieve the actual data its hittin
That certainly doesn't look right. What analyzers are you using at index
and query time?
Two things that will help track down what's really happening:
1> query.toString() is your friend.
2> get a copy of the excellent Luke tool and have it do its explain magic on
your query. Watch that the analyz
On Freitag, 26. September 2008, student_t wrote:
> A. query1 = +(content:(Pepsi))
I guess this is the string input you use for your queries, isn't it? It's
more helpful to look at the toString() output of the parsed query to see
how Lucene interpreted your input.
Regards
Daniel
--
http://ww
I am baffled by the results of the following queries. Can it be something to
do with the boosting factor? All of these queries are performed in the same
environment with the same crawled index/data.
A. query1 = +(content:(Pepsi)) resulted in 228
hits.
B. query2 = +(
Cross-posting...
Just wanted to let everyone know that there will be a number of Lucene/
Solr/Mahout/Tika related talks, training sessions, and Birds of a
Feather (BOF) gatherings at ApacheCon New Orleans this fall.
Details:
When: November 3-7
Where: Sheraton, New Orleans, USA
URL: http://u
Mike:
Actually there is more issues at first glance with OJVMDirectory integration.
Note this, I am creating an index with two simple documents:
INFO: Performing: SELECT /*+ DYNAMIC_SAMPLING(0) RULE NOCACHE(T1) */
T1.rowid,F1,extractValue(F2,'/emp/name/text()')
"name",extractValue(F2,'/emp/@id'
NOTE: This is a cross posted announcement to all Lucene sub-projects,
please confine any replies to [EMAIL PROTECTED]
-
The Travel Assistance Committee is taking in applications for those wanting
to attend ApacheCon US 2008 between the 3rd and 7th November 2008 in New
Orleans.
Th
OK it does sound like you're primarily protecting against an
untrustworthy storage system (or, maybe, Lucene bugs ;).
Probably the best option is to do this fully externally, ie, compute
digest yourself, store it away in a separate Lucene field, then test
the digest on loading the field?
Which version of Lucene is this? Looks like 2.3.x -- what's the x?
Can you run your app server with assertions enabled for
org.apache.lucene.*? It may catch something sooner.
Can you try running CheckIndex after the snapshot is produced, just to
see if there is any corruption?
Your fir
This one looks spooky!
Is it easily repeated? If you could print out which 2 terms you had
tried to delete, and then zip up the index just before deleting those
docs (after closing the writer) and send to me, I can try to
understand what's wrong with the index. It looks as if the *.tis f
I'm thinking more in terms of CRC32 checks performed on database
pages. Is there a way to incorporate this technique in a way that
does not affect performance too much in Lucene? The question is, when
is the CRC32 check is performed, and to which files is it applied if
any?
On Fri, Sep 26, 2008
OK. I really need to see those stack traces to better understand this
issue.
Also, does the issue still happen on 2.3, or 2.4 RC2?
Mike
Chaula Ganatra wrote:
Lucene 2.2.0, windows XP
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: 26 September, 2008 8
The following are steps..
1.We do indexing every 5 minutes on master and when indexing is done a
snapshot is taken
2. On slave we have a cronjob which runs snappuller every 3 minutes to check
for new snapshots and installs it on slave if it finds new one
3.Master and Slave are continuously serv
Corrupted data in what sense?
EG if you don't trust your IO system to store data properly?
Mike
Jason Rutherglen wrote:
Mike,
As part of my goal of trying to use Lucene as primary storage
mechanism (perhaps not the best idea), what do you think is the best
way to handle storing data in Luce
Hi all,
The index has Millions of entries. I need to display the index content in a
JTable with columns (terms, field, freq) and the user can choose the sorting
order (field, freq, terms), (freq, term, field), etc...
What is the best solution to manage the Index sorting
I just need some entries
Mike,
As part of my goal of trying to use Lucene as primary storage
mechanism (perhaps not the best idea), what do you think is the best
way to handle storing data in Lucene and preventing corrupted data the
way something like an SQL database handles corrupted data? Or is
there simply no good way
Confirmed that the manifest date on the 2.3-SNAPSHOT is much older
than the file date:
Implementation-Version: 2.3-SNAPSHOT 613047 - hudson - 2008-01-18 04:1
1:25
Is there an available SNAPSHOT of the 2.3 branch with this fix?
I've downloaded the 2.4 SNAPSHOT to see if this will resolve the
corru
Michael:
I just start testing 2.4rc2 running inside OJVM.
I found a similar stack trace during indexing:
IW 3 [Root Thread]: flush: segment=_3 docStoreSegment=_3
docStoreOffset=0 flushDocs=true flushDeletes=true flushDocStores=false
numDocs=2 numBufDelTerms=2
IW 3 [Root Thread]: index before
Cheers All
2008/9/24 Karl Wettin <[EMAIL PROTECTED]>
>
> 24 sep 2008 kl. 12.40 skrev Grant Ingersoll:
>
> One side note based on your example, below: Index time boosting does not
>> have much granularity (only 255 values), in other words, there is a loss of
>> precision. Thus, you
>> want to m
I think somebody provided a patch (might have been a whole new IndexReader
impl?) mny moons ago (2005?), but it never attracted enough
interest to get committed.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Michael Wechner <
Gregor,
You could loop through the results or collect them using a custom HitCollector.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Friday, September 26,
Lucene 2.2.0, windows XP
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: 26 September, 2008 8:00 PM
To: java-user@lucene.apache.org
Subject: Re: How to restore corrupted index
It's perfectly fine to have a reader open on an index, while an
IndexWriter runs
Ganesh:
> Hello all,
>
> I need to do warmup the searcher object from my JSP pages. Currently i am
> having a static object, which i am frequently checking whether index got
> updated, if so i am closing the indexer and re-opening it. These JSP pages
> are invoked by the User. When User perform
Hello you all,
is it somehow possible to get all document ids found by a search. Not only 50
or 100...
If it is possible and someone knows it, please help me :-)
Thanks and beste regards,
Gregor
TREND MICRO Deutschland GmbH, Lise-Meitner-Str. 4, D-85716 Unterschleissheim,
Germany
It's perfectly fine to have a reader open on an index, while an
IndexWriter runs optimize.
Which version of Lucene are you using? And which OS & filesystem?
Mike
Chaula Ganatra wrote:
It was the Reader on same index, which I did not close so gave
exception
in writer.optimise()
Chaula
It was the Reader on same index, which I did not close so gave exception
in writer.optimise()
Chaula
-Original Message-
From: Michael McCandless [mailto:[EMAIL PROTECTED]
Sent: 26 September, 2008 7:17 PM
To: java-user@lucene.apache.org
Subject: Re: How to restore corrupted index
Can yo
Hello all,
I need to do warmup the searcher object from my JSP pages. Currently i am
having a static object, which i am frequently checking whether index got
updated, if so i am closing the indexer and re-opening it. These JSP pages
are invoked by the User. When User performs any search operat
Can you post the full stack trace in both cases?
Mike
Chaula Ganatra wrote:
I found one case when such multiple files are remained, when we call
writer.optimise() it throws exception and multiple files remained in
index dir.
After such multiple files, when we add document in index by calling
I found one case when such multiple files are remained, when we call
writer.optimise() it throws exception and multiple files remained in
index dir.
After such multiple files, when we add document in index by calling
writer.addDocument it throws java.lang.NegativeArraySizeException
Regards,
Chaul
There is the CheckIndex tool included in the distribution for checking/
fixing bad indexes, but it can't solve everything.
The bigger question is why it is happening to begin with. Can you
describe your indexing process? How do you know the index is actually
corrupted? Are you seeing exce
You say that there are multiple files, but you don't say if the index
still works. Does it? If using the index gives you unexpected results,
can you tell us about what the failure modes are?
Best
Erick
On Fri, Sep 26, 2008 at 6:49 AM, Chaula Ganatra <[EMAIL PROTECTED]> wrote:
> We have an applic
Looks good.
On Sep 25, 2008, at 11:11 AM, Michael McCandless wrote:
Hi,
I just created the second release candidate for Lucene 2.4, here:
http://people.apache.org/~mikemccand/staging-area/lucene2.4rc2
These are the fixes since RC1:
* Issues with CheckIndex (LUCENE-1402)
* Removed new y
We have an application in which index will be updated frequently.
During development time, found that index files gets corrupted, i.e.
more than one cfs files,some other extension files e.g. frq, fnm, nrm
Remains there in index directory.
Is there any way that such issue does not occu
On Sep 26, 2008, at 6:30 AM, Michael McCandless wrote:
Ari Miller wrote:
According to https://issues.apache.org/jira/browse/LUCENE-1282?focusedCommentId=12596949
#action_12596949
(Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene), a
workaround
for the bug which causes the CorruptInd
We have an application in which index will be updated frequently.
During development time, found that index files gets corrupted, i.e.
more than one cfs files,some other extension files e.g. frq, fnm, nrm
Remains there in index directory.
Is there any way that such issue does not occur at all o
Ian Lea schrieb:
Simon
There is nothing in lucene to detect that an index has changed and
automagically reopen an IndexReader.
You can do the notification from your indexing thread, or every nnn
mins, or whatever makes sense for your application. Note that
IndexReader.reopen() does nothing if
Sorry about the spam with this thread. We started using ParallelReader
in our app and we have some bug in the app with the sorts.
I tested with simple standalone app ParallelReader and discovered that
sort works in the same way perfectly as with the other Readers.
Sorry once again.
Best Regards
Can you describe the sequence of steps that your replication process
goes through?
Also, which filesystem is the index being accessed through?
Mike
rahul_k123 wrote:
First of all, thanks to all the people who helped me in getting the
lucene
replication setup working and right now its
Ari Miller wrote:
According to https://issues.apache.org/jira/browse/LUCENE-1282?focusedCommentId=12596949
#action_12596949
(Sun hotspot compiler bug in 1.6.0_04/05 affects Lucene), a workaround
for the bug which causes the CorruptIndexException was put in to the
2.3 branch and 2.4.
However, w
Ian Lea schrieb:
Simon
There is nothing in lucene to detect that an index has changed and
automagically reopen an IndexReader.
You can do the notification from your indexing thread, or every nnn
mins, or whatever makes sense for your application. Note that
IndexReader.reopen() does nothing if
Simon
There is nothing in lucene to detect that an index has changed and
automagically reopen an IndexReader.
You can do the notification from your indexing thread, or every nnn
mins, or whatever makes sense for your application. Note that
IndexReader.reopen() does nothing if the index has not
Mark Miller schrieb:
simon litwan wrote:
hi all
i tried to reuse the IndexSearcher among all of the threads that are
doing searches as described in
(http://wiki.apache.org/lucene-java/LuceneFAQ#head-48921635adf2c968f7936dc07d51dfb40d638b82)
this works fine. but our application does contin
Hi Guys,
Does anybody know if it is possible results to be sorted using the
ParallelReader?
Best Regards,
Ivan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
46 matches
Mail list logo
