I have been looking at using ParallelReader as its documentation indicates, to
allow certain fields to be updated while most of the fields will not be updated.
However, this does not seem possible. Let's say I have two indexes, A and B,
which are used in a ParallelReader. If I upd
Hi David,
With current Lucene versions, the usage of ParallelReader is very
complicated to keep in sync. The problem is how merges occur. For
ParallelReader to work, all internal document ids (the integers) must be
parallel. As the new MergePolicies now work on size of documents and also
may work
Hello everybody,
I was wondering, if someone could point me to what I need to be aware of, using
a ParallelReader.
My intention is to modify Nutch (http://nutch.apache.org/) in a way, that in
the Lucene-index Nutch uses, only documents for changed websites are updated.
However, due to the
I am trying to find a work around for updating fields and in turn the
documents in the original index.
I am using parallel reader and providing it two index, the second index
being the first to be seen by parallel reader. The second index has same
number of documents as first index[in this case,
>> Any case where it would break?
If a query uses multiple fields it would break. That is, usually all the
fields need to be in doc in index 2 - not just the modified one.
On Fri, Oct 15, 2010 at 2:35 PM, Erick Erickson wrote:
> This seems like far too much work if I'm reading things right. You
This seems like far too much work if I'm reading things right. You can't
update
a field, but you #can# update a document which actually re-index that
document
under the covers (you have to have a way to uniquely identify the doc).
Then, when
you reopen your index reader, you'll only see the new val
Hey Erick, Sure.
*
*
*What I am trying to achieve:*
A) Update a field in Index A
B) When searching for that old field, it should be a miss.
*How I achieved it*
*Index 1 *
Doc 1 - Field1, Value 1
Doc 2 - Field1, Value 1
*Index 2*
Doc 1 - Field1, Modified_Value 1
Doc 2 - EMPTY
Add index 2 before
No. And you don't even want to try... Document IDs are NOT invariant.
Particularly
when you delete a document and optimize an index, all the documents that
come
after the deleted one get new doc IDs. Trying to keep these two indexes in
synch
will be a nightmare.
Perhaps you could explain what you'
I have two index, A and B. Can two documents doc1[in index A] and doc2[in
index B] have a common field? doc1 and doc2 have same document Id's.
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
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]
Hello,
When using a parallel reader with two indexes lets say, when we call a
document with id,
is it the combined fields of a document from the two indexes that return?
The documentation was not clear on that one, except the document(int n,
FieldSelector fs) method.
Best,
-C.B.
Hi,
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Saturday, June 16, 2007 3:10:08 AM
Subject: Re: How to Use ParallelReader
: My question is: If I just want to update the small fields in one index
: and do not want to upda
IndexWriter settings, and optimize both indexes. you can rebuild either
of them again and again and again if you want -- as long as you keep doing
it in the same order.
ParallelReader is a pretty special caes class that not a lot of people
seem to use (or if they are they don't talk about it
Hi,
There is one class named org.apache.lucene.index.ParallelReader, as its javadoc
stated:
An IndexReader which reads multiple, parallel indexes. Each index added must
have the same number of documents, but typically each contains different
fields. Each document contains the union of the field
Hi,
On Tue, 2007-03-06 at 15:34 -0500, Andy Liu wrote:
> Is there a working solution out there that would let me use ParallelReader
> to search over a large, immutable index and a smaller, auxillary index that
> is updated frequently? Currently, from my understanding, the ParallelReade
From my understanding, MultiSearcher is used to combine two indexes that
have the same fields but different documents. ParallelReader is used to
combine two indexes that have same documents but different fields. I'm
trying to do the latter. Is my understanding correct? For example, wha
To: java-user@lucene.apache.org
Subject: Using ParallelReader over large immutable index and small updatable
index
Is there a working solution out there that would let me use ParallelReader
to search over a large, immutable index and a smaller, auxillary index that
is updated frequently? Currently
Is there a working solution out there that would let me use ParallelReader
to search over a large, immutable index and a smaller, auxillary index that
is updated frequently? Currently, from my understanding, the ParallelReader
fails when one of the indexes is updated because the document ID&#
Hi Erik,
i made some several test as follows:
Create new indicies with only on document with one Value ("ID"=100).
Open it with parallelreader.
Delete Document with parallelreader.delete(new Term("ID","100"))
Close Reader with parallelreader.close.
After this
f both your deletion code
and test case ...
Best
Erick
On 8/27/06, neils <[EMAIL PROTECTED]> wrote:
Hi,
I'm using a parallelreader to hold on two indicies. There have to be
updated
everyday.
When I'm performing a deletion e.g. parallelreader.delete(New
Term("ID",&qu
Hi,
I'm using a parallelreader to hold on two indicies. There have to be updated
everyday.
When I'm performing a deletion e.g. parallelreader.delete(New
Term("ID","100)), the documents are still there.
When i do the some with normal indexreader e.g. indexreader.delet
;m happy that you give me the right direction for my problem
:-)
Thanks.
--
View this message in context:
http://www.nabble.com/Sorting-with-Parallelreader-fails-tf1999747.html#a5493952
Sent from the Lucene - Java Users forum at Nabble.com.
---
Steven Rowe wrote:
> And, por supuesto, posting what appears to be Visual Basic code
> (presumably to be used with Lucene.Net) to an explicitly *Java* list
> (dude, the name of the list is "java-user") may be prove fruitful than
> you might hope
That should read: ... may prove *less* fruitful
neils wrote:
> Hi,
>
> i have 3 indexfiles which i access over a parallelreader.
>
> When i make a search, everything works fine, butwhen i want to make a
> search and sorting by a special
> column i get an error.
You need to say exactly what the error is, right?
Hi,
i have 3 indexfiles which i access over a parallelreader.
When i make a search, everything works fine, butwhen i want to make a
search and sorting by a special
column i get an error. Here is my code:
Schnipp
Dim field As SortField = New SortField("Streetname")
Dim
moving this to java-user.
Hello,
Is anyone using ParallelReader the way Chuck is describing his scenario? I
remember looking at the ParallelReader a few months ago and asking myself the
same question: how can I update only one of the parallel indices and still keep
the documents in two
.
Searching could then be done via ParallelReader. If I understand that
class correctly I have to ensure that the documents in the two indexes
stay in the same order. If I'm not mistaken, updating a document must
thus be done by first deleting the to-update document from both indexes,
and then addi
you should delete from both indexes, and likewise with add.
Erik
On Oct 10, 2005, at 4:14 PM, John Smith wrote:
Sorry to bug people on this again and again.
I might be missing something or confused totally, But what is the
use case for a ParallelReader if the use case is not addressing the
Sorry to bug people on this again and again.
I might be missing something or confused totally, But what is the use case for
a ParallelReader if the use case is not addressing the situation where we have
a index changing frequently( meaning deletes and reindex) and index not
changing , but has
no
way of addressing the situation.
JZ
Eyal <[EMAIL PROTECTED]> wrote:Run a search on "Lucene ParallelReader" in
google - You'll find something
Doug Cutting wrote that I believe is what you're looking for.
Eyal
> -Original Message-
> From: Joh
On Montag 10 Oktober 2005 20:24, John Smith wrote:
> My understanding is ParallelReader works for situations where you have a
> static index and a dynamic index.
That's no correct. Quoting the documentation:
It is up to you to make sure all indexes
are created and modified the sa
Hi
I am using the ParallelReader feature from Lucene 1.9.
I have 2 indexes, one that doesnât change and the other that changes often. I
delete and re-index documents from the dynamic index often.
I am indexing the documents with a keyword field âidâ and giving it a
unique number
Thank you.
I will try that
JS
Erik Hatcher <[EMAIL PROTECTED]> wrote:
On Sep 12, 2005, at 2:04 PM, John Smith wrote:
> I have Lucene 1.4.3 codebase and I got Parallel Reader from the
> trunk along with a few changes that need to go on top of it to make
> it compile.
I highly recommend you si
On Sep 12, 2005, at 2:04 PM, John Smith wrote:
I have Lucene 1.4.3 codebase and I got Parallel Reader from the
trunk along with a few changes that need to go on top of it to make
it compile.
I highly recommend you simply compile the trunk and use it instead of
trying to patch these classe
)
First of all, is it a good idea to get all the code from the trunk, instead of
just pieces to make ParallelReader work or is there a bug which I can just fix
and move on with the existing code ?
Question 2:
==
My index 2 is expected to be dynamic, meaning will be
Dear Doug,
thanks for your message.
On Fri, Jun 03, 2005 at 09:37:01AM -0700, Doug Cutting wrote:
> Sebastian Marius Kirsch wrote:
> >I took up your suggestion to use a ParallelReader for adding more
> >fields to existing documents. I now have two indexes with the same
> &g
Sebastian Marius Kirsch wrote:
I took up your suggestion to use a ParallelReader for adding more
fields to existing documents. I now have two indexes with the same
number of documents, but different fields.
Does search work using the ParalleReader?
One field is duplicated
(the id field
Hi Doug,
I took up your suggestion to use a ParallelReader for adding more
fields to existing documents. I now have two indexes with the same
number of documents, but different fields. One field is duplicated
(the id field.)
I wrote a small class to merge those two indexes into one index; it is
On 5/31/05, Doug Cutting <[EMAIL PROTECTED]> wrote:
> > I have wondered about this as well. Are there any *sure fire* ways of
> > creating (and updating) two indices so that doc numbers in one index
> > deliberately correspond to doc numbers in the other index?
>
> If you add the documents in the
ther index?
>
> If you add the documents in the same order to both indexes and perform
> the same deletions on both indexes then they'll have the same numbers.
The Javadoc says that ParallelReader is useful with collections that
have large fields which change rarely and small fie
Matt Quail wrote:
I have a similar problem, for which ParallelReader looks like a good
solution -- except for the problem of creating a set of indices with
matching document numbers.
I have wondered about this as well. Are there any *sure fire* ways of
creating (and updating) two indices so
I have a similar problem, for which ParallelReader looks like a good
solution -- except for the problem of creating a set of indices with
matching document numbers.
I have wondered about this as well. Are there any *sure fire* ways of
creating (and updating) two indices so that doc numbers in
43 matches
Mail list logo
