[
https://issues.apache.org/jira/browse/LUCENE-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724016#action_12724016
]
Shai Erera commented on LUCENE-1716:
------------------------------------
I was afraid of that ... I think we should just delete that section of the
test. If you give an infoStream file which the OS cannot create, you'll get an
exception. I see no reason to test for it.
Would you like me to update the patch, or can you just delete this part of the
patch if you think it's ready to commit (the last lines of the patch - 587-597)?
> Adding norms, properties indexing and writer.infoStream support to benchmark
> ----------------------------------------------------------------------------
>
> Key: LUCENE-1716
> URL: https://issues.apache.org/jira/browse/LUCENE-1716
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Shai Erera
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1716.patch
>
>
> I would like to add the following support in benchmark:
> # Ability to specify whether norms should be stored in the index.
> # Ability to specify whether norms should be stored for the body field
> (assuming norms are usually stored for that field in real life applications,
> make it explicit)
> # Ability to specify an infoStream for IndexWriter
> # Ability to specify whether to index the properties returned on DocData (for
> content sources like TREC, these may include arbitrary <meta> tags, which we
> may not want to index).
> Patch to come shortly.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
