[ 
https://issues.apache.org/jira/browse/SOLR-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622329#comment-16622329
 ] 

Alexandre Rafalovitch commented on SOLR-12789:
----------------------------------------------

UIMA has been removed as of Solr 7.5, as it was incredible out of date and the 
UIMA architecture itself has changed significantly. See SOLR-11694. 

I am not quite sure there is a viable next step for this. Especially, not as a 
blocker for a version that is no longer supported beyond security fixes.

> UIMA enhancements to allow for dynamic AE detection
> ---------------------------------------------------
>
>                 Key: SOLR-12789
>                 URL: https://issues.apache.org/jira/browse/SOLR-12789
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: contrib - UIMA
>    Affects Versions: 6.0
>            Reporter: Aaron LaBella
>            Priority: Blocker
>              Labels: ready-to-commit
>         Attachments: SOLR-12789-1.patch, SOLR-12789-2.patch, 
> SOLR-12789-3.patch
>
>
> I've been sitting on this patch for over 2 years (and likewise it's been 
> running IN production for the same) ... finally got around to contributing it 
> back to the community.  This change prepares the UIMAUpdateRequestProcessor 
> to allow subclasses to have additional control over how the analysis engine 
> is selected.  In my case, I wrote a sub-class that allows for *dynamic* 
> detection of the UIMA analysis engine based on the document fields.  ie: a 
> field in the document can be used to select different UIMA configurations and 
> rules.
>  
> Can someone please commit this as soon as possible.  I don't necessarily need 
> it to be back-ported, having in 7.4.1 would suffice.
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to