lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-5940) change index backwards compatibility policy.
Date Fri, 19 Sep 2014 05:26:34 GMT

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

Shawn Heisey commented on LUCENE-5940:
--------------------------------------

bq. i also get the feeling a lot of the lucene devs in general don't think "full reindexing"
is an issue and can just be done at any point with minimal cost (just a vibe i've picked up).

You're definitely not wrong here.  When first getting an index into production (often daily
or even more frequently), and later when the application needs change, the user must make
changes to the code (Lucene) or schema (Solr, elasticsearch, or other product) that are incompatible
with the existing index.  When a user obtains help from a mailing list or other support resource,
such a change is VERY likely.

Reindexing is part and parcel of search.  Users who are unable to efficiently perform a reindex
will usually find themselves without the search capabilities that they really need, because
they made incorrect early assumptions that can't be fixed without reindexing.  This can be
the case even if they go years without upgrading their Lucene libraries.  If the actual source
data is difficult to obtain, it's strongly recommended that it be gathered into an intermediate
store with excellent retrieval characteristics, such as a database.


> change index backwards compatibility policy.
> --------------------------------------------
>
>                 Key: LUCENE-5940
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5940
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>
> Currently, our index backwards compatibility is unmanageable. The length of time in which
we must support old indexes is simply too long.
> The index back compat works like this: everyone wants it, but there are frequently bugs,
and when push comes to shove, its not a very sexy thing to work on/fix, so its hard to get
any help.
> Currently our back compat "promise" is just a broken promise, because we cannot actually
guarantee it for these reasons.
> I propose we scale back the length of time for which we must support old indexes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message