[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-dev
Subject:    [jira] [Created] (SOLR-8110) Start enforcing field naming recomendations in next X.0 release?
From:       "Hoss Man (JIRA)" <jira () apache ! org>
Date:       2015-09-30 22:20:04
Message-ID: JIRA.12901721.1443651586000.126523.1443651604119 () Atlassian ! JIRA
[Download RAW message or body]

Hoss Man created SOLR-8110:
------------------------------

             Summary: Start enforcing field naming recomendations in next X.0 \
release?  Key: SOLR-8110
                 URL: https://issues.apache.org/jira/browse/SOLR-8110
             Project: Solr
          Issue Type: Improvement
            Reporter: Hoss Man


For a very long time now, Solr has made the following "recommendation" regarding \
field naming conventions...

bq. field names should consist of alphanumeric or underscore characters only and not \
start with a digit.  This is not currently strictly enforced, but other field names \
will not have first class support from all components and back compatibility is not \
guaranteed.  ...

I'm opening this issue to track discussion about if/how we should start enforcing \
this as a rule instead (instead of just a "recommendation") in our next/future X.0 \
(ie: major) release.

The goals of doing so being:
* simplify some existing code/apis that currently use hueristics to deal with lists \
of field and produce strange errors when the huerstic fails (example: \
                ReturnFields.add)
* reduce confusion/pain for new users who might start out unaware of the recommended \
conventions and then only later encountering a situation where their field names are \
not supported by some feature and get frustrated because they have to change their \
schema, reindex, update index/query client expectations, etc...




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]