I have same questions puzzled me.
Could anyone explain which class been called in the searching steps ?
Thanks!
> Date: Thu, 26 Jun 2008 00:24:08 -0700> From: [EMAIL PROTECTED]> To:
> java-user@lucene.apache.org> Subject: How Lucene Search> > > hi, > > I am
> fairly new to Lucene and is curre
On Jun 30, 2008, at 7:00 PM, Erik Hatcher wrote:
On Jun 30, 2008, at 8:55 PM, Paul J. Lucas wrote:
If I have a SortField with a type of STRING, is there any way to
sort in a case-insensitive manner?
Only if you unify the case (lower case everything) on the client
side that you send to Solr
Thanks for reply,but I am not know Solr well.
Does Solr base on lucene core or hack lucene core
to achieve the (categories amount)'s function ?
Can I achieve the similar function using
lucene core ?
> From: [EMAIL PROTECTED]> To: java-user@lucene.apache.org> Subject: Re: how to
> statistics cat
On Jun 30, 2008, at 8:55 PM, Paul J. Lucas wrote:
If I have a SortField with a type of STRING, is there any way to
sort in a case-insensitive manner?
Only if you unify the case (lower case everything) on the client side
that you send to Solr, but in general no.
You can use a text field ty
If I have a SortField with a type of STRING, is there any way to sort
in a case-insensitive manner?
- Paul
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sorry for the radio silence. I changed my code around so that a
single IndexReader and IndexSearcher are shared. Since doing that,
I've not seen the problem. That being the case, I didn't pursue the
issue.
I still think there's a bug because the code I had previously, IMHO,
should have
Interesting discussion... glad I'm not the only one with this challenge.
Michael McCandless-2 wrote:
>
> EG, if you use Highlighter on a
> multi-valued field indexed with stored field & term vectors and say
> the first field ended with a stop word that was filtered out, then
> your offset
I don't see why close must be final; I think we could/should relax that?
But: I think your situation is perfect for incRef(). That method
declares that someone is still using the IndexReader (until the
corresponding decRef() is called).
Mike
John Wang wrote:
Hi Mike:
Thanks for the
Is it possible to do nested proximity searches with lucene?
i.e. can I say I want a to be within 1 word of b and then that group to be
within 4 words of c? The syntax ""a b"~1" c"~4 doesn't seem to work (since
it treats the first two quotes as a pair and the later 2 as another pair).
Hi Mike:
Thanks for the reply!
The reason my pattern wouldn't work is because my doClose impl does
nothing to avoid the actual closing and then later my "index updater" will
do the actual closing. The problem is although my doClose is called, the
reference is decremented to 0, and ensureOp
This is spooky: that exception means you have some sort of index
corruption. The TermScorer thinks it found a doc ID 37389, which is
out of bounds.
Reopening IndexReader while IndexWriter is writing should be
completely fine.
Is this easily reproduced? If so, if you could narrow it do
Actually, you've been a big help. Your 'data_type' field suggestion I think
will work for our app and obviates the need for the Field copy functionality
that I was originally asking about. Just having one problem with it still, but
I think it has to do with my limited knowledge of how analyzer
What version of Lucene are you using? Can you share the snippet of
code that does this? Are you keeping the QueryWrapperFilter around
from search to search?
On Jun 27, 2008, at 5:24 PM, Jordon Saardchit wrote:
Hello All,
Sort of new to lucene but have a general question in regards to
pe
Hrm, sorry then I'm not sure how much more help I'm going to be able to
be on this on. I have to index things that have a DAG Structure
(Treelike), but in order to get that functionality into my search I
simply flatten out my dag, so any single term knows all of its children,
but loses the str
Matthew,
It has to do with the fact that we're trying to represent these Property
entitities hierarchically. We are displaying them in a tree structure, similar
to the way Windows Explorer displays directories and files your file system.
E.g. all the states would be at the root level. If you
Hi,
I see some strange behavoiur of lucene. The following scenario.
While adding documents to my index (every doc is pretty small, doc-
count is about 12000) I have implemented a custom behaviour of
flushing and committing documents to the index. Before adding
documents to the index I check
Sorry, didn't get this until this morning.
Yes, both fields should be indexed and searchable, though the data_type
one should likely be untokenized.
Data should be indexed and tokenized with whatever appropriate Analyzer
works for your data.
As for what your indexing, may I ask why you are
Hi Devashish,
The difference between these modes of operation would be that firsly,
RAMDirectory and FSDirectory on one hand are implementations of the
directory class of lucene.
http://lucene.apache.org/java/2_2_0/api/org/apache/lucene/store/Directory.html
Lucene's directory is just a flat list o
Hi
Sorry about doubble messaging, it was from mistake
I am working on an application that searches documents with lucene.
The documents are taken from a database and the basic field is in HTML.
The index and searching works fine with Greek characters. I am using
the lucene to take the ID a
You should be using the same analyzer when you query as when you built
the index. I suspect that in this case you need to make an analyzer
that recognises both English and Greek.
I hope this helps,
Eleanor Joslin
[EMAIL PROTECTED] wrote:
Hello
i am having the following code to high
It's true there is now reference counting logic to determine when it's
really time to close an IndexReader, but, at that point doClose() is
still called so your custom logic should still be running, right? It
seems like your pattern ought to still be working?
If not, another alternative
That's right -- the check was added in 2.2.
Mike
java_is_everything wrote:
Hi Mike.
Our project currently uses 2.0.0. So I suppose the later versions
might not
be allowing this, right?
Ajay Garg
Michael McCandless-2 wrote:
Which version of Lucene are you using? Recent versions do
What is the difference between these three modes of operating with
lucene... And are there any other modes/ways of operation also, using
which we can more effectively run applications with lucene.
I have heard there is also something called 'Memory' in contrib
directory of lucene source package wh
23 matches
Mail list logo