> Is anyone on this list using schemaless mode in production or have you tried > to?
Schemaless mode is one of a group of Solr features present for convenience but not intended for production usage. It's in the same boat as "bin/post", and SolrCell, and others. These features do cause headaches when users ignore the documented restrictions and use them for more than prototyping. But at the same time they're super valuable for these sort of demo-ing or getting-started use cases. An easy getting-started experience is important, and schemaless et al serve a mostly positive role in that. I think we'd better serve our users if we left schemaless in/undeprecated, and instead focused on making it harder to (unknowingly) use them in ways contrary to community recommendations. Add louder warnings in the documentation (where not already present). Add warnings to the Solr logs the first time these features are used. Disable them by default (where that makes sense). Taken to the extreme, we could even add a section into Solr's response that lists non-production features used in serving a given request. There are lots of ways to address the "feature X is trappy" problem without removing X together. On Mon, Aug 3, 2020 at 11:33 AM Marcus Eagan <[email protected]> wrote: > > Community, > > There are many of us that have had to deal with the pain of managing the > schemaless mode of operation in Solr. I'm curious to get others thoughts > about how well it is working for them and if they would like to continue to > use it. > > I for one don't think Schemaless works as intended and favor deprecating it > and replacing it with some more usable but I am sure others have thoughts > here. > > Is anyone on this list using schemaless mode in production or have you tried > to? > > A preliminary discussion has occurred in this Jira ticket: > https://issues.apache.org/jira/browse/SOLR-14701 > > Thank you all, > > Marcus Eagan > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
