I suspect that your index doesn't contain what you think it does, or
your query isn't doing what you think. Here's what I'd do:
1> use Luke or perhaps TermsComponent to see what is
actually in your designations field. Watch out for
deleted documents (this is where an optimize might
be of use first, to remove deleted documents' data).
2> Use &debugQuery=on to see how your query is actually
parsed. Perhaps your designations: query isn't doing quite
what you think.
3> I'm a little suspicious that your evidence is that when you
query on a different query you don't get the results you think
you are. Is it possible that you're using edismax or similar when
you get all 3,000 results?
Anyway, posting the two queries with the results of &debugQuery=on
might allow some further analysis.
Best
Erick
On Fri, Nov 11, 2011 at 11:40 AM, dennis leary <d...@learys.com> wrote:
> In our implementation we are using dataimport handler to bring records in
> via database. In our schema we have a field called "designation" and it is
> of type "string" and is multivalued. We run a simple query
> q=designations:"My Designation" and it returns documents that match but
> depending on the documents loaded via the db it will miss/skip some of the
> documents. If we load 3000 records with a certain where clause all the
> results are returned but if we load a subset of that 3000 with different
> criteria for some reason SOLR does not return the same number of documents
> even though the documents that are not showing up in the results are in the
> index which we verified by performing diff search (eg. q=lname:"Smith").
> Has anyone faced a similar issue in their experiences of SOLR and can
> anyone point me in a direction of where to look as to what could be the
> issue?
>
