hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Aggarwal (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-18439) Subclasses of o.a.h.h.chaos.actions.Action all use the same logger
Date Sun, 06 Aug 2017 09:37:00 GMT

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

Sahil Aggarwal reassigned HBASE-18439:
--------------------------------------

    Assignee: Sahil Aggarwal

> Subclasses of o.a.h.h.chaos.actions.Action all use the same logger
> ------------------------------------------------------------------
>
>                 Key: HBASE-18439
>                 URL: https://issues.apache.org/jira/browse/HBASE-18439
>             Project: HBase
>          Issue Type: Bug
>          Components: integration tests
>            Reporter: Mike Drob
>            Assignee: Sahil Aggarwal
>            Priority: Minor
>              Labels: beginner
>
> A bunch of the actions all use the same logger inherited from the super class. We should
have them declare distinct loggers, either each one in class or perhaps we can do something
dynamically like {{LogFactory.getLogger(MethodHandles.lookup().lookupClass()}} and drop the
static modifier on the log field.
> I'm not sure that exact incantation would actually work, but the MethodHandles approach
in general is how logger resolution happens in Solr and it actually works out pretty well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message