lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5228) Don't require <field> or <dynamicField> be inside of <fields> -- or that <fieldType> be inside of <types>
Date Mon, 09 Sep 2013 23:37:52 GMT

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

Robert Muir commented on SOLR-5228:
-----------------------------------

I think its annoying the fields and fieldTypes have to be in separate sections too. This makes
it hard for you to logically arrange things in such a way that its readable without lots of
scrolling up and down and getting lost.

Can we just go the simple route of deprecating 'fields' and 'types' in 4.x (throw error in
5.x), and in 4.x also allow field/fieldtypes to be "top-level" in the schema.

I think this is ultimately simpler than just willy-nilly allowing shit to be nested underneath
anywhere: thats hard to maintain: and it still allows people who want to group types/fields
together to do that, and those that want to put them side-by-side to do that too.
                
> Don't require <field> or <dynamicField> be inside of <fields> -- or
that <fieldType> be inside of <types>
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5228
>                 URL: https://issues.apache.org/jira/browse/SOLR-5228
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>
> On the solr-user mailing list, Nutan recently mentioned spending days trying to track
down a problem that turned out to be because he had attempted to add a {{<dynamicField
.. />}} that was outside of the {{<fields>}} block in his schema.xml -- Solr was
just silently ignoring it.
> We have made improvements in other areas of config validation by generating statup errors
when tags/attributes are found that are not expected -- but in this case i think we should
just stop expecting/requiring that the {{<fields>}} and {{<types>}} tags will
be used to group these sorts of things.  I think schema.xml parsing should just start ignoring
them and only care about finding the {{<field>}}, {{<dynamicField>}}, and {{<fieldType>}}
tags wherever they may be.
> If people want to keep using them, fine.  If people want to mix fieldTypes and fields
side by side (perhaps specify a fieldType, then list all the fields using it) fine.  I don't
see any value in forcing people to use them, but we definitely shouldn't leave things the
way they are with otherwise perfectly valid field/type declarations being silently ignored.
> ---
> I'll take this on unless i see any objections.

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


Mime
View raw message