[
https://issues.apache.org/jira/browse/SOLR-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761578#action_12761578
]
Shalin Shekhar Mangar commented on SOLR-1483:
---------------------------------------------
bq. What comments are you referring to?
The comments just before int, float, long, double say "For faster range
queries, consider the tint/tfloat/tlong/tdouble types." But
tint/tfloat/tlong/tdouble are actually the same as int/float/long/double with
precisionStep being different.
The example schema has 4 types of numeric fields - int/tint/pint/sint. I think
we should have only one trie field else we should clearly document why using
int is better/different than sint/pint. Without that it would be pretty
confusing to a new Solr user who starts off with 1.4
> Example schema is confusing with int, tint and pint fields
> ----------------------------------------------------------
>
> Key: SOLR-1483
> URL: https://issues.apache.org/jira/browse/SOLR-1483
> Project: Solr
> Issue Type: Bug
> Components: documentation
> Reporter: Shalin Shekhar Mangar
> Fix For: 1.4
>
>
> Example schema defines int (TrieIntField), tint (TrieIntField) and pint
> (IntField) which is confusing. In particular, the comments for int fields
> tell users to use tint types (which is the same thing).
> Let us remove tint, tlong, tdouble, tdate types from example schemas and fix
> the comments - carefully noting the things trie fields do not work with.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
