Re: Using an & in an indexed field and then querying for it.

2019-11-25 Thread David Hastings
This again is why its recommended to have something inbetween your js and solr, also gets have limitations so if eventually you start getting more complications you may hit it: https://stackoverflow.com/questions/2659952/maximum-length-of-http-get-request On Mon, Nov 25, 2019 at 2:40 PM rhys J w

Re: Using an & in an indexed field and then querying for it.

2019-11-25 Thread rhys J
On Mon, Nov 25, 2019 at 2:36 PM David Hastings wrote: > its breaking on the & because its in the url and you are most likely > sending a get request to solr. you should send it as post or as %26 > > The package I am using doesn't have a postJSON function available, so I'm using their getJSON fun

Re: Using an & in an indexed field and then querying for it.

2019-11-25 Thread David Hastings
its breaking on the & because its in the url and you are most likely sending a get request to solr. you should send it as post or as %26 On Mon, Nov 25, 2019 at 2:32 PM rhys J wrote: > I have some fields that have text like so: > > Reliable Van & Storage. > > They indexed fine when I used curl

Using an & in an indexed field and then querying for it.

2019-11-25 Thread rhys J
I have some fields that have text like so: Reliable Van & Storage. They indexed fine when I used curl and csv files to read them into the core. Now when I try to query for them, I get errors. If I try escaping it like so \&, I get the following error: on_data({ "responseHeader":{ "status