Re: Query time analyzer call

Don't believe so...you'll have to store which one was used on your own when you index if you want. I think there is talk of allowing for this type of thing with the flexible indexing change that may be coming up at some point, but nothing now that I know of. - Mark John Griffin wrote: Guys a

Query time analyzer call

Guys and Gals, Is there a call that can be made at query time to determine what analyzer was used at index time so the same analyzer can be used in the query? If there is I can't find it. John G.

Strict Ordering of Boosted results?

Hi, I've looked around a bit and couldn't find an answer to this. I want to impose a strict ordering on results from a single query where there multiple boosted terms in the query. Let's say I have a field called 'word:'. If my query is word: termA^10.0 word: termB^2.0 I want ALL termA resu

Re: Fastest way to get just the "bits" of matching documents

Op Thursday 24 July 2008 23:00:33 schreef Robert Stewart: > Queries are very complex in our case, some have up to 100 or more > clauses (over several fields), including disjunctions and prohibited > clauses. Other than the earlier advice, did you try setAllowDocsOutOfOrder() ? Regards, Paul Elsc

Re: deleting documents with doc id

hello, the thing is: I got a indexwriter and indexsearcher. I do a indexsearcher.getIndexReader.delete(int id) would not that cause problems? there is not a way to delete from indexwriter, and I think i will cause a lock issue deleting from indexsearcher. best, -C.B. On Thu, Jul 24, 2008 at 2

Re: Query in IndexWriter.deleteDocuments(Term term)

Ajay Garg wrote: Pardon me. But will commit() be "code-fully" equal to calling close() followed by reinstantiating IW with create=false ??? If the above is indeed true, I can very well begin with my work. Yes, commit() can be seen as achieving exactly the same as close() and opening a ne

Re: Query in IndexWriter.deleteDocuments(Term term)

Yes. Mike Ajay Garg wrote: So commit() will be available from 2.4 onwards?? Michael McCandless-2 wrote: Ajay Garg wrote: Thanks Mike. That was quite explanatory. A couple of doubts: You're welcome! 1. The deletions apply to buffered as well as stored-in-RAM documents. Right. So,

Re: Query in IndexWriter.deleteDocuments(Term term)

Pardon me. But will commit() be "code-fully" equal to calling close() followed by reinstantiating IW with create=false ??? If the above is indeed true, I can very well begin with my work. I ask this, because I plan to work within a fortnight, and 2.4 is still someway away, and the primary reason

Re: Query in IndexWriter.deleteDocuments(Term term)

So commit() will be available from 2.4 onwards?? Michael McCandless-2 wrote: > > > Ajay Garg wrote: > >> Thanks Mike. That was quite explanatory. A couple of doubts: > > You're welcome! > >> 1. The deletions apply to buffered as well as stored-in-RAM documents. >> Right. So, if the index dir

Re: Query in IndexWriter.deleteDocuments(Term term)

Ajay Garg wrote: Thanks Mike. That was quite explanatory. A couple of doubts: You're welcome! 1. The deletions apply to buffered as well as stored-in-RAM documents. Right. So, if the index directory contains 1 document that matches a deleteDocument query, and 1 document in RAM that contains

Re: Query in IndexWriter.deleteDocuments(Term term)

Thanks Mike. That was quite explanatory. A couple of doubts : 1. The deletions apply to buffered as well as stored-in-RAM documents. Right. So, if the index directory contains 1 document that matches a deleteDocument query, and 1 document in RAM that contains the same deleteDocument query, then,

Re: Query in IndexWriter.deleteDocuments(Term term)

java_is_everything wrote: Hi all. This may seem a longish and informal mail, but do correct me if my assumptions are wrong anywhere, otherwise my actual doubt will make no sense. Say I opened an IndexWriter on an initially empty directory, using autocommit = true. Now, what I do is add and d