[
https://issues.apache.org/jira/browse/LUCENE-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135837#comment-14135837
]
Ryan Ernst commented on LUCENE-5956:
------------------------------------
bq. should it really be separate from the current 'backwards-codecs' module?
Not saying if its right or wrong, but thats where the tests for the upgrader
are.
Sure, it could be in the same module. I just though "running" the backwards
codecs sounded weird from a user perspective (not obvious at all)
bq. how valuable is it to support older than N-1 indexes, when the analysis
chains used to create them have now changed?
Yeah, I'm not sure. It's a good point... how would analysis be upgraded at all
except by reindexing? Implying really that to go across major versions you need
to reindex?
bq. how will SPI etc work here, will the older versions somehow have their own
SPI lists in different classloader or something?
Well, I think the only overlapping SPI would be with the last minor release?
e.g. 4.11 upgrader and 5.0 upgrader would both be able to read 4.11. But
yeah...need to figure it out.
> Add runnable index upgrader
> ---------------------------
>
> Key: LUCENE-5956
> URL: https://issues.apache.org/jira/browse/LUCENE-5956
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Ryan Ernst
>
> As a spinoff from discussion in LUCENE-5940, I'd like to add a new module
> "lucene-upgrader", move {{IndexUpgrader}} to this, and add embed older
> versions of lucene (just enough to upgrade indexes) in the built version of
> the module's jar. This would be runnable from the command line with
> something like:
> {{java -jar lucene-upgrader-4.11.0.jar /path/to/index}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
