FastCharStream.java, and replaced it with a blank space. That took
care of it.
Thanks for your help!
Tareque
> 20 dec 2007 kl. 22.32 skrev [EMAIL PROTECTED]:
>
>> In fact I had previously located the grammar in StandardTokenizer.jj
>> (just wasn't sure if that was the one
ot defined in the
grammar, would be acting as splitter, since they are not contributing to
any TOKEN definition.
Please let me know what I am missing.
Thanks
Tareque
>
> 20 dec 2007 kl. 20.21 skrev [EMAIL PROTECTED]:
>
>> I would rather like to modify the lexer grammar. But exact
ng at the right place.
Thanks again!
Tareque
>
> 20 dec 2007 kl. 18.43 skrev [EMAIL PROTECTED]:
>
>> I am using StandardAnalyzer for my indexes. Now I don't want to be
>> able to
>> be search whole email addresses, and want to consider '@' as a
>&g
ng by the
whole address. And, that way, then can create a query that will return
email addresses anyway.
How do I let StandardAnalyzer consider '@' as a punctuation?
Thanks
Tareque
-
To unsubscribe, e-mail: [EMAIL
Yeah, since I will need to toggle selectively, it may not work. Also as
for writing customized query subclasses, only way I can think of is to
create several queries with all possible upper/lower case combinations of
the main query, which may really degrade the performance. Creating two
different i
>> mind that StopFilter is case-sensitive and that the stop word list is
>> all lowercase - so you will need to account for this with a custom
>> stop filter probably too.
>>
>> It is highly recommended to "analyze the analyzer" - a topic covered
>> in depth
a custom
> stop filter probably too.
>
> It is highly recommended to "analyze the analyzer" - a topic covered
> in depth in the Analysis chapter in Lucene in Action, and one of my
> java.net articles.
>
> Erik
>
It's all working now. I did write a custom analyz
> On Thu, 2005-08-18 at 17:16, [EMAIL PROTECTED] wrote:
>> Thanks again! The analyzer is working now. But seems like actually the
>> QueryParser I am using is probably converting the queries to lowercase
>> first. Is there any way to stop that? Here is the line of code where I
>> am
>> parsing:
>>
re indexing, and don't
>>> lower-case your queries (i.e. pick an Analyzer that doesn't
>>> lower-case).
>>>
>>> Otis
>>>
>>>
>>> --- [EMAIL PROTECTED] wrote:
>>>
>>>
>>>> Is there any way to do a cas
nput before indexing, and don't
>> lower-case your queries (i.e. pick an Analyzer that doesn't
>> lower-case).
>>
>> Otis
>>
>>
>> --- [EMAIL PROTECTED] wrote:
>>
>>> Is there any way to do a case-sensitive search?
>>>
&
s like it's case insensitive. In other
> words, don't lower-case your input before indexing, and don't
> lower-case your queries (i.e. pick an Analyzer that doesn't
> lower-case).
>
> Otis
>
>
> --- [EMAIL PROTECTED] wrote:
>
>> Is there any way
Is there any way to do a case-sensitive search?
Thanks
Tareque
ControlDOCS
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
document names, '_h59.cfs', '_16v6.cfs' and '_1fft.cfs'. I have made sure
that the analyzers being used in indexing and searching is the same
(StopAnalyzer for this instance). More puzzling is that, it is not acting
so for all searches. Is there an
Does lucene have adaptive re-indexing option? I have indexed several large
tables. I need to add extra documents to the tables every now and then. Do
I need to re-index the whole table all the time or there is any way to add
the new documents to the indexing with less fuss?
Thanks
Tareque
ted with "-"(hyphen) or
>> '."(period). For
>> example it didn't returned result for a text that contained
>> "processing-7-bit" and "straighforwerd.processing" but mysql did.
>> Is there
>> any settings issue or it is something
at contained
"processing-7-bit" and "straighforwerd.processing" but mysql did. Is there
any settings issue or it is something unavoidable?
Thanks
Tareque
ControlDOCS
PS: In contrast to that, I previously found lucene returning some other
results those mysql didn't. For
> On Friday 17 June 2005 22:05, [EMAIL PROTECTED] wrote:
>
>> I checked the docs missing
>> from the result set and found that those documents actually contain the
>> word 'information' but lucene is not returning them anyway. Is it a
>> known issue? Any way around?
>
> See
> http://lucene.apache.
n the
word 'information' but lucene is not returning them anyway. Is it a known
issue? Any way around?
Thanks
Tareque
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
n the
word 'information' but lucene is not returning them anyway. Is it a known
issue? Any way around?
Thanks
Tareque
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
19 matches
Mail list logo