lucene-dev mailing list archives

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


Eric Pugh commented on SOLR-11694:

I've been down the upgrade UIMA process before, and I failed..   I dug into JIRA, and it was
back in 2012!  SOLR-3736 and SOLR-3738 specifically.    

I think as important as adding new features is deprecating/removing features that no longer
have significant community support.   As fascinated as I was by UIMA, I think that is an example
of a feature that doesn't really fit into the mainline use cases for Solr, otherwise the upgrade
to UIMA 3.x would have happened before now.

I suspect that the best thing would be a proper indexing pipeline that encompasses the use
cases for Tika, UIMA, the ScriptingUpdateRequestHandler and friends?   

Then you could have the UIMA plugin be it's own project with it's own dedicated folks... 
  But right now, I think the core Solr committership isn't interested in UIMA.

> 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