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

Hoss Man commented on LUCENE-6213:
----------------------------------

bq. Eg. For M.0.0, expect a test index "(M)x-with-(M-1)x-segments". I think 
this is essentially what you were saying?

My point was that for a sanity check like this, where the focus is on major 
versions, we can  go even farther then just looking at the list of existing 
releases.

In your example, i think that even if there is no official "M" release, the 
smoketester for "M+1" should fail if a test for "(M)x-with-(M-1)x-segments can 
not be found.  

Example: if the trunk version property is set to "8.Y" (where the value of Y is 
irrelevant) then it should be expected that the a "7x-with-6x-segments" index 
is tested -- even if there is no 7.X release yet according to jira / 
archive.apache.org.

that way, in the first few days after a "7x_branch" is created, and trunk's 
version property is updated to "8.0" it will be clear from the smokeTester 
failures on trunk that trunk is not in a state suitable to be released -- by 
definittion trunk won't be suitable for release until a 7.0 release is final 
and the 7x index format is used to create the "7x-with-6x-segments" index for 
the trunk test.


> Add test for IndexFormatTooOldException if a commit has a 3.x segment
> ---------------------------------------------------------------------
>
>                 Key: LUCENE-6213
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6213
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Ryan Ernst
>         Attachments: LUCENE-6213.patch, LUCENE-6213.patch, LUCENE-6213.patch, 
> unsupported.4x-with-3x-segments.zip
>
>
> We should add a 4.x index (4.x commit) with some 3.x segment(s) to our 
> backwards tests.
> I don't think we throw IndexFormatTooOldException correctly in this case. I 
> think instead the user will get a confusing SPI error about a missing codec 
> "Lucene3x".



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to