[jira] [Resolved] (HTRACE-328) htraced continues scanning in some cases even when no more results are possible

["Masatake Iwasaki (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HTRACE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Masatake Iwasaki resolved HTRACE-328.
-------------------------------------
          Resolution: Fixed
       Fix Version/s: 4.1
    Target Version/s: 4.1

+1. committed this. Thanks, [~cmccabe] and [~busbey].

> 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)