lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] Updated: (LUCENE-1778) Add log.step support per task
Date Mon, 03 Aug 2009 16:05:14 GMT


Mark Miller updated LUCENE-1778:

    Attachment: LUCENE-1778.patch

I changed the delete log step in the existing algs to match the new format and I updated the
package.html to be a bit more correct in terms of log.step.

That should be good enough for this issue, but I think we do also have to reconcile the package.html
documentation with some of the more recent changes. Its not horribly off, but its off, and
their are some tasks it doesn't list.

Relating to this issue, it also still mentions: doc.tokenize.log.step, which is no longer
used. Not fixed in my patch, but should this now be: log.step.ReadTokens ? I'm not sure offhand
what used to use that log name.

> Add log.step support per task
> -----------------------------
>                 Key: LUCENE-1778
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/benchmark
>            Reporter: Shai Erera
>             Fix For: 2.9
>         Attachments: LUCENE-1778.patch, LUCENE-1778.patch
> Following LUCENE-1774, this will add support for log.step per task name, rather than
a single log.step setting for all tasks. The .alg file will support:
> * log.step - for all tasks.
> * log.step.<Task Class Name> - for a specific task. For example, log.step.AddDoc,
or log.step.DeleteDoc
> I will post the patch soon

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:
For additional commands, e-mail:

View raw message