lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (SOLR-359) LukeResponse.FieldInfo should expose the selected flags info and the indexInfo
Date Fri, 21 Sep 2007 17:11:51 GMT


Grant Ingersoll commented on SOLR-359:

I am working on extending the LukeRequestHandler (LRH) and the LukeResponse to give more info
about the FieldTypes.  Right now, the LRH returns the name of the FieldType, but does not
return the class name.  Also, I would like to return back more structured access to the FieldType
information by extracting it from the IndexInfo in the same way the FieldInfo does now.

Currently,  I am mirroring what is done for the FieldInfo to add FieldTypeInfo. 

One question, though, LRH currently writes out the instance of the Analyzer (around line 371
of LRH), would it be better to just return the class name?  Or do people actually need the
value of Analyzer.toString()

Also, do I need to worry about back-compatibility of the message?  That is, if I add in the
class name of the FieldType instance (i.e. solr.IntField, etc.) does that break the compatibility
of the message?

I will post a new patch shortly which has more access to the FieldType info.

> LukeResponse.FieldInfo should expose the selected flags info and the indexInfo
> ------------------------------------------------------------------------------
>                 Key: SOLR-359
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: clients - java
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>         Attachments: SOLR-359.patch
> The LukeResponse has access, when reading in the NamedList to more information that is
not currently being shared, like the "flags" for each FieldInfo and/or the indexInfo object
so that more info about the fields may be used by the client.

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

View raw message