There may be APIs which are introduced after 1.3 release and are not yet crystallized , may change by the time release happens.
As a rule of thumb any feature in the CHANGES.TXT post 1.3 is possible to change . But as long as you know what you are using you should be OK. It is not quite possible to ensure that everything works perfectly . but, what you can do is, what ever features you use , test them thoroughly . If you face issues report them back --Noble On Fri, Apr 17, 2009 at 12:28 PM, ristretto.rb <ristretto...@gmail.com> wrote: > I have built the trunk code as of Revision: 765826 and tried !tag=/!ex= > which is what I need to work. And IT WORKS! That's great. > > Now, is it unwise to release 1.4 into production for this feature (based > on my explanation below)? > > thanks > gene > > > > ---------- Forwarded message ---------- > From: ristretto.rb <ristretto...@gmail.com> > Date: Fri, Apr 17, 2009 at 11:16 AM > Subject: Advice on moving from 1.3 to 1.4-dev or trunk? > To: solr-user@lucene.apache.org > > > Hello, I'm using solr 1.3 with solr.py. We have a basic schema.xml, > nothing custom or out of the ordinary. > I need the following the feature from .... > http://svn.apache.org/repos/asf/lucene/solr/trunk/CHANGES.txt > > SOLR-911: Add support for multi-select faceting by allowing filters to be > tagged and facet commands to exclude certain filters. This patch also > added the ability to change the output key for facets in the response, and > optimized distributed faceting refinement by lowering parsing overhead and > by making requests and responses smaller. > > Since this requires 1.4, looks like I have to upgrade (or roll my own > solution that this feature provides.) > I'm looking for a bit of advice. I have looked through the bugs here > http://issues.apache.org/jira/browse/SOLR/fixforversion/12313351 > > 1. I would need to get the source for 1.4 and build it, right? No > release yet, eh? > 2. Any one using 1.4 in production without issue; is this wise? Or > should I wait? > 3. Will I need to make changes to my schema.xml to support my current > field set under 1.4? > 4. Do I need to reindex all my data? > > thanks > gene > -- --Noble Paul
