[
https://issues.apache.org/jira/browse/SOLR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500704
]
Will Johnson commented on SOLR-239:
-----------------------------------
after seeing that i'd need to regenerate a patch for the new IndexSchema's
SolrException handling i got to thinking about ways to preserve the
getInputStream() functionality. tracing things down a bit it seems to all fall
to Config.openResource(fileName). i was wondering if it might not be better to
extend that code to handle URL's as well as file names by looking for http://
at the beginning of the resourceName. this might open up other avenues for
centralized configuration of all of solr in the future but it does at least
solve this problem and maintain more backwards compatibility with the existing
api.
thoughts?
> 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
>
>
> 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.
