lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-464) <copyField> requests between dissimilar types should have consistent results
Date Tue, 22 Jan 2008 07:02:36 GMT

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

Hoss Man commented on SOLR-464:
-------------------------------

Lance: I'm not understanding your description of this issue ... copyField has completely consistent
behavior -- it always copies the source field to the dest field ... i just tested and had
no problems copying a "date" field to a "string" field -- no failure, no silent failure.

as i mentioned in the mailing list: there are definite improvements that could be made to
make it easier to convert input date strings to other date formats (including integers) but
that's really an orthoginal issue to copyField.

do you have any specific examples of cases where copyField completley failed to work?

> <copyField> requests between dissimilar types should have consistent results
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-464
>                 URL: https://issues.apache.org/jira/browse/SOLR-464
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.3
>         Environment: Any Solr environment
>            Reporter: Lance Norskog
>            Priority: Minor
>
> The <copyField> directive works between certain dissimilar types, but does not
work among other types. The directive works between 'sint' and 'integer' types.  However,
copying a 'date' field to a 'String' field does not express the date as a string. The directive
also fails silently.
> The behaviour of <copyfield> between different types should be consistent. It should
either always fail, or always succeed. If the policy is that it should fail in all cases,
it should give an error on loading the schema, rather than failing silently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message