Details
-
Wish
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
A while back, I was tasked at my day job to brainstorm & design some "smarter field types" in Solr. In particular to think about:
- How to simplify some of the "special things" people have to know about Solr behavior when creating their schemas
- How to reduce the number of situations where users have to copy/clone one "logical field" into multiple "schema felds in order to meet diff use cases
The main result of this thought excercise is a handful of usecases/goals that people seem to have - many of which are already tracked in existing jiras - along with a high level design/roadmap of potential solutions for these goals that can be implemented incrementally to leverage some common changes (and what those changes might look like).
My intention is to use this jira as a place to share these ideas for broader community discussion, and as a central linkage point for the related jiras. (details to follow in a very looooooong comment)
NOTE: I am not (at this point) personally committing to following through on implementing every aspect of these ideas 
