lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <>
Subject [jira] Commented: (LUCENE-1540) Improvements to contrib.benchmark for TREC collections
Date Sat, 05 Feb 2011 00:54:30 GMT


Doron Cohen commented on LUCENE-1540:

r1066771 - 3x
r1067359 - trunk,

A comment about the merging and messaging the mergeinfo's. 
The great [wiki page about svn-merge|] was very
helpful, just that I merged from 3x to trunk, while there it is recommended the other way
around. I think the two are equivalent, but had to go carefully with it. 

Eventually these are the commands I ran:

cd trunk/lucene/src
svn merge -c 1066771
cd trunk/modules/benchmark
svn merge -c 1066771
cd trunk
svn merge --record-only -c 1066771
svn revert  --depth empty modules/benchmark
svn revert solr

The record-only merge discarded, by itself, the (new) mergeinfo prop from trunk/lucene/src,
and updated the ones in trunk and trunk/src.
Note the use of *revert --depth empty* for reverting (all) property changes.

I'll keep this issue open for a day in case any problem is revealed with this merge process
which I am doing for the first time.

> Improvements to contrib.benchmark for TREC collections
> ------------------------------------------------------
>                 Key: LUCENE-1540
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/benchmark
>            Reporter: Tim Armstrong
>            Assignee: Doron Cohen
>            Priority: Minor
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-1540.patch, LUCENE-1540.patch, LUCENE-1540.patch, LUCENE-1540.patch,
> The benchmarking utilities for  TREC test collections ( are quite
limited and do not support some of the variations in format of older TREC collections.  
> I have been doing some benchmarking work with Lucene and have had to modify the package
to support:
> * Older TREC document formats, which the current parser fails on due to missing document
> * Variations in query format - newlines after <title> tag causing the query parser
to get confused.
> * Ability to detect and read in uncompressed text collections
> * Storage of document numbers by default without storing full text.
> I can submit a patch if there is interest, although I will probably want to write unit
tests for the new functionality first.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message