Return-Path: 
 <hdfs-issues-return-154641-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F2D0218EC9
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Wed,  9 Mar 2016 20:44:49 +0000 (UTC)
Received: (qmail 72193 invoked by uid 500); 9 Mar 2016 20:44:41 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 72031 invoked by uid 500); 9 Mar 2016 20:44:41 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 71964 invoked by uid 99); 9 Mar 2016 20:44:41 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2016 20:44:41 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 51F072C1F5C
	for <hdfs-issues@hadoop.apache.org>; Wed,  9 Mar 2016 20:44:41 +0000 (UTC)
Date: Wed, 9 Mar 2016 20:44:41 +0000 (UTC)
From: "Bob Hansen (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12895242.1442866186000.50677.1457556281332@Atlassian.JIRA>
In-Reply-To: <JIRA.12895242.1442866186000@Atlassian.JIRA>
References: <JIRA.12895242.1442866186000@Atlassian.JIRA>
 <JIRA.12895242.1442866186800@arcas>
Subject: [jira] [Commented] (HDFS-9118) Add logging system for libdhfs++
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Bob Hansen commented on HDFS-9118:
----------------------------------

Great.  If we can, let's implement the plugins for the C-API glue logger and the stream/stderr logger.  If we want to be super-cool, we could include example plug-ins for google logging (but we don't want to have a dependency here).

What data types to we need to support in the first pass?  I would say all the fundamental types http://en.cppreference.com/w/cpp/language/types and special handling for const char * and const std::string &.  

I think we should be able to have a fallback << <T>foo that calls std::to_string<T>(foo) that covers many cases.

> Add logging system for libdhfs++
> --------------------------------
>
>                 Key: HDFS-9118
>                 URL: https://issues.apache.org/jira/browse/HDFS-9118
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>    Affects Versions: HDFS-8707
>            Reporter: Bob Hansen
>            Assignee: James Clampffer
>         Attachments: HDFS-9118.HDFS-8707.000.patch, HDFS-9118.HDFS-8707.001.patch
>
>
> With HDFS-9505, we've starting logging data from libhdfs++.  Consumers of the library are going to have their own logging infrastructure that we're going to want to provide data to.  
> libhdfs++ should have a logging library that:
> * Is overridable and can provide sufficient information to work well with common C++ logging frameworks
> * Has a rational default implementation 
> * Is performant



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