...

Current state: Under Discussion

Discussion threads:

•  Main: https://lists.apache.org/thread

...

• .html/r3bf5981894e5b94f1897f4946b1652f068d3090dbccc84bfe90e130d%40%3Cdev.lucene.apache.org%3E
  
• RefGuide dogfooding: https://

...

• lists.apache.org/

...

• thread.html/r7b4f3acce10fc3e1eceedb32cbd7349ace4af70632ec6f4def16f4ab%40%3Cdev.lucene.apache.org%3E

JIRA: 

...

• https://github.com/arafalov/simplest-solr-config
• https://www.slideshare.net/arafalov/json-in-solr-from-top-to-bottom
• https://www.slideshare.net/arafalov/rebuilding-solr-6-examples-layer-by-layer-lucenesolrrevolution-2016
• https://github.com/arafalov/solr-thai-test
• https://github.com/arafalov/solr-indexing-book

Learning vs Production vs kitchen sink setup

Learning config

• Should be as small as possible and still load in both standalone and cloud configurations
• Should have every line to have a purpose and be explained with RefGuide references
• managed-schema should be ordered in the order of reading comprehension (fieldType, related fields, uniqueKey declaration next to ID)
• Additional examples should layer on top of learning schema to demonstrate different features
• schemaless mode (to be rewritten to be learning mode) is a separate example
• Related issues:

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key SOLR-13652

Production config

• managed-schema should be minimal to allow users to include what is actually needed
• solrconfig.xml
  • should be fairly comprehensive, but obscure defaults and detailed explanation should live in RefGuide. From experience, nobody updates the schema files unless forced to (it still points to wiki)
  • there should be some easy way to tell solrconfig.xml nested structure where a new configuration needs to go (or focus on configoverlay and config API if it is fixed )

Kitchen sink config

• Is there a point to have a kitchen sink config that is basically a reference of field type definitions? That's where all the language variants could go.
• managed-schema points
  
  • having kitchen-sink default configset allows us to put some inline comments that make no sense in either production or learning schema as their files may get rewritten on use
  • may be write locked to clearly indicate it is not for real use
  • kitchen sink may be the only one with commented out analyzer lines

Lessons learned

From DIH Cleanup (

Jira
server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key SOLR-14783

)

...