ok, I understand.
It means, that we have to fetch total no. of docs i.e.
Suppose we need to show 100 docs per page
Page No. NDocs No. of documents to be shown on Page
1 1000-99
2 200 100-199
3 300200
Yes.
Also note that , topdocs.totalhits will always give u total number of hits,
regardless of the number of score doc u choose to retrieve.
topdocs.scoredocs will have min(totalhits, ndocs) docs populated.
On Fri, Dec 24, 2010 at 2:48 PM, Jawahar Lal wrote:
> ok, I understand.
>
> It means,
Thanks Umesh
I want to know more about Filters, how to use that using lucene 3.0.3
Can I get links to learn how/when to use filters.
jawahar
On 24 December 2010 16:25, Umesh Prasad wrote:
> Yes.
>
> Also note that , topdocs.totalhits will always give u total number of hits,
> regardless of t
I open a IndexReader. I want to see how many docs are indexed, to get this
count I used
objReader.maxDoc() ... its returning me 0.
How can I get the total no. of docs in index?
On 24 December 2010 16:36, Jawahar Lal wrote:
> Thanks Umesh
>
> I want to know more about Filters, how to use that
>Also note that , topdocs.totalhits will always give u total number of hits,
>regardless of the number of score doc u choose to retrieve.
> topdocs.scoredocs will have min(totalhits, ndocs) docs populated.
Is it Ok use Integer.MaxValue as nDoc ?
On 24 December 2010 17:13, Jawahar Lal wrote:
> I
>From Hossman's Apache Page:
When starting a new discussion on a mailing list, please do not reply to
an existing message, instead start a fresh email. Even if you change the
subject line of your email, other mail headers still track which thread
you replied to and your question is "hidden" in th
Heh, yes, all stuff I know. My question was if an index contained any meta
data which revealed whether or not a certain indexed field had been analyzed or
not, which I think you are saying it does not.
Our searching and indexing is isolated into 2 completely seperate packages
which can be depl
Well, not to my knowledge. In fact there's no guarantee that the #same#
index
has the #same# analyzer used on the #same# field in different documents, so
I don't
see how there could be a robust implementation of what you want.
You could populate a field with a particular analyzer (or none at all),
