[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-3619:
---------------------------------
Attachment: solrconfig.xml
managed-schema
bq. non field-guessing default should probably just have dynamic fields as a
start
When I look at the managed-schema from the schemaless example (which is what I
based the default on), it has all the popular Solr field types and dynamic
fields defined. I've attached it here for your review - let me know if you want
to add/remove anything.
I'm not trying to be obtuse or argumentative, but can you elaborate on how
enabling an optional feature makes it hard to go to production? If I don't want
field guessing, then my docs coming need to be well-formed to the schema that
is defined.
Disabling field guessing requires one line change (to comment out the
add-unknown-fields-to-the-schema in the update chain) and I don't think we've
ever advocated going to production without the user doing a thorough review of
their solrconfig.xml.
My default solrconfig.xml is attached too, please review as I was pretty
aggressive with my removals.
At this point, it sounds like we're in agreement that there should be a getting
started configset and another one that doesn't have field guessing enabled. Any
other features that you think are important to be enabled /disabled. These
configsets need names? Thinking data-driven-schema (Hoss' term) and default??
> Rename 'example' dir to 'server' and pull examples into an 'examples'
> directory
> -------------------------------------------------------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Timothy Potter
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, managed-schema,
> server-name-layout.png, solrconfig.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
