[
https://issues.apache.org/jira/browse/ASTERIXDB-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219341#comment-16219341
]
ASF subversion and git services commented on ASTERIXDB-2132:
------------------------------------------------------------
Commit 3be86c5820e8d6f6509d255ea80852eb74fd0ee9 in asterixdb's branch
refs/heads/master from [~tillw]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=3be86c5 ]
[ASTERIXDB-2132] Replace ITracer.check
- user model changes: no
- storage format changes: no
- interface changes: yes
Trace categories in the ITracer interface are represented by long
values where each bit represents a category.
Introduce ITraceCategoryRegistry, an interface for a registry/mapping
from Strings to bit positions representing categories.
- add simple tests for Tracer and TraceCategoryRegistry
Change-Id: I3f26ae988d3786ef4ddb17e8fe78f911e7e628f1
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2087
Sonar-Qube: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
> Replace ITracer.check
> ---------------------
>
> Key: ASTERIXDB-2132
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2132
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Abdullah Alamoudi
> Assignee: Till
>
> ITracer.check call replace the tracer with a no op tracer if tracing is not
> enabled.
> However, it is creating some confusion is to how to use the tracer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)