[
https://issues.apache.org/jira/browse/SOLR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505846
]
Will Johnson commented on SOLR-239:
-----------------------------------
after looking at all the dependencies for IndexSchema and with the addition of
the new solrj stuff in trunk i no longer think this approach is the correct way
to go about things. the LukeRequest/LukeResponse seems to give most of the
same info with ~0 overhead and it's already checked in.
> Read IndexSchema from InputStream instead of Config file
> --------------------------------------------------------
>
> Key: SOLR-239
> URL: https://issues.apache.org/jira/browse/SOLR-239
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.2
> Environment: all
> Reporter: Will Johnson
> Priority: Minor
> Fix For: 1.2
>
> Attachments: IndexSchemaStream.patch, IndexSchemaStream2.patch,
> IndexSchemaStream2.patch, IndexSchemaStream2.patch, IndexSchemaStream2.patch,
> IndexSchemaStream2.patch
>
>
> Soon to follow patch adds a constructor to IndexSchema to allow them to be
> created directly from InputStreams. The overall logic for the Core's use of
> the IndexSchema creation/use does not change however this allows java clients
> like those in SOLR-20 to be able to parse an IndexSchema. Once a schema is
> parsed, the client can inspect an index's capabilities which is useful for
> building generic search UI's. ie provide a drop down list of fields to
> search/sort by.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
