[
https://issues.apache.org/jira/browse/SOLR-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902519#comment-14902519
]
Steve Rowe commented on SOLR-8078:
----------------------------------
One of the nice things about having separate configsets is that they are full
examples, and I wouldn't want to lose that.
If we merge them, we should make it easy to find the schema/config API JSON
used to compose each configset. Having examples of this, which is a very
likely usage pattern, would be good even if we don't do the merge. And it's
the direction we want to encourage users to go in: think of schema/config as
addressable via API as opposed to static files.
bq. We don't need a minimal config set , since all the extra fields in tech
products is been added by the startup script and is not present otherwise.
Do you mean that the data_driven_schema_configs is already minimal? If so, I
don't agree, there is quite a bit of stuff in there.
We could have only the minimal config set and then deltas (in the form of API
JSONs) for both data driven and tech products.
> Data driven solrconfig spellchecker refers to a non-existent field
> ------------------------------------------------------------------
>
> Key: SOLR-8078
> URL: https://issues.apache.org/jira/browse/SOLR-8078
> Project: Solr
> Issue Type: Bug
> Reporter: Varun Thacker
>
> In the data driven solrconfig.xml file, the "default" spellchecker refers to
> a field called "text" which doesn't exist in the schema.
> Even the "wordbreak" spellchecker refers to a field called "name" which does
> not exist.
> So when you run this query
> {{http://localhost:8983/solr/gettingstarted/spell?q=*}} Solr will throw an
> error.
> I guess the field name should be {{\_text\_}} ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
