[
https://issues.apache.org/jira/browse/SOLR-11694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622839#comment-16622839
]
Aaron LaBella commented on SOLR-11694:
--------------------------------------
Apace UIMA 3.0 is in alpha state, and it'll probably be a long time before a.)
its an actual 3.0 release and b.) anyone out there actually adopts it. 2.10.2
is the latest and its from February of 2018. I'm really not sure why we're
pulling a feature out of Solr that has to be used out there by several people.
What harm does it have to keep it there? We're saving 7MB of space?? I don't
actively follow the Solr mailing list and I'm not sure just because no one
responded in ~6 months that you can safely assume that the entire community
doesn't use UIMA. I feel strongly that this is not the right decision here.
If you want to clean up, I'd agree, remove the AlchemyAPI, OpenCalais, and
Tagger. Upgrade uima-core 2.3.1 to 2.10.2 and keep the rest of the Solr/UIMA
classes – they work just fine. There's no reason to pull this contrib project.
> Remove extremely outdated UIMA contrib module
> ---------------------------------------------
>
> Key: SOLR-11694
> URL: https://issues.apache.org/jira/browse/SOLR-11694
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - UIMA
> Reporter: Cassandra Targett
> Assignee: Alexandre Rafalovitch
> Priority: Major
> Fix For: 7.5, master (8.0)
>
> Attachments: SOLR-11694.patch
>
>
> A user on the [solr-user mailing list back in
> June|https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201706.mbox/%3CCANsk%2BC_PvZJ38AQ2VfzKRYSQn6c8b33kGvaXxR3qNS3GQ4VUKA%40mail.gmail.com%3E]
> brought up the fact that IBM has bought Alchemy and keys are no longer
> available to use Solr's UIMA contrib.
> Someone recently made a [similar
> comment|https://lucene.apache.org/solr/guide/7_1/uima-integration.html#comment_7174]
> to the Solr Ref Guide page and asking for a patch.
> I know next to nothing about UIMA, but figured it's worth an issue to
> determine what to do here. I think folks are saying it's no longer usable? Or
> maybe only usable by people who already have keys (which will possibly expire
> at some point)?
> Anyone have an idea what needs to be done here? It seems we should have some
> kind of answer, but if it's no longer usable perhaps we should retire the
> contrib.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
