thanks! it's very helpful advice for me
나의 iPhone에서 보냄
2013. 3. 5. 오후 10:14 Erick Erickson 작성:
> If you kept an "indexed_time" field, you could always just index
> to the same instance and then do a delete by query, something like
> timestamp:[* TO NOW/DAY],
> commit and go. That would delete e
Whew, cool, thanks for reporting back. I'll add the restart trick to the wiki.
- Steve
On Mar 5, 2013, at 12:46 PM, Chris Bamford wrote:
>
> Hi Steve,
>
> Turns out IntelliJ was all confused and just needed a restart.
> I can now run the tests I'm interested in :-D
>
> Thanks for all your h
Hi Steve,
Turns out IntelliJ was all confused and just needed a restart.
I can now run the tests I'm interested in :-D
Thanks for all your help.
Cheers,
- Chris
-Original Message-
From: Steve Rowe
To: java-user@lucene.apache.org
Sent: Tue, 5 Mar 2013 15:23
Subject: Re: Loading
To allow deleting the document block all at once, here is another possibility:
In addDocuments() function, add an internal field, i.e.,
"_num_children_docs_", for the number of children documents. Since the
doc ID of all parent/children documents are consecutive, we can use
this internal field tog
Hi Chris,
Those steps sound correct to me.
On Mar 5, 2013, at 9:58 AM, Chris Bamford wrote:
> Thanks for all your help here. I just tried it all again and this time I get
> "Cannot Open Project /Users/cbamford/projects/lucene_solr_4_1_0 contains no
> IntelliJ IDEA project" when I do File > O
Hi Steve,
Thanks for all your help here. I just tried it all again and this time I get
"Cannot Open Project /Users/cbamford/projects/lucene_solr_4_1_0 contains no
IntelliJ IDEA project" when I do File > Open > directory.
These are my exact steps:
cd projects
mkdir lucene_solr_4_1_0
svn co
If you kept an "indexed_time" field, you could always just index
to the same instance and then do a delete by query, something like
timestamp:[* TO NOW/DAY],
commit and go. That would delete everything indexed before midnight.
last night (NOW/DAY rounds down).
Note, most of this would be already r
On Mon, Mar 4, 2013 at 11:26 PM, Emmanuel Espina
wrote:
> 100 terms in a boolean query is not so costly. You could wrap that query in
> a ConstantScoreQuery to avoid the score calculation.
>
Thank you Immanuel. This one sounds good.
>
> Why do you have separate indexes? It would be better to bui
That sounds fine. Or just open an IndexWriter with
create/overwrite/whatever-it-is set to true.
There's rarely a clear best strategy. Do the simplest thing that could
possibly work: http://www.xprogramming.com/Practices/PracSimplest.html
--
Ian.
On Tue, Mar 5, 2013 at 5:10 AM, 장용석 wrote:
> Hi.
