Current state: Under Discussion
- 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
Released: TBD (target 9.0)
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast). Confluence supports inline comments that can also be used.
As Solr has grown, the examples have become a mix of ancient documents, kitchen-sink additions with complicated - and often confusing - interplay of definitions, left-over configurations conflicting or out of sync with documentation. The "more info" links mostly point into legacy wiki that is two generations of redirects behind the current Reference Guide. Solutions were introduced with a fix-the-pain approach, that have also caused magic paths or pushed demonstration configurations into consolidated defaults. The new features are often not demonstrated as adding new example requires understanding the existing one.
The default configuration files have grown to the ridiculous sizes with a lot of that size being commented out out-of-date defaults and explanations (that should be or even already are in Reference Guide) or comments that will go away on first API-driven rewrite:
|as shipped||No comments||% reduction|
For solrconfig.xml, this bloated configuration is both confusing for people trying to identify significant configuration entries and potentially dangerous, such as remote streaming enabled by default until recently.
For managed-schema, all comments go away on first rewrite, making them completely unsuitable for any significant education purposes.
Similarly, our out-of-the-box filesystem layout has legacy/incremental setup different from our lessons learned in docker/service/3rd party/production layouts (logical locations for solr.in.sh, logs, pid, solr.home, live vs non-live directories). We also have magic syntax around creating examples that hides just enough internal machinery to make it very hard to run those examples multiple times and to understand when things go wrong. This will especially hit those that try to run multiple Solr instances on the same machine.
The examples themselves are out of date, demonstrate legacy features (techproducts) and sometimes (films) became less viable because the external source of interesting data has disappeared. The examples are also not providing enough records/fields to show advanced Solr capabilities or even basic nested ones. One example (schemaless) is no longer different from a standard core created with one or two commands, apart from the behind-the-scenes logging magic that will not work outside of the example directory.
Some of the other examples are going away as part of other initiatives (DIH). Some other examples demonstrate the features that we strongly do not recommend in production and spend a lot of time advising people on the mailing list to undo what they learned from our own default schemas (Tika integration, schemaless mode as default chain).
Finally, the recent attempt to do getting started guide with initial focus on the cloud setup may have made the comprehension of what Solr is actually doing more complex and - again, because of magical nature of examples directory - not easily reproducible.
All together, this makes new users confused about getting examples running, understanding what they are actually running, learning about latest features of Solr and knowing how they can apply that learning from example configurations to their own. They are also going into production with kitchen-sink configurations that everybody is afraid to modify.
This will affect all the examples. It may affect some of the directories, startup scripts, documentation, and tests.
- Go through the default configuration files line by line.
- Ensure that any documentation and explanation not yet in the Reference Guide are moved there. Delete any significant passage and replace them with Ref Guide links to ensure a single-source of truth ( - SOLR-11875Getting issue details... STATUS - SOLR-14841Getting issue details... STATUS - SOLR-14834Getting issue details... STATUS )
- Delete any default blocks that do not use parameter substitutions and point them to RefGuide for the section and to the API to get the real defaults as appropriate
- Delete legacy sections that 'no longer work' (e.g. jmx, possibly EditorialMarkerFactory)
- Delete workaround explanations for those migration from Solr prior to Solr 7? (Document them on RefGuide ?)
- Review directory layouts current state
- Clarify naming for locations of:
- Static O/S global part of running solr
- Writable O/S global part of running solr (only pid file or more?)
- Server/Node level information (start.in.sh?, logs? configsets? solr.xml) - there may be several of this on a physical server, such as in cloud example. Or put all those in solr.home and have cores one level lower under coreRootDirectory (in solr.xml, but see - SOLR-14097Getting issue details... STATUS
- Collection/Core level information (core.properties)
- Individual directories per core (conf, data) - some of these already can be in other locations
- Refactor example directory and associated commands to reduce magic
- This mainly affects log configuration and logging directory locations and figuring out what is the directory above solr home
- May also involve exploration about configsets and environmental override directories
- Create new examples (
SOLR-10329Getting issue details...
SOLR-11352Getting issue details...
- Create a base learning config that is either based on default or has even simpler its own ( - SOLR-13652Getting issue details... STATUS )
- Setup new dataset (https://www.fakenamegenerator.com can generate 100k records with many interesting fields under CC license (https://creativecommons.org/licenses/by-sa/3.0/us/, similar to CC license used by films example already)
- Split records into different formats to demonstrate XML, CSV, multiple JSONs, nested records, etc
- Create a number of additive configurations+examples, that augment base configuration to demonstrate specific features with point precision
- Move non-essential schema definitions (e.g. languages) from default into alternative schema (new kitchen-sink). Should it be copy/paste XML or API commands, To Be Explored ( - SOLR-11033Getting issue details... STATUS )
- Update documentation to use new examples to demonstrate features that used to use older configsets
- Use short names for analyzer/filter/tokenizer wherever possible ( - SOLR-13691Getting issue details... STATUS ) - make sure they are easily discoverable in documentation as well
- Rewrite Getting Started guide that focuses on simplest path through
- Start from standalone mode
- Explain what is happening with cross-references for more details (teach troubleshooting skills early)
- Use API as much as possible, but not at a cost of readability/comprehension
- Demonstrate recent APIs/features
- Build up to the cloud example
- Bigger changes that needs further discussion
- Delete ALL DIH examples in bulk - DONE ( - SOLR-14066Getting issue details... STATUS , - SOLR-14783Getting issue details... STATUS )
- Delete Tika configuration and refer to the manual for configuration and warning ( - SOLR-13973Getting issue details... STATUS )
- Move schemaless mode into learning chain ( - SOLR-14701Getting issue details... STATUS - SOLR-11741Getting issue details... STATUS )
- Delete (refactor) techproducts example and its files (but what about tests?)
- Delete Velocity example ( - SOLR-14065Getting issue details... STATUS )
- V2 vs V1 API for examples (V2 is not available for standalone mode in 8.6.1)
- post tool vs curl
- Interplay with Admin UI changes in progress (e.g. how much to leverage/demonstrate it)
- Neither default nor techproducts are realistic production schemes - a whole separate but related discussion (Jira exists?)
- It seems that even though Velocity/DIH/others have been deprecated, they have not actually been removed from code/documentation for 9.0 yet. Are there Jiras for that already?
- Other cleanup
Compatibility, Deprecation, and Migration Plan
- Existing users will only be affected when they look at examples again to learn additional features
- The directory locations may change, but possibly in a very minor way. If 3rd party tools hardcode paths, this may need a call-out
- Tests use both default and techproducts scheme. They would need to be migrated
This proposal should not affect or possibly improve the security.
All existing tests should run. Additional tests may be needed?
The current status is broken in 100 different small ways. The discussions and attempts to fix them are happening in parallel efforts, but they do it from a functional (rather than critical path) point of view. Being separate efforts, their priority and impact is often not fully appreciated without a higher-level critical path discussion.
It may be possible to create just a minimal learning schema and/or a couple of examples, but this would still not address that, once the person tries to add new functionality or test new features, they are not supported. Nor will it address kitchen-sink production deploys.
Related previous explorations and feature tests
Learning vs Production vs kitchen sink setup
- 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:
- managed-schema should be minimal to allow users to include what is actually needed
- 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
- To get DIH to work, we had to add permissions into solr/server/etc/security.policy, which is very low-level. Is it going to be an issue? Do we need a way for packages to explain such needs on install? Are there more examples like that? Also, it is great that somebody commented it properly, otherwise it would just be sitting there forever