[
https://issues.apache.org/jira/browse/JENA-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564385#comment-17564385
]
Holger Knublauch commented on JENA-2336:
----------------------------------------
My suggestion is to simply delete the toString function in DatasetGraphBase, or
rename it to a custom function name. From what I can see, none of its
subclasses in Jena defines another toString method, so it doesn't matter which
specific implementation I was using (it was one of the built-in ones).
Meanwhile I found a way in Eclipse to bypass this (Settings > Java > Debug >
Details Formatters) so it's no longer urgent for me, but until I saw that this
issue here was blocking my progress for a couple of hours. So I thought that
reporting this, for others, might be sensible and would be appreciated. If you
don't agree, feel free to close the ticket.
> DatasetGraphBase.toString does not scale (for debugging)
> --------------------------------------------------------
>
> Key: JENA-2336
> URL: https://issues.apache.org/jira/browse/JENA-2336
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: Holger Knublauch
> Priority: Major
>
> When I am debugging Jena-based code and mouse-over a dataset variable, the
> system basically hangs. It seems that the toString() method of
> DatasetGraphBase is producing a complete rendering of the whole dataset using
> WriterGraph.output(out, this, null). And our datasets typically contain
> thousands of named graphs, some of which are quite large.
> This is handled much better in places such as GraphBase.toString, which
> terminates after a certain number of triples.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
