Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1736697929.87221267755447123.JavaMail.jira@brutus.apache.org>
Date: Fri, 5 Mar 2010 02:17:27 +0000 (UTC)
From: "Michael Henson (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1716) Add logging support for
 ScriptTransformer
In-Reply-To: <1135788790.158971263236694610.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841659#action_12841659 ] 

Michael Henson commented on SOLR-1716:
--------------------------------------

Is this intended to replace the Rhino built-in "print()" function? I've used that to successfully debug script transformers recently.

> Add logging support for ScriptTransformer
> -----------------------------------------
>
>                 Key: SOLR-1716
>                 URL: https://issues.apache.org/jira/browse/SOLR-1716
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>            Reporter: Uri Boness
>             Fix For: 1.5
>
>         Attachments: SOLR-1716.patch, SOLR-1716.patch
>
>
> Currently it's very hard to debug the logic embedded in the script ran by the ScriptTransformer. There should be a possibility to add a logger to the function signature, which can be used for logging.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.