12 Sep
2013
12 Sep
'13
5:37 p.m.
On Sep 12, 2013, at 5:21 PM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
On 09/12/2013 10:48 AM, Vincent Massol wrote:
The API won't change. Quite the opposite the proposal is about freezing it :)
Hi devs,
Now that we have a SOLR search, I think we should close all Lucene-related JIRA issues as
won't fix, remove the Lucene search by default in XWiki 5.3 and move it to
xwiki-contrib.
I don't think we want to maintain 2 implementation especially since the SOLR one is
better.
Here's my +1.
-1. Although it's just a plugin, the Lucene search has been available
for a very long time, so I view it as an API. And a rather important one. The search has been often customized on client
projects, so it's not
just the default wiki search that's using the Lucene index and the
Lucene search API. Is there a migration plan for porting those custom
searches to the new Solr search? Are we sure the Solr index has support
for all the features that the Lucene one had?
We should follow the standard deprecation strategy:
- mark the plugin as deprecated
- warn users that they should switch to Solr
- write a migration guide
- after a few releases (6.1?), remove the search UI (we still have the
even older DatabaseSearch UI available, why not keep the Lucene one a
bit longer?)
- after a few more releases (7.1?), retire the plugin
The Lucene modules will still be available, just not bundled by default. You could install
them with the EM if you need them.
Whoever is already using Lucene will have the extensions installed and upgrading will not
remove them AFAIK.
We're not that many in term of devs and even you have much less time to work on XWiki
lately. We need to move on. I feel this proposal doesn't break anything important for
users/developers.
The net effect of this proposal is about freezing any dev on Lucene and not releasing it
anymore. It should continue to work as now on older versions.
Thanks
-Vincent
But yes, we could close Lucene-related issues that
we're not going to fix.
--
Sergiu Dumitriu