[jira] [Updated] (SOLR-10010) NGramTokenizer with SynonymFilterFacory doesn't work properly when using Managed-Schema
[
https://issues.apache.org/jira/browse/SOLR-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Issei Nishigata updated SOLR-10010:
---
Attachment: SOLR-10010.patch
ManagedIndexSchema#postReadInform seems to be called both when reading the
managed-schema file at Solr startup and when using Schema API.
this patch calls this postReadInform() only when it read the managed-schema
file, and modified details only super.postReadInform().
I created managedPostReadInform and make solr use this new method when solr
calls Schema API.
I do not know if this fixing is smart or not.
Also, the test code I created in fixing it might not be appropriate.
But I think that it has sufficient details to reproduce this problem.
> NGramTokenizer with SynonymFilterFacory doesn't work properly when using
> Managed-Schema
> ---
>
> Key: SOLR-10010
> URL: https://issues.apache.org/jira/browse/SOLR-10010
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
>Reporter: Issei Nishigata
> Attachments: SOLR-10010.patch
>
>
> NGramTokenizer with SynonymFilterFacory doesn't work properly when using
> Managed-Schema
> When using Managed-Schema, it doesn't work properly with the following
> settings.
> {code:title=managed-schema}
>
> positionIncrementGap="100"
>autoGeneratePhraseQueries="false">
>
>maxGramSize="2"/>
>synonyms="synonyms.txt"
>
> tokenizerFactory="solr.NGramTokenizerFactory"
>
> tokenizerFactory.minGramSize="2" tokenizerFactory.maxGramSize="2"
> ignoreCase="true"
> expand="true"/>
>
>
> {code}
> {code:title=synonyms.txt}
> ab,ba
> {code}
> {code:title=expected}
> querystring => "bigram:ab"
> parsedquery => "bigram:ab bigram:ba"
> {code}
> {code:title=actual}
> querystring => "bigram:ab"
> parsedquery => "bigram:ab"
> {code}
> When using ClassicIndexSchemaFactory, works peroperly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10010) NGramTokenizer with SynonymFilterFacory doesn't work properly when using Managed-Schema
[
https://issues.apache.org/jira/browse/SOLR-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831261#comment-15831261
]
Issei Nishigata commented on SOLR-10010:
I guess this is causing
org.apache.lucene.analysis.synonym.SynonymFilterFactory#loadSynonyms doesn't
set tokenizerFactory.minGramSize="2", tokenizerFactory.maxGramSize="2" when
calling loader.inform() ( => constructor of
"org.apache.solr.schema.IndexSchema")
(tokArgs is empty)
> NGramTokenizer with SynonymFilterFacory doesn't work properly when using
> Managed-Schema
> ---
>
> Key: SOLR-10010
> URL: https://issues.apache.org/jira/browse/SOLR-10010
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
>Reporter: Issei Nishigata
>
> NGramTokenizer with SynonymFilterFacory doesn't work properly when using
> Managed-Schema
> When using Managed-Schema, it doesn't work properly with the following
> settings.
> {code:title=managed-schema}
>
> positionIncrementGap="100"
>autoGeneratePhraseQueries="false">
>
>maxGramSize="2"/>
>synonyms="synonyms.txt"
>
> tokenizerFactory="solr.NGramTokenizerFactory"
>
> tokenizerFactory.minGramSize="2" tokenizerFactory.maxGramSize="2"
> ignoreCase="true"
> expand="true"/>
>
>
> {code}
> {code:title=synonyms.txt}
> ab,ba
> {code}
> {code:title=expected}
> querystring => "bigram:ab"
> parsedquery => "bigram:ab bigram:ba"
> {code}
> {code:title=actual}
> querystring => "bigram:ab"
> parsedquery => "bigram:ab"
> {code}
> When using ClassicIndexSchemaFactory, works peroperly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10010) NGramTokenizer with SynonymFilterFacory doesn't work properly when using Managed-Schema
[
https://issues.apache.org/jira/browse/SOLR-10010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Issei Nishigata updated SOLR-10010:
---
Description:
NGramTokenizer with SynonymFilterFacory doesn't work properly when using
Managed-Schema
When using Managed-Schema, it doesn't work properly with the following settings.
{code:title=managed-schema}
{code}
{code:title=synonyms.txt}
ab,ba
{code}
{code:title=expected}
querystring => "bigram:ab"
parsedquery => "bigram:ab bigram:ba"
{code}
{code:title=actual}
querystring => "bigram:ab"
parsedquery => "bigram:ab"
{code}
When using ClassicIndexSchemaFactory, works peroperly.
was:
NGramTokenizer with SynonymFilterFacory doesn't work properly when using
Managed-Schema
When using Managed-Schema, it doesn't work properly with the following settings.
{code:title=managed-schema}
{code}
{code:title=synonyms.txt}
ab,ba
{code}
{code:title=expected}
querystring => "bigram:ab"
parsedquery => "bigram:ab bigram:ba"
{code}
{code:title=actual}
querystring => "bigram:ab"
parsedquery => "bigram:ab"
{code}
When using ClassicIndexSchemaFactory, works peroperly.
I guess this is causing
org.apache.lucene.analysis.synonym.SynonymFilterFactory#loadSynonyms doesn't
set tokenizerFactory.minGramSize="2", tokenizerFactory.maxGramSize="2" when
calling loader.inform() ( => constructor of
"org.apache.solr.schema.IndexSchema")
(tokArgs is empty)
> NGramTokenizer with SynonymFilterFacory doesn't work properly when using
> Managed-Schema
> ---
>
> Key: SOLR-10010
> URL: https://issues.apache.org/jira/browse/SOLR-10010
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
>Reporter: Issei Nishigata
>
> NGramTokenizer with SynonymFilterFacory doesn't work properly when using
> Managed-Schema
> When using Managed-Schema, it doesn't work properly with the following
> settings.
> {code:title=managed-schema}
>
> positionIncrementGap="100"
>autoGeneratePhraseQueries="false">
>
>maxGramSize="2"/>
>synonyms="synonyms.txt"
>
> tokenizerFactory="solr.NGramTokenizerFactory"
>
> tokenizerFactory.minGramSize="2" tokenizerFactory.maxGramSize="2"
> ignoreCase="true"
> expand="true"/>
>
>
> {code}
> {code:title=synonyms.txt}
> ab,ba
> {code}
> {code:title=expected}
> querystring => "bigram:ab"
> parsedquery => "bigram:ab bigram:ba"
> {code}
> {code:title=actual}
> querystring => "bigram:ab"
> parsedquery => "bigram:ab"
> {code}
> When using ClassicIndexSchemaFactory, works peroperly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-10010) NGramTokenizer with SynonymFilterFacory doesn't work properly when using Managed-Schema
Issei Nishigata created SOLR-10010:
--
Summary: NGramTokenizer with SynonymFilterFacory doesn't work
properly when using Managed-Schema
Key: SOLR-10010
URL: https://issues.apache.org/jira/browse/SOLR-10010
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: Schema and Analysis
Reporter: Issei Nishigata
NGramTokenizer with SynonymFilterFacory doesn't work properly when using
Managed-Schema
When using Managed-Schema, it doesn't work properly with the following settings.
{code:title=managed-schema}
{code}
{code:title=synonyms.txt}
ab,ba
{code}
{code:title=expected}
querystring => "bigram:ab"
parsedquery => "bigram:ab bigram:ba"
{code}
{code:title=actual}
querystring => "bigram:ab"
parsedquery => "bigram:ab"
{code}
When using ClassicIndexSchemaFactory, works peroperly.
I guess this is causing
org.apache.lucene.analysis.synonym.SynonymFilterFactory#loadSynonyms doesn't
set tokenizerFactory.minGramSize="2", tokenizerFactory.maxGramSize="2" when
calling loader.inform() ( => constructor of
"org.apache.solr.schema.IndexSchema")
(tokArgs is empty)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310477#comment-15310477
]
Issei Nishigata commented on SOLR-9174:
---
I think I misunderstood the behavior of {{mm}}.
In this particular case, it seems that I can also get expected result by the
{{q.op=OR}}.
As a matter of fact, it does have no meaning that I mixed up {{q.op}} and
{{mm}} together.
I have confirmed that {{q.op}} is interpreted {{mm}} in the source code.
I understood that {{q.op}} overrides {{mm}}.
Is my understanding mentioned above right?
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> [schema]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308192#comment-15308192
]
Issei Nishigata commented on SOLR-9174:
---
Thank you for your suggestion.
Is q.op=OR completely replaceable with q.op=AND parameter?
Is the result with q.op=OR perfectly identical with the result with q.op=AND
parameter
as long as mm parameter is used, even under different condition such that there
are multiple search words?
If so, I will use q.op=OR tentatively.
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> [schema]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Issei Nishigata updated SOLR-9174:
--
Description:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
[schema]
{code:xml}
{code}
[request]
{quote}
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
[Solr 5.4]
{code:xml}
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
{code}
[Solr 6.0.1]
{code:xml}
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
{code}
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
was:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
[schema]
{code:xml}
{code}
[request]
{quote}
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
{code:xml}
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
{code}
[Solr 6.0.1]
{code:xml}
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
{code}
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> [schema]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Issei Nishigata updated SOLR-9174:
--
Description:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
[schema]
{code:xml}
{code}
[request]
{quote}
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
{code:xml}
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
{code}
[Solr 6.0.1]
{code:xml}
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
{code}
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
was:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
{code:xml}
{code}
{quote}
[request]
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
[Solr 6.0.1]
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> [schema]
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> [request]
> {quote}
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> Has the setting of mm parameter specs, or description of file setting changed?
> [Solr 5.4]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> {code}
> [Solr 6.0.1]
> {code:xml}
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> {code}
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Issei Nishigata updated SOLR-9174:
--
Description:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
{code:xml}
{code}
{quote}
[request]
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
[Solr 6.0.1]
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
was:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
{quote}
[schema]
[request]
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
[Solr 6.0.1]
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> {code:xml}
>
>
> maxGramSize="2"/>
>
>
> {code}
> {quote}
> [request]
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> Has the setting of mm parameter specs, or description of file setting changed?
> [Solr 5.4]
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> [Solr 6.0.1]
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[
https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Issei Nishigata updated SOLR-9174:
--
Description:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
{quote}
[schema]
[request]
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
{quote}
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
[Solr 6.0.1]
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
was:
“mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
In Solr 5.4, mm parameter works expectedly with the following setting.
---
[schema]
[request]
http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
—
After Solr 5.5, the result will not be the same as Solr 5.4.
Has the setting of mm parameter specs, or description of file setting changed?
[Solr 5.4]
...
2
solar
edismax
AND
...
0
solr
solar
solar
(+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
+(((text:so text:ol text:la
text:ar)~2))
...
[Solr 6.0.1]
...
2
solar
edismax
AND
...
solar
solar
(+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
+((+text:so +text:ol +text:la
+text:ar))
...
As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
Solr 5.5).
> After Solr 5.5, mm parameter doesn't work properly
> --
>
> Key: SOLR-9174
> URL: https://issues.apache.org/jira/browse/SOLR-9174
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
>Affects Versions: 5.5, 6.0, 6.0.1
>Reporter: Issei Nishigata
>
> “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5.
> In Solr 5.4, mm parameter works expectedly with the following setting.
> {quote}
> [schema]
>
>
> maxGramSize="2"/>
>
>
> [request]
> http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar
> {quote}
> After Solr 5.5, the result will not be the same as Solr 5.4.
> Has the setting of mm parameter specs, or description of file setting changed?
> [Solr 5.4]
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> 0
>
> solr
>
>
>
>
> solar
> solar
>
> (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord
>
> +(((text:so text:ol text:la
> text:ar)~2))
> ...
>
> [Solr 6.0.1]
>
> ...
>
> 2
> solar
> edismax
> AND
>
> ...
>
>
> solar
> solar
>
> (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord
>
> +((+text:so +text:ol +text:la
> +text:ar))
> ...
> As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after
> Solr 5.5).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[ https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issei Nishigata updated SOLR-9174: -- External issue ID: 8812 > After Solr 5.5, mm parameter doesn't work properly > -- > > Key: SOLR-9174 > URL: https://issues.apache.org/jira/browse/SOLR-9174 > Project: Solr > Issue Type: Bug > Components: query parsers, search >Affects Versions: 5.5, 6.0, 6.0.1 >Reporter: Issei Nishigata > > “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5. > In Solr 5.4, mm parameter works expectedly with the following setting. > --- > [schema] > > > maxGramSize="2"/> > > > [request] > http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar > — > After Solr 5.5, the result will not be the same as Solr 5.4. > Has the setting of mm parameter specs, or description of file setting changed? > [Solr 5.4] > > ... > > 2 > solar > edismax > AND > > ... > > > 0 > > solr > > > > > solar > solar > > (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord > > +(((text:so text:ol text:la > text:ar)~2)) > ... > > [Solr 6.0.1] > > ... > > 2 > solar > edismax > AND > > ... > > > solar > solar > > (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord > > +((+text:so +text:ol +text:la > +text:ar)) > ... > As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after > Solr 5.5). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
[ https://issues.apache.org/jira/browse/SOLR-9174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issei Nishigata updated SOLR-9174: -- External issue ID: (was: 8812) > After Solr 5.5, mm parameter doesn't work properly > -- > > Key: SOLR-9174 > URL: https://issues.apache.org/jira/browse/SOLR-9174 > Project: Solr > Issue Type: Bug > Components: query parsers, search >Affects Versions: 5.5, 6.0, 6.0.1 >Reporter: Issei Nishigata > > “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5. > In Solr 5.4, mm parameter works expectedly with the following setting. > --- > [schema] > > > maxGramSize="2"/> > > > [request] > http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar > — > After Solr 5.5, the result will not be the same as Solr 5.4. > Has the setting of mm parameter specs, or description of file setting changed? > [Solr 5.4] > > ... > > 2 > solar > edismax > AND > > ... > > > 0 > > solr > > > > > solar > solar > > (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord > > +(((text:so text:ol text:la > text:ar)~2)) > ... > > [Solr 6.0.1] > > ... > > 2 > solar > edismax > AND > > ... > > > solar > solar > > (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord > > +((+text:so +text:ol +text:la > +text:ar)) > ... > As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after > Solr 5.5). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-9174) After Solr 5.5, mm parameter doesn't work properly
Issei Nishigata created SOLR-9174: - Summary: After Solr 5.5, mm parameter doesn't work properly Key: SOLR-9174 URL: https://issues.apache.org/jira/browse/SOLR-9174 Project: Solr Issue Type: Bug Components: query parsers, search Affects Versions: 6.0.1, 6.0, 5.5 Reporter: Issei Nishigata “mm" parameter does not work properly, when I set "q.op=AND” after Solr 5.5. In Solr 5.4, mm parameter works expectedly with the following setting. --- [schema] [request] http://localhost:8983/solr/collection1/select?defType=edismax=AND=2=solar — After Solr 5.5, the result will not be the same as Solr 5.4. Has the setting of mm parameter specs, or description of file setting changed? [Solr 5.4] ... 2 solar edismax AND ... 0 solr solar solar (+DisjunctionMaxQuerytext:so text:ol text:la text:ar)~2/no_coord +(((text:so text:ol text:la text:ar)~2)) ... [Solr 6.0.1] ... 2 solar edismax AND ... solar solar (+DisjunctionMaxQuery(((+text:so +text:ol +text:la +text:ar/no_coord +((+text:so +text:ol +text:la +text:ar)) ... As shown above, parsedquery also differs from Solr 5.4 and Solr 6.0.1(after Solr 5.5). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
