[
https://issues.apache.org/jira/browse/HTRACE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060199#comment-15060199
]
Colin Patrick McCabe commented on HTRACE-328:
---------------------------------------------
bq. I was puzzled at first look but the cause seems to be that break can not be
used under case to break out of surrounding for loop
Yeah.
bq. Is \[the change to GREATER_THAN_OR_EQUALS\] needed? Tests passed without
this.
This isn't needed with GREATER_THAN_OR_EQUALS, since leveldb always seeks to a
point at least greater than or equal to the key given. I posted a v2 which
doesn't change this.
> htraced continues scanning in some cases even when no more results are
> possible
> -------------------------------------------------------------------------------
>
> Key: HTRACE-328
> URL: https://issues.apache.org/jira/browse/HTRACE-328
> Project: HTrace
> Issue Type: Bug
> Components: htraced
> Affects Versions: 4.1
> Reporter: Sean Busbey
> Assignee: Colin Patrick McCabe
> Priority: Critical
> Attachments: HTRACE-328.001.patch, HTRACE-328.002.patch
>
>
> htraced continues scanning in some cases even when no more results are
> possible.
> The clearest example of this is doing a point query on a span id. It should
> be just seeking to where the span would be (if it existed) and then either
> reading it or returning "not found." Instead, it scans the whole leveldb
> database. This can be quite slow on larger leveldb instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
