Thanks Tony, but I think Rick's answer is different. He asked me to start with "new version of solrconfig.xml".
@Rick I have been doing what Tony said (copied my config to new core, and fixed each error or warning). Is there some mega solrconfig.xml which which you recommended me to start from? Nawab On Fri, Jun 2, 2017 at 12:15 PM, Tony Wang <tw...@xactlycorp.com> wrote: > Hi Nawab, > We did exact the same way like Rick recommended. When you apply your > change from your old configs on top of the originals, it will give you the > errors for incompatible settings. For an example of > "text_general_edge_ngram" fieldType setting, side="front" is no longer > valid attributes. > > Tony > > > On Wed, May 31, 2017 at 3:53 PM, Rick Leir <rl...@leirtech.com> wrote: > > > Hi Nawab > > The recommended way is to use the new version of solrconfig.xml and apply > > your modifications to it. You will want to go through it looking for > > developments that would affect you. > > Cheers > > Rick > > > > On May 31, 2017 3:45:58 PM EDT, Nawab Zada Asad Iqbal <khi...@gmail.com> > > wrote: > > >Hi, > > > > > >I am upgrading 4.5.0 to latest stable bits and wondering what will be > > >the > > >quickest way to find out any obsolete or deprecated settings in config > > >files? > > >If I run the latest server with my old config (solr.xml, > > >solrconfig.xml, > > >schema.xml) files, will it warn for deprecated/less-optimal values? > > > > > > > > >Thanks > > >Nawab > > > > -- > > Sorry for being brief. Alternate email is rickleir at yahoo dot com > > -- > > > [image: What's New with Xactly] <http://www.xactlycorp.com/email-click/> > > <https://www.nyse.com/quote/XNYS:XTLY> [image: LinkedIn] > <https://www.linkedin.com/company/xactly-corporation> [image: Twitter] > <https://twitter.com/Xactly> [image: Facebook] > <https://www.facebook.com/XactlyCorp> [image: YouTube] > <http://www.youtube.com/xactlycorporation> >
