lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SOLR-3250) Dynamic Field capabilities based on value not name
Date Mon, 01 Jul 2013 16:54:21 GMT

     [ https://issues.apache.org/jira/browse/SOLR-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Rowe resolved SOLR-3250.
------------------------------

       Resolution: Fixed
    Fix Version/s: 4.4
                   5.0
         Assignee: Steve Rowe

The constituent issues have all been committed.

Further improvements can be made in new issues.
                
> Dynamic Field capabilities based on value not name
> --------------------------------------------------
>
>                 Key: SOLR-3250
>                 URL: https://issues.apache.org/jira/browse/SOLR-3250
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Steve Rowe
>             Fix For: 5.0, 4.4
>
>
> In some situations, one already knows the schema of their content, so having to declare
a schema in Solr becomes cumbersome in some situations.  For instance, if you have all your
content in JSON (or can easily generate it) or other typed serializations, then you already
have a schema defined.  It would be nice if we could have support for dynamic fields that
used whatever name was passed in, but then picked the appropriate FieldType for that field
based on the value of the content.  So, for instance, if the input is a number, it would select
the appropriate numeric type.  If it is a plain text string, it would pick the appropriate
text field (you could even add in language detection here).  If it is comma separated, it
would treat them as keywords, etc.  Also, we could likely send in a hint as to the type too.
> With this approach, you of course have a "first in wins" situation, but assuming you
have this schema defined elsewhere, it is likely fine.
> Supporting such cases would allow us to be schemaless when appropriate, while offering
the benefits of schemas when appropriate.  Naturally, one could mix and match these too.

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