> -Original Message-
> From: Chris Hostetter [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 6 July 2006 9:52 AM
> To: solr-user@lucene.apache.org
> Subject: Re: base64 support & containers
>
>
> : Does Solr support/or will in the future base64 encoded XML documents
so
> : that binary blo
: With the standard setup, the "OR" operator is used between two or more
: search values.
correct, that's because it is the default behavior of the Lucene
QueryParser (which is used by the StandardRequestHandler)
: How can I setup Solar, that my users don't have to key in AND all the
: time?
Ch
Hi Solr users,
I would like to configure my Solr search to make it Google like.
With the standard setup, the "OR" operator is used between two or more
search values.
Example:
A search for berlin robin
returns in debug mode:
berlin robin
pubtext:berlin pubtext:robin
(and will give me all docu
: Does Solr support/or will in the future base64 encoded XML documents so
: that binary blobs can be added to the index?
I'm not sure if I'm understanding your question completely ... if you have
binary data that you want to shove into a stored field, you should
certinaly be able to base64 encode
On 7/5/06, Eric Jain <[EMAIL PROTECTED]> wrote:
Yonik Seeley wrote:
> Something like this I suppose:
Yes, just what I meant :-)
Thanks a lot!
The fix is committed (and new tests confirm it works ;-)
-Yonik
Yonik Seeley wrote:
Something like this I suppose:
Yes, just what I meant :-)
Thanks a lot!
On 7/5/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
So fixing the first token at the end of next() and also at the other
exit point (line 276) is probably the easiest fix.
Something like this I suppose:
Index: src/java/org/apache/solr/analysis/WordDelimiterFilter.java
==
On 7/5/06, Eric Jain <[EMAIL PROTECTED]> wrote:
Yonik Seeley wrote:
> Your'e right, it does look possible that position info can be lost.
> The fix probably isn't as simple as copying the position increment in
> newTok()... the original increment should only be copied for the first
> token genera
