lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1483) Example schema is confusing with int, tint and pint fields
Date Wed, 07 Oct 2009 21:11:31 GMT

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

Yonik Seeley commented on SOLR-1483:
------------------------------------

bq. The doubling memory issue for p-types should still be noted somewhere though.

I had just always considered it as unsupported.  Actually, sortMissingLast should probably
work on trie based fields with precisionStep==0, again at the cost of doubling the fieldCache.
 Less confusing to tell people that it's not supported.

bq. Should I remove pdate too (which already existed in that note)?

Nope - pdate (DateField) uses StringIndex by default, so no increased memory usage.

> 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
>
>         Attachments: SOLR-1483.patch, SOLR-1483.patch, SOLR-1483.patch
>
>
> 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.


Mime
View raw message