[jira] [Commented] (LUCENE-3034) If you vary a setting per round and that setting is a long string, the report padding/columns break down.

["Doron Cohen (JIRA)" <ji...@apache.org>]

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

Doron Cohen commented on LUCENE-3034:
-------------------------------------

Hi Mark, could you add an example algorithm with this behavior?

Also, this is from the package javadocs:

{code}
# multi val params are iterated by NewRound's, added to reports, start with column name.
merge.factor=mrg:10:20
max.buffered=buf:100:1000
{code}

Is it possible to workaround the problem by specifying a sufficiently long column name as the first value, that is, replacing e.g. 'mrg' or 'buf' in the above?

> If you vary a setting per round and that setting is a long string, the report padding/columns break down.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3034
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3034
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/benchmark
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Trivial
>             Fix For: 3.1.1, 4.0
>
>
> This is especially noticeable if you vary a setting where the value is a fully specified class name - in this case, it would be nice if columns in each row still lined up.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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