[
https://issues.apache.org/jira/browse/LUCENE-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355259#comment-15355259
]
Alan Woodward commented on LUCENE-7361:
---------------------------------------
I agree with Robert here - toString() is used in things like IDE debugging
windows, what happens if I run a debugging session on a 2Gb index?
Having some kind of introspector on an index could be useful, though, so maybe
instead of adding .toString() implementations, we have a special class in misc/
that prints this information out? And then MemoryIndex.toString() can just
include some top-level stats, and users get pointed to the introspector for
more detailed debugging info.
> Terms.toStringDebug
> -------------------
>
> Key: LUCENE-7361
> URL: https://issues.apache.org/jira/browse/LUCENE-7361
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: David Smiley
> Attachments: MemoryIndexToString.java
>
>
> While fixing LUCENE-7340, MemoryIndex.toString(), I thought MemoryIndex
> shouldn't need it's own debug toString() impl for its Terms when there could
> be a generic one. So here I propose that we create a
> Terms.toStringDebug(Appendable result, int charLimit, String indent) or
> some-such but probably not override toString() for obvious reasons. Maybe
> also have this on Fields() that simply loops and calls out to the one on
> Terms.
> The format is debatable.
--
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
