[
https://issues.apache.org/jira/browse/SOLR-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761612#action_12761612
]
Grant Ingersoll commented on SOLR-1483:
---------------------------------------
int says:
{quote}
Default numeric field types. For faster range queries, consider the
tint/tfloat/tlong/tdouble types.
Note: the statistics component does not yet work with these field types.
{quote}
tint says:
{quote}
Numeric field types that index each value at various levels of precision
to accelerate range queries when the number of values between the range
endpoints is large. See the javadoc for NumericRangeQuery for internal
implementation details.
Smaller precisionStep values (specified in bits) will lead to more tokens
indexed per value, slightly larger index size, and faster range queries.
Note: faceting does not currently work for these fields.
{quote}
I guess I'd add that in the int case, you could add some "why" to it, but
otherwise, I think both comments explain the case for each one. One gives
faster range queries than the other.
> 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.
