Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 3 Nov 2016 15:06:58 +0000 (UTC)
From: "Seth Hendrickson (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.13017683.1478185612000.173418.1478185618353@Atlassian.JIRA>
In-Reply-To: <JIRA.13017683.1478185612000@Atlassian.JIRA>
References: <JIRA.13017683.1478185612000@Atlassian.JIRA> <JIRA.13017683.1478185612364@arcas>
Subject: [jira] [Created] (SPARK-18253) ML Instrumentation logging requires
 too much manual implementation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 03 Nov 2016 15:06:59 -0000

Seth Hendrickson created SPARK-18253:
----------------------------------------

             Summary: ML Instrumentation logging requires too much manual implementation
                 Key: SPARK-18253
                 URL: https://issues.apache.org/jira/browse/SPARK-18253
             Project: Spark
          Issue Type: Improvement
          Components: ML
            Reporter: Seth Hendrickson
            Priority: Minor


[SPARK-14567|https://issues.apache.org/jira/browse/SPARK-14567] introduced an {{Instrumentation}} class for standardized logging of ML training sessions. Right now, we manually log individual params for each algorithm, partly because we don't want to log all params since some params can be huge in size, and we could flood the logs. We should find a more sustainable way of logging params in ML algos. The current approach does not seem sustainable.


--
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