lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <>
Subject [jira] [Commented] (SOLR-11694) Remove extremely outdated UIMA contrib module
Date Thu, 20 Sep 2018 20:27:00 GMT


Alexandre Rafalovitch commented on SOLR-11694:

Here is a couple of decision points that went into this:
 # I made a call for UIMA use cases on the Solr Users mailing list and got zero positive replies.
 # UIMA version 2.8 was released in May 2016
 # The current version of UIMA is 3.x, with a completely different infrastructure
 # We had integration points that no longer worked for very long time
 # I think you probably can still use UIMA as your own custom module, most of the integration
I deleted was to get it to build and ship (and all the dead examples).

I would say a contribution that upgrades UIMA to the latest 3.x version with at least rudimentary
example/documentation would be viewed positively. However, it does not seem to be what is
being offered here. So, I am -0 on the proposal to just reverse. 

Others may have a different opinion.

> Remove extremely outdated UIMA contrib module
> ---------------------------------------------
>                 Key: SOLR-11694
>                 URL:
>             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|]
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|]
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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message