Hi,
I'm using Solr 8.0.0 I can't get autoGeneratePhraseQueries to work (also tried
with 7.7.1 and same result):
debug":{
"rawquerystring":"TROUBLESHOOT:my25word",
"querystring":"TROUBLESHOOT:my25word",
"parsedquery":"TROUBLESHOOT:my TROUBLESHOOT:25 TROUBLESHOOT:word",
"parsedque
To add some information: using "sow=true" it seems to work.But I don't
understand why with "sow=false" it wouldn't work (can't find anything in the
docs about sow interaction with autoGeneratePhraseQueries); and the implication
of setting saw=true.
I've found this:[SOLR-9185] Solr's edismax and
any update on this?
> On 5 Mar 2019, at 09:06, Nicolas Franck wrote:
>
> I noticed a change in the behaviour of the regular "dismax" parser.
> At least in version 7.4:
>
> when you add "bq", it filters the results (like "fq" does), instead of
> boosting the matches.
>
>
> e.g.
>
> defType=d
The issue is that the Standard Query Parser does pre-processing of the
query and splits it on whitespace beforehand (to deal with all the
special syntax). So, if you don't use quoted phrases then by the time
the field specific query analyzer chain kicks in, the text is already
pre-split and the ana
That's a bit "fast" to expect somebody to reproduce this from
information given. Or even in general to check the mailing list, given
that we are not paid support :-)
Could you please
1) Download the latest 8.0 distribution
2) Do one of the basic examples
3) Give the search query that shows before/
Thank you for the reply.
I'm using eDisMax, does it use the same parser as the Standard Query Parser
then?
I think this behavior should be documented somehow... it's very confusing and
to be honest I don't even remember how I got to the sow parameter... and I'm
not sure what that means for all
I agree, but I thought my thread was lost in the long list of issues.
I prepared a simple case for solr 8.0:
basic_dismax_set/config:
schema.xml and solrconfig.xml
basic_dismax_set/data:
records_pp.json
Total 6 records:
http://localhost:8983/solr/test/select?echoParams=all
5
Hi - Did you find any solution for this. Because am also facing the same
problem. After removing the field, it throws an error while doing full
index. And also the index gets failed.
Regards,
H P
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
I came across this posting with exactly the same symptoms in my solr cloud.
Here is what finally repaired my system:
I had an id with fieldType class="solr.TextField"
I changed this to class="solr.StrField"
Best regards
Christian
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472
“Throws an error” is not very informative. _What_ error?
In general reindexing should not be required. This is often a result of trying
to _use_ the field for something. Take a careful look at the error, that may
give a clue.
Best,
Erick
> On Apr 16, 2019, at 6:00 AM, Hema Preetha wrote:
>
>
The issue isn’t SoW. What’s happening here is that the query _parser_ passes
my25word through as a single token, then WordDelimiterGraphFilterFactory splits
it up on number/letter changes after SoW is out of the picture. The
admin/analysis page will show you how this works.
By fiddling with the
Hi Edwin,
To clarify what you're running into:
- on 7.6, this query works all the time
- on 7.7 this query works all the time
- on 8.0, this query works the first time you run it, but subsequent
runs return a 401 error?
Is that correct? It might be helpful for others if you could share
your sec
Hi, Dmitri
There was discussion here a while ago...
http://lucene.472066.n3.nabble.com/Soft-commit-and-new-replica-types-td4417253.html
May be it helps you somehow.
--
Vadim
> -Original Message-
> From: Dmitry Vorotilin [mailto:d.voroti...@gmail.com]
> Sent: Tuesday, April 16, 2019 9:41
Hello Everyone,
I have a Bean object which can have child documents of classes Child_type1
and Child_type2. When I try to index this document, I get an error message
"Doc cannot have more than one Field with child=true".
I looked at the mailing list but couldn't find any solution for this.
Any su
Ah oops. Did not realize the original text was missing spaces. Looked
like so many questions that did, I did not recheck the search query.
Go with Erick's explanation for this specific case. And keep my in
mind for input with spaces.
Regards,
Alex.
On Tue, 16 Apr 2019 at 17:48, Erick Erickson
If you set q.op=OR (and not as 'AND' you defined in your config), you
will see the difference between your last two queries. The second last
one will show 6 items and the last one still 5.
As is, with your custom config, booster query is added as one more
clause in the search. q.op=ALL forces it t
Ok, thanks for your investigation ;-) That was quick.
So you consider this as a bug, as it was fixed for edismax parser?
I thought the parameter q.op only applied to the terms in de main
query (parameter "q"), making ..
jakarta apache
to be interpreted as
+jakarta +apache
when q.op = AND
17 matches
Mail list logo
