You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2016/06/28 21:14:57 UTC

[jira] [Commented] (LUCENE-7361) Terms.toStringDebug

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

Robert Muir commented on LUCENE-7361:
-------------------------------------

I don't really think the two are comparable. For memoryindex maybe it is ok to loop over things like fields or terms, but this is not ok for a real index. Can't memoryindex just do this stuff itself?

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org