[ https://issues.apache.org/jira/browse/LUCENE-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless updated LUCENE-6084: --------------------------------------- Attachment: LUCENE-6084.patch New patch, just accepting DataOutput also in CorruptIndexException, and fixing Lucene50PostingsWriter to pass that directly (instead of doing the .toString()) itself ... I couldn't find any other callers that "wanted" to pass a DataOutput. > Add reasonable IndexOutput.toString > ----------------------------------- > > Key: LUCENE-6084 > URL: https://issues.apache.org/jira/browse/LUCENE-6084 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Michael McCandless > Assignee: Michael McCandless > Priority: Minor > Fix For: 5.0, Trunk > > Attachments: LUCENE-6084.patch, LUCENE-6084.patch > > > In LUCENE-3539 we fixed IndexInput.toString to always include the > resourceDescription. > I think we should do the same for IndexOutput? > I don't think Lucene currently uses/relies on IndexOutput.toString, but e.g. > at least Elasticsearch does, and likely others, so I think it can only help > if you can see which path is open by this IndexOutput. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org