[
https://issues.apache.org/jira/browse/HTRACE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025273#comment-15025273
]
Hudson commented on HTRACE-305:
-------------------------------
SUCCESS: Integrated in HTrace-Master #215 (See
[https://builds.apache.org/job/HTrace-Master/215/])
HTRACE-305 htrace-web: Use greater-than-or-equal rather than (cmccabe: rev
5f87495ab6c2d02cc0c6c1584ac006180e260036)
* htrace-webapp/src/main/webapp/index.html
* htrace-webapp/src/main/webapp/app/predicate.js
> htrace-web: Use greater-than-or-equal rather than greater-than in more places
> -----------------------------------------------------------------------------
>
> Key: HTRACE-305
> URL: https://issues.apache.org/jira/browse/HTRACE-305
> Project: HTrace
> Issue Type: Improvement
> Components: htraced, ui
> Affects Versions: 4.1
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Fix For: 4.1
>
> Attachments: HTRACE-305.001.patch, HTRACE-305.002.patch
>
>
> htrace-web: We should use greater-than-or-equal rather than greater-than in
> more places. It generally makes things easier on both the implementation and
> user side. For example, if you only have "Duration greater than" you can't
> search for spans with duration >= 0, but if you have "Duration greater than
> or equal" you can. It's also easier to efficiently implement
> greater-than-or-equal on the backend than greater-than, although we could
> implement the latter efficiently with some more effort.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
