I didn't mean to imply that _you'd_ changed things, the _defaults_ may have changed. So the "string" fieldType may be defined with docValues="true" in your new schema and "false" in your old schema without you intentionally changing anything at _all_.....
That's why the LukeRequestHandler will help, because it tells you what's _there_ regardless of how it got there... Best, Erick On Fri, Feb 16, 2018 at 1:37 PM, Howe, David <david.h...@auspost.com.au> wrote: > > Hi Erick, > > I'm 99% sure that I haven't changed the field types between the two snapshots > as all of my test runs are completely scripted and build a new Solr server > from scratch (both the virtual machine and the Solr software). I can diff > the scripts between two runs to make sure I haven't accidentally changed > anything, and I have done this. > > The only difference is that I added docValues=false to all of the fields that > are indexed=false and stored=true in the run that is smaller. I had tested > this previously with the data in the order that makes the index larger and it > only made a minor difference (see one of my previous posts). Unfortunately, > I hadn't added the change to log the file sizes when I did that run, but it > definitely didn't fix the problem. > > I need to try and get my project back on track now, so I will concentrate on > the "fix" that I have and perhaps re-run some other scenarios when I have > more time. > > Thanks again for your help. > > Regards, > > David > > David Howe > Java Domain Architect > Postal Systems > Level 16, 111 Bourke Street Melbourne VIC 3000 > > T 0391067904 > > M 0424036591 > > E david.h...@auspost.com.au > > W auspost.com.au > W startrack.com.au > > Australia Post is committed to providing our customers with excellent > service. If we can assist you in any way please telephone 13 13 18 or visit > our website. > > The information contained in this email communication may be proprietary, > confidential or legally professionally privileged. It is intended exclusively > for the individual or entity to which it is addressed. You should only read, > disclose, re-transmit, copy, distribute, act in reliance on or commercialise > the information if you are authorised to do so. Australia Post does not > represent, warrant or guarantee that the integrity of this email > communication has been maintained nor that the communication is free of > errors, virus or interference. > > If you are not the addressee or intended recipient please notify us by > replying direct to the sender and then destroy any electronic or paper copy > of this message. Any views expressed in this email communication are taken to > be those of the individual sender, except where the sender specifically > attributes those views to Australia Post and is authorised to do so. > > Please consider the environment before printing this email.
