[
https://issues.apache.org/jira/browse/SOLR-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902558#comment-14902558
]
Varun Thacker commented on SOLR-8078:
-------------------------------------
bq. 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.
We can print messages in the startup script similarly to what we do currently
to alter soft commits:
{code}
POSTing request to Config API: http://localhost:8983/solr/gettingstarted/config
{"set-property":{"updateHandler.autoSoftCommit.maxTime":"3000"}}
{code}
bq. 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.
+1
So to summarize the motivation for merging would be :
1. Easier for us to maintain one config
2. Nudging users to start using APIs instead of hand editing the config files
> 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]
