You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2018/07/20 22:43:00 UTC
[jira] [Commented] (SOLR-12570)
OpenNLPExtractNamedEntitiesUpdateProcessor cannot support multi fields
because pattern replacement doesn't work correctly
[ https://issues.apache.org/jira/browse/SOLR-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551389#comment-16551389 ]
Steve Rowe commented on SOLR-12570:
-----------------------------------
+1 to the patch, good catch!
It would be good to have a test for this capability (none there now) - we'd need to generate a test model that predicts multiple entity types; the one test model we have now can only predict {{PERSON}}.
> OpenNLPExtractNamedEntitiesUpdateProcessor cannot support multi fields because pattern replacement doesn't work correctly
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-12570
> URL: https://issues.apache.org/jira/browse/SOLR-12570
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
> Affects Versions: 7.3, 7.3.1, 7.4
> Reporter: Koji Sekiguchi
> Priority: Minor
> Fix For: master (8.0), 7.5
>
> Attachments: SOLR-12570.patch
>
>
> Because of the following code, if resolvedDest is "body_{EntityType}_s" and becomes "body_PERSON_s" by replacement, but once it is replaced, as placeholder ({EntityType}) is overwritten, the destination is always "body_PERSON_s".
> {code}
> resolvedDest = resolvedDest.replace(ENTITY_TYPE, entityType);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org