lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] Commented: (SOLR-1483) Example schema is confusing with int, tint and pint fields
Date Wed, 07 Oct 2009 20:29:31 GMT


Shalin Shekhar Mangar commented on SOLR-1483:

I left pint and friends off for a reason... if you try using sortMissingFirst with them, it
will double your fieldCache size.
pint uses a native int[] for the fieldcache entry and the comparator that implements sortMissingFirst
asks for the StringIndex.

This full of gotchas! Things like this should be noted in CHANGES.txt in the upgrading section
as well as on the wiki in the SchemaXml page. A user is very likely to keep using sortMissingFirst
with his old schema in a new 1.4 installation.

> Example schema is confusing with int, tint and pint fields
> ----------------------------------------------------------
>                 Key: SOLR-1483
>                 URL:
>             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.

View raw message