Veit
     My query parser looks like this
     string DefaultSearchField = "TITLE";
     QueryParser qp(DefaultSearchField, &analyzer);

after this i am performing search and I have been observed that, if
query having more than 1000 results it is throwing below error.
"Invalid field name being used in the query string".
Query i have given is a*, b* etc...for all these queries its throwing
same error.
Could you plese help me out on this.

With best regards
Raghuram


------------------------------------------------------------------------------------
Hi,

do you do something else before executing the search? I ask, because I
can't find any line in the CLucene source code where an exception with
such a message is thrown. Neither in 0.9.21 nor in the lucene_2_3_2
branch.

Kind regards

Veit

2010/4/8 n raghuramireddy <[email protected]>:
> Hi Veit
> Thanks for your response. Search is throwing the error and the default field
> I have given is the field which is tokenized. I am indexing the Title
> of the document and this
> title is given as default searchable field.
>
> Message: 2
> Date: Wed, 7 Apr 2010 21:11:20 +0200
> From: Veit Jahns <[email protected]>
> Subject: Re: [CLucene-dev] Clucene search - An invalid field name was
>       used    in a query string
> To: [email protected]
> Message-ID:
>       <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi Raghuram,
>
> who throws this exception? The query parser parsing the query or the
> searcher executing the query? And what does your query parser use as
> default field?
>
> Kind regards,
>
> Veit
>
> 2010/4/7 n raghuramireddy <[email protected]>:
>> Hi
>> I am indexing arround 10 million records. If I search with keyword a*,
>> Clucene is throwing following error
>> "An invalid field name was used in a query string". Whether this error
>> because of number of hits are more.
>> Could any one please sugges me.
>>
>> Regards
>> Raghuram
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> CLucene-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/clucene-developers
>>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> CLucene-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/clucene-developers
>

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
CLucene-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clucene-developers

Reply via email to