[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788116#action_12788116
]
Chris A. Mattmann commented on SOLR-1131:
-----------------------------------------
Hi Yonik:
I agree in general with your points above regarding unit tests. However, there
seems to be a contradiction in your last statement to what you proposed above:
bq. schema.xml: geo will be core... let's not add a new/different schema file
in tests for this and simply add it to the latest schema12
Why have unit tests point at the actual schema? That explicitly ties your unit
tests to the shipped ops schema, and then encourages people to write unit tests
against it (which could lead to the specific number checks that will break when
the schema is updated as you mentioned). Instead +1 for having a separate test
schema even if it causes duplication it insulates change.
Cheers,
Chris
> Allow a single field type to index multiple fields
> --------------------------------------------------
>
> Key: SOLR-1131
> URL: https://issues.apache.org/jira/browse/SOLR-1131
> Project: Solr
> Issue Type: New Feature
> Components: Schema and Analysis
> Reporter: Ryan McKinley
> Assignee: Grant Ingersoll
> Fix For: 1.5
>
> Attachments: SOLR-1131-IndexMultipleFields.patch, SOLR-1131.patch,
> SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.patch
>
>
> In a few special cases, it makes sense for a single "field" (the concept) to
> be indexed as a set of Fields (lucene Field). Consider SOLR-773. The
> concept "point" may be best indexed in a variety of ways:
> * geohash (sincle lucene field)
> * lat field, lon field (two double fields)
> * cartesian tiers (a series of fields with tokens to say if it exists within
> that region)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
