You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2021/03/26 16:16:00 UTC
[jira] [Commented] (IGNITE-14430) Common logger interface.
[ https://issues.apache.org/jira/browse/IGNITE-14430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309530#comment-17309530 ]
Andrey Mashenkov commented on IGNITE-14430:
-------------------------------------------
It would be nice to add something like as follows:
boolean isInfoEnabled();
boolean isDebugEnabled();
Or add methods (error, warn, info and etc) that allow a message supplier as an argument to prevent message computation if a loglevel is muted.
> Common logger interface.
> ------------------------
>
> Key: IGNITE-14430
> URL: https://issues.apache.org/jira/browse/IGNITE-14430
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3, newbie
> Fix For: 3.0.0-alpha2
>
>
> 1. Introduce a common interface for a logger, like it was done in Ignite to abstract from any 3-rd party logger implementation.
> This will give users the freedom to choose any logger in the future, and prevent possible issues related to unwanted dependencies or dependency versions.
> 2. Add a default implementation based on System.Logger, which was introduced in Java 9, to the core module.
> 3. Remove any 3-rd party logger dependencies in all modules and switch to IgniteLogger if possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)