Ok. If i distribure the indexes, whether sorting would be faster?
In Lucene user group mailing list, most emails suggests to use single
indicies. Searching across the indexes may not be slower?
Lucene uses FieldCache for sorting on non-tokenized field and tries to
maintain fields from all you
I still suggest you to setup and test a standalone IndexSearcher though you
believe it should work.
If it work, and tomcat get the right parameter, sorry, i don't know what is
the problem.
2008/9/18 anandsarwade <[EMAIL PROTECTED]>
>
> This Luke tool seems to be pretty cool. I have installed and
please anyone help me and tell me how to unsubscribe from this mailing list
> From: [EMAIL PROTECTED]> Subject: Re: Search all Related Documents> Date:
> Thu, 18 Sep 2008 17:35:14 -0500> To: java-user@lucene.apache.org> > You can
> search the lucene and solr mailing lists for "denormalize" > but
Thanks Mike for the insight. I did check the stdout log and found it
was complaining of not having enough disk space. I thought we need
only x2 of the index size. Our index size is 10G (max) and we had 45G
left on that parition - should it still complain of the space?
Some comments/questions on o
You can search the lucene and solr mailing lists for "denormalize"
but the general response is to try one of:
1. de-normalize the data while indexing
- advantage: one query
- disadvantage: data repetition
2. use 2 indices
- advantage: no need for repetition; this is necessa
Hello,
I wanted to wait until now to follow-up to this, in order to give people who
were on vacation in August a chance to see this.
We've received several emails with case-study offers -- thank you!
We are still welcoming contribution ideas, of course.
Otis
--
Sematext -- http://sematext.com/
After 5 month work we are happy to announce the first developer
preview release of katta.
This release contains all functionality to serve a large, sharded
lucene index on many servers.
Katta is standing on the shoulders of the giants lucene, hadoop and
zookeeper.
Main features:
+ Plays wel
Hi,
I just created the first release candidate for 2.4, here:
http://people.apache.org/~mikemccand/staging-area/lucene2.4rc1
Please download the release candidate, kick the tires and report back
on any issues you encounter.
The plan is to make only serious bug fixes or build/doc fixes, to
2
Michael McCandless-2 wrote:
>
>
> It's only with the trunk version of Lucene that QueryParser calls
> getWildcardQuery on parsing a wildcard string from the user's query.
>
I see..
So, how can I plug the WildcardFilter in, to prevent TooManyClauses? Are
there other ways, than using the tru
IndexReader.isCurrent() goes and opens that most recent segments_N
file from the index and then compares that version to its own. So if
your replication brought over a new segments_N then isCurrent would
return false.
Mike
rahul_k123 wrote:
I am doing replication and i am running scr
It's only with the trunk version of Lucene that QueryParser calls
getWildcardQuery on parsing a wildcard string from the user's query.
Mike
Konstantyn Smirnov wrote:
Beard, Brian wrote:
1) Extend QueryParser to override the getWildcardQuery method.
Kinda late :), but I still have a
Beard, Brian wrote:
>
> 1) Extend QueryParser to override the getWildcardQuery method.
>
Kinda late :), but I still have another question:
Who calls that getWildcardQuery() method?
I subclassed the QueryParser, but that method does never get invoked, even
if the query contains *.
Shall I
Hi All,
Scenario: I have 100 documents in an index and if these documents fall into
10 mutualy exclusive set; And within that set one of them is the main
document.
Now if I am to search on the index and group the result on 10 mutually
exclusive sets. And if I have to display the result with field
Lucene tries to carry forward the root cause exception from the merge,
into that IOException that optimize throws. But it doesn't always
succeed in doing so; I'll open a Jira issue and try to figure out why
this is the case.
All the exception "means" is that the optimize didn't finish -- you
sti
uuu, take anything Otis says as *much* more informed than anything I say
on this topic .
Erick
On Thu, Sep 18, 2008 at 2:32 AM, Tobias Larsson Hult <
[EMAIL PROTECTED]> wrote:
> Thanks for the quick responses!
>
> Good point about the warmup issues Erick, that's something we will
> consider.
one moment:
the top doc collector is based on some sort of queue, I assume. What
kind of queue is that? does it sort based on score, or whichever doc
comes first.
best.
On Wed, Sep 17, 2008 at 9:43 PM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
>
> : Well, it turns out the theoretical maximum f
This Luke tool seems to be pretty cool. I have installed and its very easy to
find out the indexes and what is being stored. thanks for this info.
I have tried in tomcat and things works fine without issues. Default
operator is OR in my case. i havent tried with setting up stanalone
indexsearcher
And, you can use Tool luke to see what is in the index indeed.
what is in the Query which put into IndexSearcher.search(), what is the
defaultOperatoer of QueryParser.
Can you get hits by setup a simple IndexSearcher, no through tomcat?
2008/9/18 anandsarwade <[EMAIL PROTECTED]>
>
> Hi,
>
> I d
18 matches
Mail list logo
