I agree, it is a bad idea. Solr is missing nearly everything you want in a repository, because it is not designed to be a repository.
Does not have: * access control * transactions * transactional backup * dump and load * schema migration * versioning And so on. Also, I’m glad to share a one-line curl command that will delete all the documents in your collection. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Nov 17, 2016, at 1:20 AM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > > I've heard of people doing it but it is not recommended. > > One of the biggest implementation breakthroughs is that - after the > initial learning curve - you will start mapping your input data to > signals. Those signals will not look very much like your original data > and therefore are not terribly suitable to be the source of it. > > We are talking copyFields, UpdateRequestProcessor pre-processing, > fields that are not stored, nested documents flattening, > denormalization, etc. Getting back from that to original shape of data > is painful. > > Regards, > Alex. > ---- > Solr Example reading group is starting November 2016, join us at > http://j.mp/SolrERG > Newsletter and resources for Solr beginners and intermediates: > http://www.solr-start.com/ > > > On 17 November 2016 at 18:46, Dorian Hoxha <dorian.ho...@gmail.com> wrote: >> Hi, >> >> Anyone use solr for source-of-data with no `normal` db (of course with >> normal backups/replication) ? >> >> Are there any drawbacks ? >> >> Thank You
