You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/08/18 10:03:20 UTC

[jira] [Comment Edited] (IGNITE-3289) .NET: Add logging messages

    [ https://issues.apache.org/jira/browse/IGNITE-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424651#comment-15424651 ] 

Pavel Tupitsyn edited comment on IGNITE-3289 at 8/18/16 10:02 AM:
------------------------------------------------------------------

Java side checks for `quiet` for some of the output, and either writes it to console, or to logger.
We may do the same for things like startup message with version and QueryEntity warnings.

In quiet mode there is only minimal output to console. In non-quiet mode, all console output is done via logger, there is no direct output.


was (Author: ptupitsyn):
Java side checks for `quiet` for some of the output, and either writes it to console, or to logger.
We may do the same for things like startup message with version and QueryEntity warnings.

> .NET: Add logging messages
> --------------------------
>
>                 Key: IGNITE-3289
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3289
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 1.7
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .net, roadmap
>             Fix For: 1.8
>
>
> Add various logging where it might be useful:
> * Startup (starting JVM, loading DLLs, resolving IGNITE_HOME and classpath, initializing store, etc)
> * Unmanaged callbacks
> * Anything else?
> Investigate whether we should write to console as well, taking IGNITE_QUIET flag into account.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)