[
https://issues.apache.org/jira/browse/HTRACE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062149#comment-15062149
]
Hudson commented on HTRACE-328:
-------------------------------
SUCCESS: Integrated in HTrace-Master #231 (See
[https://builds.apache.org/job/HTrace-Master/231/])
HTRACE-328. htraced continues scanning in some cases even when no more
(iwasakims: rev 2210541c411d7920cf36d7da5f5ba706833a8af6)
* htrace-htraced/go/src/org/apache/htrace/htraced/rest.go
* htrace-htraced/go/src/org/apache/htrace/htraced/datastore.go
* htrace-htraced/go/src/org/apache/htrace/htraced/datastore_test.go
> 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
> Fix For: 4.1
>
> 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)
