Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 7 Mar 2013 23:24:12 +0000 (UTC)
From: "Commit Tag Bot (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12635907.1362695282662.403957.1362698652975@arcas>
In-Reply-To: <JIRA.12635907.1362695282662@arcas>
References: <JIRA.12635907.1362695282662@arcas>
Subject: [jira] [Commented] (SOLR-4537) Clean up schema information REST API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Commit Tag Bot commented on SOLR-4537:
--------------------------------------

[branch_4x commit] Steven Rowe
http://svn.apache.org/viewvc?view=revision&revision=1454159

SOLR-4537: Clean up schema information REST API (merged trunk r1454141)

                
> Clean up schema information REST API
> ------------------------------------
>
>                 Key: SOLR-4537
>                 URL: https://issues.apache.org/jira/browse/SOLR-4537
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 4.2
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>            Priority: Minor
>             Fix For: 4.3
>
>         Attachments: SOLR-4537.patch
>
>
> SOLR-4503 introduced schema information REST API resources for fields, dynamicFields, fieldTypes, and copyFields.
> However, TestFieldsCollectionResource tests make assumptions about the order in which results are returned, and FieldsCollectionResource doesn't provide them in a stable order, and as a result, those tests are failing in environments where the hash iteration order is different from mine (see [http://markmail.org/message/phknufx4ywlc7eiw]).
> Also, FieldsCollectionResource always ignores the "includeDynamic" query parameter, which makes sense in the get-me-info-on-all-the-fields case (i.e., the "fl" query parameter is not specified), but when the "fl" query parameter *is* specified, the "includeDynamic" query parameter should be respected, so that if a requested field doesn't match an explicit field, but matches a dynamic field, properties for the matching dynamic field are returned.

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