. Note that my index is a mix of 7.x and 8.x
segments and I am only reindexing 7.x segments by preventing them from
participating in merge via a custom MergePolicy.
Additionally as mentioned, Solr provides a handler (/admin/segments)
which does what Luke does and it shows that by the end of the
segments and I am only reindexing 7.x segments by preventing them from
participating in merge via a custom MergePolicy.
Additionally as mentioned, Solr provides a handler (/admin/segments)
which does what Luke does and it shows that by the end of the process there
are no more 7.x segments as referenced
ideal scenario a commit should have
taken care of dropping the segment files. So that tells me the refCounts
for the files are not getting set to 0. I have a fair suspicion the
reindexing process running on the same index inside the same JVM has to do
something with it.
Mike,
Thanks for the caution
have a fair suspicion the
reindexing process running on the same index inside the same JVM has to do
something with it.
Mike,
Thanks for the caution on Approach 2 ...good to at least be able to
continue on one train of thought. As mentioned in my response to Stefan,
the reindexing is going on *inside
ed to replicate same thing without the code by indexing 3 docs on an
> empty test core, and then reindexing the same docs. The older segment gets
> deleted as soon as softCommit interval hits or an explicit commit=true is
> called.
>
> Here are the two approaches that I have tried
Hi Rahul,
What you're describing sounds similar to index rearranging [1], although in
that case the reindexing is done in a new index. The last commit in the
IndexRearranger class added support for reading and reindexing deletes -
maybe
having a look at that and at the Javadoc would
a segment has been fully processed
> > and an autoCommit (as well as autoSoftCommit ) has kicked in, the segment
> > with 0 live docs gets left behind. *Upon Solr restart, the segment does
> get
> > cleared succesfully.*
> >
> > I tried to replicate same thing without the co
ve docs gets left behind. *Upon Solr restart, the segment does get
> cleared succesfully.*
>
> I tried to replicate same thing without the code by indexing 3 docs on an
> empty test core, and then reindexing the same docs. The older segment gets
> deleted as soon as softCommit inte
(as well as autoSoftCommit ) has kicked in, the segment
with 0 live docs gets left behind. *Upon Solr restart, the segment does get
cleared succesfully.*
I tried to replicate same thing without the code by indexing 3 docs on an
empty test core, and then reindexing the same docs. The older segment
eting a member
So am trying to index group_name, group_members(member ids as csv) as
parent and every text message & message_id as child.
By using parent & child, i am trying to solve 1 * m cases...
If there are 1 lakh messages under one parent, how to delete a member id
or
edit a group name witho
group_name, group_members(member ids as csv) as
>> parent and every text message & message_id as child.
>> By using parent & child, i am trying to solve 1 * m cases...
>> If there are 1 lakh messages under one parent, how to delete a member id
>> or
>> edit a
a member id or
edit a group name without reindexing of its children??
is it possible to avoid reindexing? Which lucene class is best fit for
this?
Related Article:
http://blog.mikemccandless.com/2012/01/searching-relational-content-with.html
--
Kumaran R
--
*Imixs*...extends the way peo
to delete a member id or
edit a group name without reindexing of its children??
is it possible to avoid reindexing? Which lucene class is best fit for
this?
Related Article:
http://blog.mikemccandless.com/2012/01/searching-relational-content-with.html
--
Kumaran R
thetaphi.de
>
> > -Original Message-
> > From: Rajnish kamboj [mailto:rajnishk7.i...@gmail.com ]
> > Sent: Monday, August 22, 2016 5:22 PM
> > To: java-user@lucene.apache.org
> > Subject: Re: searchAfter behavior after reindexing
> >
> > Please help m
kamboj [mailto:rajnishk7.i...@gmail.com]
> Sent: Monday, August 22, 2016 5:22 PM
> To: java-user@lucene.apache.org
> Subject: Re: searchAfter behavior after reindexing
>
> Please help me in understanding the behaviour of searchAfter().
>
> On Sunday 21 August 2016, Rajnish kamb
Please help me in understanding the behaviour of searchAfter().
On Sunday 21 August 2016, Rajnish kamboj wrote:
> Hi Team
>
> What is the searchAfter behavior if index is continuously being updated.
> Document numbers changes if indexes are updated. Also indexes are update
> on segment merge.
>
Hi Team
What is the searchAfter behavior if index is continuously being updated.
Document numbers changes if indexes are updated. Also indexes are update on
segment merge.
Now, Suppose
- I am holding a ScoreDoc before index update
- Index is updated (document number changes).
(A document
, 2012 10:09 AM
To: java-user@lucene.apache.org
Subject: Reindexing after database change
Hello,
I am working on a Data warehouse project and importing a huge mass of data
directly to the database (MysQL).
After conclude the project and roll out to production, I have discovered
that one of th
riods)
Best regards, and thanks in advance.
Rodrigo.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Reindexing-after-database-change-tp3997870.html
Sent from the Lucene - Java Users mailing list archive at Nabbl
Thank you very much!
Tajti Ákos
On 2011.09.06., at 18:42, Chris Hostetter wrote:
>
> : You can use IndexReader's setNorm method?
> :
> : It's an expert method, and accepts a new byte norm value for the doc X
> : field, ie you'll have to compute the right byte value.
>
> In particular, you sh
: You can use IndexReader's setNorm method?
:
: It's an expert method, and accepts a new byte norm value for the doc X
: field, ie you'll have to compute the right byte value.
In particular, you should take a look at the FieldNormModifier utility.
It was created for the purpose of trying out d
. The problem is that we have many documents and it takes a
> lot
> > of time to reindex them. Is there a way to change the index time boosts
> > (afaik it's stored in the fieldNorm) without actually executing the
> > reindexing?
> >
> > Thanks in advance,
>
t,
>
> I'd like to test fine-tune the boosts in the search module of our
> application. The problem is that we have many documents and it takes a lot
> of time to reindex them. Is there a way to change the index time boosts
> (afaik it's stored in the fieldNorm) without actu
cuting the
reindexing?
Thanks in advance,
Ákos Tajti
o
>> accomplish
>> >> this.
>> >> >
>> >> > There are a few strategies I've thought of, and I was wondering if
>> >> anyone
>> >> > could help me out as to which would be t
; whether two different lucene documents represent the same message.
> >> >
> >> > 1. Simply iterate over all message in the message store, convert them
> >> to
> >> > lucene documents, and call IndexWriter.update() for each one (using
> the
> &
> > lucene documents, and call IndexWriter.update() for each one (using the
>> > guid).
>> >
>> > 2. Iterate over all messages in small steps (say 1000 at a time), and
>> the
>> > for each batch delete the existing documents
dexwriter.insert() for all messages (this is essentially step 1, split
> up
> > into small parts and with the delete and insert part batched).
> >
> > 3. Iterate over all messages in small steps, and for each batch create a
> > separate index (lets say a RAM index), delet
me as 3, except merge first, and then remove the old duplicates.
>
> Any help on this issue would be much appreciated.
>
> Thanks in advance,
> Maarten
> --
> View this message in context:
> http://www.nabble.com/Best-strategy-for-reindexing-large-amount-of-data-tp25791659p257
emove the old duplicates.
Any help on this issue would be much appreciated.
Thanks in advance,
Maarten
--
View this message in context:
http://www.nabble.com/Best-strategy-for-reindexing-large-amount-of-data-tp25791659p25791659.html
Sent from the Lucene - Java Users
entally write once, so, syncing changes
over
should
simply be copying over new files and removing now-deleted files.
You
won't
be able to remove files held open by the IndexSearcher, but, once
the
IndexSearcher restarts you'd then be able to delete those files
on the
next
syn
genStartupServlet.SEARCH, new
>>> Search(getRoot(request) + "/lucene"));
>>> ctx.setAttribute(FelleskatalogenStartupServlet.SEARCHACTIVE,
>>> new Boolean(true));
>>>
>>>
>>
>> BR,
>>
>> Christopher
>>
>
her restarts you'd then be able to delete those files on
the next
sync.
Mike
Christopher Kolstad wrote:
Hi.
Currently using Lucene 2.3.2 in a tomcat webapp. We have an action
configured that performs reindexing on our staging server.
However, our
live
server can not reindex since i
gt; simply be copying over new files and removing now-deleted files. You won't
> be able to remove files held open by the IndexSearcher, but, once the
> IndexSearcher restarts you'd then be able to delete those files on the next
> sync.
>
> Mike
>
>
> Christopher
able to remove files held open by the
IndexSearcher, but, once the IndexSearcher restarts you'd then be able
to delete those files on the next sync.
Mike
Christopher Kolstad wrote:
Hi.
Currently using Lucene 2.3.2 in a tomcat webapp. We have an action
configured that performs reindex
Hi.
Currently using Lucene 2.3.2 in a tomcat webapp. We have an action
configured that performs reindexing on our staging server. However, our live
server can not reindex since it does not have the necessary dtd files to
process the xml.
To update the index on the live server we perform a
rnate list.
>> Erik
>> On Feb 7, 2006, at 7:58 AM, revati joshi wrote:
>>> Hello lucene members,
>>> i'm the silent member of
>>> this group.last week i had sent some query regarding
>>> reindexing,but i
i'm the silent member of
this group.last week i had sent some query regarding
reindexing,but i dn't received any reply from any one.Still i'm
stuck up with the same problem of reindexing.
i hve completed with the reindexing code using hibernate
Lifecycle c
the Hibernate list.
Erik
On Feb 7, 2006, at 7:58 AM, revati joshi wrote:
Hello lucene members,
i'm the silent member of this
group.last week i had sent some query regarding reindexing,but i dn't
received any reply from any one.Still i'm
-0500
>You may likely get better response by posting in the Hibernate list.
>
> Erik
>
>
>On Feb 7, 2006, at 7:58 AM, revati joshi wrote:
>
>> Hello lucene members,
>> i'm the silent member of this
>> group.la
You may likely get better response by posting in the Hibernate list.
Erik
On Feb 7, 2006, at 7:58 AM, revati joshi wrote:
Hello lucene members,
i'm the silent member of this
group.last week i had sent some query regarding reindexing,but i
Hello lucene members,
i'm the silent member of this group.last
week i had sent some query regarding reindexing,but i dn't received any reply
from any one.Still i'm stuck up with the same problem of reindexing.
i hve completed with the reinde
Hello Lucene members.
i tried to do reindexing using Lifecycle
interface of Hibernate
,but i'm stuck up with the implementation part of this interface.
I wrote the code for it but i'm now stuck up with the concept of Hibernate.
It uses me
ths.I hve finished with
indexing,searching stuff successfully.
Now i'm stuck up with one stuff i.e reindexing.I got some help from some
lucene members abt this.
For Reindexing lucene uses Lifecycles/Interceptors interface for updating
search.
But where do i get Lifecycles/Interceptors
embers abt this.
For Reindexing lucene uses Lifecycles/Interceptors interface for updating
search.
But where do i get Lifecycles/Interceptors interface?.whether i hve to
download some jar file for it?.
Quartz is a job scheduler system through which i can achieve reindexing
process.
Which
Storing numbers as text doesn't sound like
>>> something a modern application does.
>>>
>>> So, if it hasn't been asked for before, here comes: It would be
>>> nice if
>>> Lucene could search by binary fields.
>>>
>>> --
>>>
>>> Mikko
D]
Sent: Sunday, September 11, 2005 2:24 AM
To: java-user@lucene.apache.org
Subject: Re: How do I avoid reindexing?
delete document with this id and then add document with the same id.
Jian
On 9/10/05, Filip Anselm <[EMAIL PROTECTED]> wrote:
...well the title says it all
I index some
oromaa ([EMAIL PROTECTED]) - tel. +358 40 7348034
>Noromaa Solutions - see http://www.nm-sol.com/
>
>
>
>
>>-Original Message-
>>From: jian chen [mailto:[EMAIL PROTECTED]
>>Sent: Sunday, September 11, 2005 2:24 AM
>>To: java-user@lucene.apache.org
>>S
ED]
> Sent: Sunday, September 11, 2005 2:24 AM
> To: java-user@lucene.apache.org
> Subject: Re: How do I avoid reindexing?
>
>
> delete document with this id and then add document with the same id.
>
> Jian
>
> On 9/10/05, Filip Anselm <[EMAIL PROTECTED]> w
delete document with this id and then add document with the same id.
Jian
On 9/10/05, Filip Anselm <[EMAIL PROTECTED]> wrote:
>
> ...well the title says it all
>
> I index some documents - all with the same fields... One of the fields,
> "id" is unique for the indexed documents. If i try to ind
...well the title says it all
I index some documents - all with the same fields... One of the fields,
"id" is unique for the indexed documents. If i try to index a document
with an id, that is already indexed - the old document should be updated
or replaced with the new document, so that I avoid i
51 matches
Mail list logo
