You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by GitBox <gi...@apache.org> on 2021/04/10 17:14:42 UTC

[GitHub] [lucenenet] rclabo commented on issue #270: Need tests to ensure 2-way index/codec compatibility with Lucene

rclabo commented on issue #270:
URL: https://github.com/apache/lucenenet/issues/270#issuecomment-817173186


   I had a similar thought and Shad pointed me to this issue.  I was thinking about it slightly differently.  Here is another way we might accomplish the same goal of ensuring that a Lucene.NET 4.8 index is compatible with Lucene 4.8.0:
   
   We could index a decent size set of documents using some test code that utilizes stored fields, DocValues, term positions, norms and such.  Then port that code to java and index the same set of documents using 4.8 java Lucene.  Then run a byte by byte comparison of the index files of Lucene.NET and Java Lucene.  This would unequivocally validate that the codec is sound.  And the cool thing is the code could be leveraged again any time we port another codec like the one used in 9.0.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org