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

Robert Muir commented on LUCENE-2764:
-------------------------------------

Simon looks good.

this way, we randomly emulate working with lucene 3.0 indexes in our test, 
which are always completely preflex codec.

the patch looks good to me (i would fix the RAMDOM spelling to RANDOM in that 
one place, thats all).

It would probably be good to get Mike to check that "impersonation" is working 
[this is the whole business of how we use preflex-rw for writing but preflex 
for reading and they share the same name]. I think at one time, maybe for about 
5 minutes i understood how this worked before, but i lost it.

> Allow tests to use random codec per field
> -----------------------------------------
>
>                 Key: LUCENE-2764
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2764
>             Project: Lucene - Java
>          Issue Type: Test
>          Components: Tests
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: LUCENE-2764.patch, LUCENE-2764.patch, LUCENE-2764.patch, 
> LUCENE-2764.patch
>
>
> Since we now have a real per field codec support we should enable to run the 
> tests with a random codec per field. When I change something related to 
> codecs internally I would like to ensure that whatever combination of codecs 
> (except of preflex) I use the code works just fine. I created a 
> RandomCodecProvider in LuceneTestCase that randomly selects the codec for 
> fields when it sees them the first time. I disabled the test by default to 
> leave the old randomize codec support in as it was / is.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to