RE: Odd Edge Case for SpellCheck

This is a great help, thank you! Brett Moyer -Original Message- From: Erick Erickson Sent: Monday, November 25, 2019 4:12 PM To: solr-user@lucene.apache.org Subject: Re: Odd Edge Case for SpellCheck If you’re using direct spell checking, it looks for the _indexed_ term. So this means

Solr Case Insensitive Search while preserving cases in Index and allowing Boolean AND/OR searches

Hi, I am exploring possibility to do case insensitive filter/facet queries in solr. I would also need to preserve the cases in the index. This means that the normal LowerCaseFilterFactory approach would not work as facet values will not preserve cases and will show in all lowercase. One method w

Re: Odd Edge Case for SpellCheck

If you’re using direct spell checking, it looks for the _indexed_ term. So this means you get stemmed corrections if you’re stemming etc. Usually you should use a copyField to a field with minimal analysis and use that field for spellchecking. Another way to thing about it is that if you use th

RE: Odd Edge Case for SpellCheck

Yes we are stemming, ahh so we shouldn't stem our words to be spelled? Brett Moyer -Original Message- From: Jörn Franke Sent: Friday, November 22, 2019 8:34 AM To: solr-user@lucene.apache.org Subject: Re: Odd Edge Case for SpellCheck Stemming involved ? > Am 22.11.2019 um 14:23 schrie

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

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: Solr 4 to Solr7 migration DIH behavior change

It's worth to increase log level for DIH categories in SolrAmin. It's quite useful usually. On Mon, Nov 25, 2019 at 10:19 PM Shashank Bellary wrote: > That didn't make any difference. However, I upgraded to 8.0.15 version of > mysql-jdbc driver which fixed the problem of result set closing but t

Re: Updates blocked in Tlog solr cloud?

Update for another observation: after the follower replica become unresponsive, I notice there are multiple commits happen on the leader within two minutes, and then seeing the following OOM error on leader: o.a.s.s.HttpSolrCall null:java.lang.RuntimeException: java.lang.OutOfMemoryError: Direct b

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

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: Fetch parent and child document in solr 8.2

some more information, in solr 8.2 it does not fetch child document only when schema has _nest_path_ field defined without nest_path it can fetch child documents. On Thu, 21 Nov 2019 at 16:01, Jigar Gajjar wrote: > Hello, > > > > I am trying to fetch parent and child document together in one Sol

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

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.

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

Re: Solr 4 to Solr7 migration DIH behavior change

That didn't make any difference. However, I upgraded to 8.0.15 version of mysql-jdbc driver which fixed the problem of result set closing but then data import got really slow and getting stuck without any logs in solr logs. I'll debug more from DB perspective, in the meantime any pointers would

FlattenGraphFilter Eliminates Tokens - Can't match "Can't"

Hi all, I have been trying to solve an issue where FlattenGraphFilter (FGF) removes tokens produced by WordDelimiterGraphFilter (WDGF) - consequently searches that contain the contraction "can't" do not match. This is on Solr version 7.7.1. The field in question is defined as follows: And t

Re: How to tell which core was used based on Json or XML response from Solr

I was referring to David Hastings' suggestion of shielding solr from direct access which is something I strongly agree with. If you're not going with a PHP-based server-side application as to not expose your solr directly to the javascript application (and thus to possible manipulation by an en

Re: How to tell which core was used based on Json or XML response from Solr

On Mon, Nov 25, 2019 at 10:43 AM David Hastings < hastings.recurs...@gmail.com> wrote: > you missed the part about adding &core= to the query: > &echoParams=all&core=mega > > returns for me: > > "responseHeader":{ > "status":0, > "QTime":0, > "params":{ > "q":"*:*", > "cor

Re: How to tell which core was used based on Json or XML response from Solr

On 11/25/2019 8:30 AM, rhys J wrote: On Mon, Nov 25, 2019 at 2:10 AM Erik Hatcher wrote: add &core=&echoParams=all and the parameter will be in the response header. Erik Thanks. I just tried this, and all I got was this response: http://localhost:8983/solr/dbtr/select?q=debtor_id%3A%2

Re: How to tell which core was used based on Json or XML response from Solr

you missed the part about adding &core= to the query: &echoParams=all&core=mega returns for me: "responseHeader":{ "status":0, "QTime":0, "params":{ "q":"*:*", "core":"mega", "df":"text", "q.op":"AND", "rows":"10", "echoParams":"all"}}, also we ar

Re: How to tell which core was used based on Json or XML response from Solr

On Mon, Nov 25, 2019 at 1:10 AM Paras Lehana wrote: > Hey rhys, > > What David suggested is what we do for querying Solr. You can figure out > our frontend implementation of Auto-Suggest by seeing the AJAX requests > fired when you type in the search box on www.indiamart.com. > That is pretty c

Re: How to tell which core was used based on Json or XML response from Solr

> if you are taking the PHP route for the mentioned server part then I would > suggest > using a client library, not plain curl. There is solarium, for instance: > > https://solarium.readthedocs.io/en/stable/ > https://github.com/solariumphp/solarium > > It can use curl under the hood but you can

Re: How to tell which core was used based on Json or XML response from Solr

On Mon, Nov 25, 2019 at 2:10 AM Erik Hatcher wrote: > add &core=&echoParams=all and the parameter will be in the response > header. > >Erik > Thanks. I just tried this, and all I got was this response: http://localhost:8983/solr/dbtr/select?q=debtor_id%3A%20393291&echoParams=all

Re: How to tell which core was used based on Json or XML response from Solr

Hi rhys, if you are taking the PHP route for the mentioned server part then I would suggest using a client library, not plain curl. There is solarium, for instance: https://solarium.readthedocs.io/en/stable/ https://github.com/solariumphp/solarium It can use curl under the hood but you can pr

Production Issue: cannot connect to solr server suddenly

I don't get this error always. At certain times, I get this error with my Solr suddenly. However, If I check my Solr url, it will be working but. When I want to update via code, it will not work. Please help me out with this. ERROR: *Failed to connect to server at 'http://127.0.0.1:8983/solr/my_co