Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 25182F47D for ; Wed, 3 Apr 2013 06:39:20 +0000 (UTC) Received: (qmail 79643 invoked by uid 500); 3 Apr 2013 06:39:19 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 79540 invoked by uid 500); 3 Apr 2013 06:39:18 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 79502 invoked by uid 99); 3 Apr 2013 06:39:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 06:39:16 +0000 Date: Wed, 3 Apr 2013 06:39:16 +0000 (UTC) From: "Dawid Weiss (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-4653) Solr configuration should log inaccessible/ non-existent relative paths 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/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620671#comment-13620671 ] Dawid Weiss commented on SOLR-4653: ----------------------------------- This (the variable substitution) should also work as far as I'm concerned because variables are substituted globally in all text nodes. That's my understanding of the code, didn't check on a live instance. So if you passed ${solr.contrib.root} and it doesn't point anywhere you'd get a warning in the logs. Since some folks expressed their concern about failing hard (and it was actually documented that it won't fail hard) I think it makes sense to preserve this behavior, at least in the same Solr line (4.x). Perhaps another issue changing this behavior should be filed for 5.x. > Solr configuration should log inaccessible/ non-existent relative paths > --------------------------------------------------------------------------------------- > > Key: SOLR-4653 > URL: https://issues.apache.org/jira/browse/SOLR-4653 > Project: Solr > Issue Type: Bug > Reporter: Dawid Weiss > Assignee: Dawid Weiss > Priority: Trivial > Attachments: SOLR-4653.patch > > > Currently the dir path is resolved relative to core's instanceDir but if you don't know it nothing happens (no warning, no nothing). This is very frustrating. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org