Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 15 Jun 2016 04:21:09 +0000 (UTC)
From: "Reynold Xin (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12950756.1458111525000.682.1465964469609@Atlassian.JIRA>
In-Reply-To: <JIRA.12950756.1458111525000@Atlassian.JIRA>
References: <JIRA.12950756.1458111525000@Atlassian.JIRA> <JIRA.12950756.1458111525634@arcas>
Subject: [jira] [Commented] (SPARK-13928) Move org.apache.spark.Logging into
 org.apache.spark.internal.Logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 15 Jun 2016 04:21:12 -0000


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

Reynold Xin commented on SPARK-13928:
-------------------------------------

It was never meant to be public (the comment had a note saying it's private). You can certainly copy the code out (just a few lines of code) and put it in your own project.


> Move org.apache.spark.Logging into org.apache.spark.internal.Logging
> --------------------------------------------------------------------
>
>                 Key: SPARK-13928
>                 URL: https://issues.apache.org/jira/browse/SPARK-13928
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Reynold Xin
>            Assignee: Wenchen Fan
>             Fix For: 2.0.0
>
>
> Logging was made private in Spark 2.0. If we move it, then users would be able to create a Logging trait themselves to avoid changing their own code. Alternatively, we can also provide in a compatibility package that adds logging.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org