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

David Smiley commented on LUCENE-5874:
--------------------------------------

I weighed in on LUCENE-5858.

bq. How is it somewhat related? Its completely related if the motivation here 
is to have all the lucene features: all the other codecs support the full 
feature set.

I think one day there's going to be some new feature only supported by a subset 
of the codecs in the rotation.  If the only tool we have is to say which codecs 
we *don't* want, then it's less ideal then expressing what you *do* want.

> Allow choosing latest default codec (not random)
> ------------------------------------------------
>
>                 Key: LUCENE-5874
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5874
>             Project: Lucene - Core
>          Issue Type: Test
>          Components: modules/test-framework
>            Reporter: David Smiley
>
> Within the Lucene/Solr tests, I can see that we want to widely test the 
> various Lucene Codecs.  And so a test can use a black-list @SuppressCodecs 
> when certain codecs are known not to work with certain tests.  But there is 
> no white-list nor white-list by capabilities (e.g. saying you need term 
> vectors that support payloads).
> In external applications that are using the test infrastructure, this is 
> annoying.  An application generally wants to test with only the codec that 
> ships as default with the particular Lucene version they use.  Now sure, this 
> could be done by using "-Dtests.codec=Lucene46" , or having your 
> \@BeforeClass explicitly do Codec.setDefault(Codec.forName("Lucene46")).  But 
> in both these cases, you have to call out a specific version; you can't 
> simply ask for whatever the latest is for the Lucene version you're using 
> that's on your classpath.  So what I propose is two things: a whitelist 
> annotation \@LuceneTestCase.Codecs and a value "CURRENT" (to align with the 
> LUCENE_CURRENT naming convention).  In this way a test could use the latest 
> Codec and not hit a random failure the first time around just because 
> Lucene3x or some other old codec was chosen.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to