I am here on lucene as a user since the project started, even before solr came to life, many many years. And I was always using trunk version for pretty big customers, and *never* experienced some serious problems. The worst thing that can happen is to notice bug somewhere, and if you have some reasonable testing for your product, you will see it quickly. But, with this community, *you will definitely not have wait long top get it fixed*. Not only they will fix it, they will thank you for bringing it up!
I can, as an old user, 100 % vouch what Robert said below. Simply, just go for it, test you application a bit and make your users happy. On Wed, Mar 7, 2012 at 5:55 PM, Robert Muir <rcm...@gmail.com> wrote: > On Wed, Mar 7, 2012 at 11:47 AM, Dirceu Vieira <dirceu...@gmail.com> wrote: >> Hi All, >> >> Has anybody started using Solr 4.0 in production environments? Is it stable >> enough? >> I'm planning to create a proof of concept using solr 4.0, we have some >> projects that will gain a lot with features such as near real time search, >> joins and others, that are available only on version 4. >> >> Is it too risky to think of using it right now? >> What are your thoughts and experiences with that? >> > > In general, we try to keep our 'trunk' (slated to be 4.0) in very > stable condition. > > Really, it should be 'ready-to-release' at any time, of course 4.0 has > had many drastic changes: both at the Lucene and Solr level. > > Before deciding what is stable, you should define stability: is it: > * api stability: will i be able to upgrade to a more recent snapshot > of 4.0 without drastic changes to my app? > * index format stability: will i be able to upgrade to a more recent > snapshot of 4.0 without re-indexing? > * correctness: is 4.0 dangerous in some way that it has many bugs > since much of the code is new? > > I think you should limit your concerns to only the first 2 items, as > far as correctness, just look at the tests. For any open source > project, you can easily judge its quality by its tests: this is a > fact. > > For lucene/solr the testing strategy, in my opinion, goes above and > beyond many other projects: for example random testing: > http://www.lucidimagination.com/devzone/events/conferences/ApacheLuceneEurocon2011_presentations#dawid_weiss > > and the new solr cloud functionality also adds the similar chaosmonkey > concept on top of this already. > > If you are worried about bugs, is a lucene/solr trunk snapshot less > reliable than even a released version of alternative software? its an > interesting question. look at their tests. > > -- > lucidimagination.com
