[jira] [Updated] (SOLR-10264) ManagedSynonymFilterFactory does not parse multi-term synonyms

2017-04-14 Thread Mark Miller (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Miller updated SOLR-10264:
---
Fix Version/s: (was: 6x)
   6.6

> ManagedSynonymFilterFactory does not parse multi-term synonyms
> --
>
> Key: SOLR-10264
> URL: https://issues.apache.org/jira/browse/SOLR-10264
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.4.2
>Reporter: Jörg Rathlev
>Assignee: Christine Poerschke
>Priority: Minor
> Fix For: master (7.0), 6.6
>
> Attachments: SOLR-10264.patch, SOLR-10264.patch, SOLR-10264.patch, 
> SOLR-10264.patch, SOLR-10264-test.patch
>
>
> The parser that the {{ManagedSynonymFilterFactory}} uses to parse the JSON 
> resource into a synonym map does not parse multi-term synonyms in the 
> expected way.
> If the synonym {"foo bar":"baz"} is added to the managed resource, the 
> expected behavior is that the multi-term synonym "foo bar" will be mapped to 
> the synonym "baz".
> In the {{analyze}} method of {{SynonymMap.Parser}}, multiple origin terms are 
> concatenated with a separating {{SynonymMap.WORD_SEPARATOR}}, but the 
> {{analyze}} method is not used by the parser in the 
> {{ManagedSynonymFilterFactory}}.
> As a workaround, multi-term synonyms can be uploaded separated by a null 
> character, i.e., uploading {"foo\ubar":"baz"} works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-10264) ManagedSynonymFilterFactory does not parse multi-term synonyms

2017-03-30 Thread Christine Poerschke (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christine Poerschke updated SOLR-10264:
---
Attachment: SOLR-10264.patch

Attaching final(\?) patch, will commit early next week or so if no further 
comments or concerns.

> ManagedSynonymFilterFactory does not parse multi-term synonyms
> --
>
> Key: SOLR-10264
> URL: https://issues.apache.org/jira/browse/SOLR-10264
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.4.2
>Reporter: Jörg Rathlev
>Assignee: Christine Poerschke
>Priority: Minor
> Attachments: SOLR-10264.patch, SOLR-10264.patch, SOLR-10264.patch, 
> SOLR-10264.patch, SOLR-10264-test.patch
>
>
> The parser that the {{ManagedSynonymFilterFactory}} uses to parse the JSON 
> resource into a synonym map does not parse multi-term synonyms in the 
> expected way.
> If the synonym {"foo bar":"baz"} is added to the managed resource, the 
> expected behavior is that the multi-term synonym "foo bar" will be mapped to 
> the synonym "baz".
> In the {{analyze}} method of {{SynonymMap.Parser}}, multiple origin terms are 
> concatenated with a separating {{SynonymMap.WORD_SEPARATOR}}, but the 
> {{analyze}} method is not used by the parser in the 
> {{ManagedSynonymFilterFactory}}.
> As a workaround, multi-term synonyms can be uploaded separated by a null 
> character, i.e., uploading {"foo\ubar":"baz"} works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-10264) ManagedSynonymFilterFactory does not parse multi-term synonyms

2017-03-20 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/SOLR-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jörg Rathlev updated SOLR-10264:

Attachment: SOLR-10264.patch

Thank you, Christine, that almost-complete test case was very helpful!

I've attached an updated patch with a working test case for multi-term origins.

Compared to Christine's test, I've changed it so that the multi-term origin is 
in the indexed document, and the single-term synonym in the query, because 
multi-term origins in the query are problematic for unrelated reasons.

> ManagedSynonymFilterFactory does not parse multi-term synonyms
> --
>
> Key: SOLR-10264
> URL: https://issues.apache.org/jira/browse/SOLR-10264
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.4.2
>Reporter: Jörg Rathlev
>Priority: Minor
> Attachments: SOLR-10264.patch, SOLR-10264.patch, SOLR-10264-test.patch
>
>
> The parser that the {{ManagedSynonymFilterFactory}} uses to parse the JSON 
> resource into a synonym map does not parse multi-term synonyms in the 
> expected way.
> If the synonym {"foo bar":"baz"} is added to the managed resource, the 
> expected behavior is that the multi-term synonym "foo bar" will be mapped to 
> the synonym "baz".
> In the {{analyze}} method of {{SynonymMap.Parser}}, multiple origin terms are 
> concatenated with a separating {{SynonymMap.WORD_SEPARATOR}}, but the 
> {{analyze}} method is not used by the parser in the 
> {{ManagedSynonymFilterFactory}}.
> As a workaround, multi-term synonyms can be uploaded separated by a null 
> character, i.e., uploading {"foo\ubar":"baz"} works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-10264) ManagedSynonymFilterFactory does not parse multi-term synonyms

2017-03-16 Thread Christine Poerschke (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christine Poerschke updated SOLR-10264:
---
Attachment: SOLR-10264-test.patch

Attaching partial (not yet multi-term) test changes.

> ManagedSynonymFilterFactory does not parse multi-term synonyms
> --
>
> Key: SOLR-10264
> URL: https://issues.apache.org/jira/browse/SOLR-10264
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.4.2
>Reporter: Jörg Rathlev
>Priority: Minor
> Attachments: SOLR-10264.patch, SOLR-10264-test.patch
>
>
> The parser that the {{ManagedSynonymFilterFactory}} uses to parse the JSON 
> resource into a synonym map does not parse multi-term synonyms in the 
> expected way.
> If the synonym {"foo bar":"baz"} is added to the managed resource, the 
> expected behavior is that the multi-term synonym "foo bar" will be mapped to 
> the synonym "baz".
> In the {{analyze}} method of {{SynonymMap.Parser}}, multiple origin terms are 
> concatenated with a separating {{SynonymMap.WORD_SEPARATOR}}, but the 
> {{analyze}} method is not used by the parser in the 
> {{ManagedSynonymFilterFactory}}.
> As a workaround, multi-term synonyms can be uploaded separated by a null 
> character, i.e., uploading {"foo\ubar":"baz"} works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Updated] (SOLR-10264) ManagedSynonymFilterFactory does not parse multi-term synonyms

2017-03-10 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/SOLR-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jörg Rathlev updated SOLR-10264:

Attachment: SOLR-10264.patch

I've attached a patch that modifies the ManagedSynonymParser to call the parent 
class's analyze method on the mapped terms.

> ManagedSynonymFilterFactory does not parse multi-term synonyms
> --
>
> Key: SOLR-10264
> URL: https://issues.apache.org/jira/browse/SOLR-10264
> Project: Solr
>  Issue Type: Bug
>  Security Level: Public(Default Security Level. Issues are Public) 
>  Components: Schema and Analysis
>Affects Versions: 6.4.2
>Reporter: Jörg Rathlev
>Priority: Minor
> Attachments: SOLR-10264.patch
>
>
> The parser that the {{ManagedSynonymFilterFactory}} uses to parse the JSON 
> resource into a synonym map does not parse multi-term synonyms in the 
> expected way.
> If the synonym {"foo bar":"baz"} is added to the managed resource, the 
> expected behavior is that the multi-term synonym "foo bar" will be mapped to 
> the synonym "baz".
> In the {{analyze}} method of {{SynonymMap.Parser}}, multiple origin terms are 
> concatenated with a separating {{SynonymMap.WORD_SEPARATOR}}, but the 
> {{analyze}} method is not used by the parser in the 
> {{ManagedSynonymFilterFactory}}.
> As a workaround, multi-term synonyms can be uploaded separated by a null 
> character, i.e., uploading {"foo\ubar":"baz"} works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org