Has anyone had any experience/problems with using C/C++ in Lucene queries?
When I do a query using that as a term I get back a bunch of records that do
not contain the term. The resulting query ends up being like: +(+c/c++) when
parsed by the QueryParser. I've also tried just adding Term objects
*This message was transferred with a trial version of CommuniGate(tm) Pro*
I'm actually using a WhitespaceAnalyzer and WhitespaceTokenizer that I
wrote. It parses terms on, of course, whitespace. Is there a way to get a
list of the tokens that are generated after indexing?
-Original
I think there is no way to do that since a double quote is a special
character for query parser.
There was some discussion about introducing an escape character to
allow things like this, but the discussion has not materialized yet.
Otis
--- Tony Biag [EMAIL PROTECTED] wrote:
Is there a way
I haven't heard of any such limit. There is a 'limit' of 10,000
characters on a field length, but that is a limit only because that
number is hard coded in the source.
However, shouldn't this be very simple for you to test?
Index something over and over and see if you ever hit the wall :)
Otis
