If your json value is & the proper xml value is &
What is the value you are setting on the stored field? is is & or &?
On Mon, Apr 30, 2012 at 12:57 PM, William Bell wrote:
> One idea was to wrap the field with CDATA. Or base64 encode it.
>
>
>
> On Fri, Apr 27, 2012 at 7:50 PM, Bill Bell
One idea was to wrap the field with CDATA. Or base64 encode it.
On Fri, Apr 27, 2012 at 7:50 PM, Bill Bell wrote:
> We are indexing a simple XML field from SQL Server into Solr as a stored
> field. We have noticed that the & is outputed as & when using
> wt=XML. When using wt=JSON we get
We are indexing a simple XML field from SQL Server into Solr as a stored field.
We have noticed that the & is outputed as & when using wt=XML. When
using wt=JSON we get the normal &. If there a way to indicate that we don't
want to encode the field since it is already XML when using wt=XML ?
Hi Yonik.
I am so embarrassed! The schema files where totally different. Actually the
slave was the master back in the day and had a WordDelimiterFilterFactory
configured. I wouldn't be to surprised if words are splitted on "&" in that
one. As I said embarrassingly simple... But good! You can't im
On Sun, Sep 7, 2008 at 7:50 AM, Marcus Herou <[EMAIL PROTECTED]> wrote:
> The strange thing is that the query works on both my local machine(s) and on
> the master.
- Check and ensure that the schema is the same on all the systems.
- Check to see that Solr is reading the index you think it is by d
Hi, turning to the mailing list since I cannot find any similar case by
googling.
We have troubles searching when the "&" sign is included in the search
query, for example; description:"h&m", "m&m" etc.
The server setup looks like this.
We apache-solr-1.3.0-RC2.war on all machines (same issues w
