You can still give an id to each value on the application side if you want to avoid repeating values. Otherwise, even without doing anything, things should not be too bad thanks to stored fields compression.
Le mar. 15 mars 2016 à 16:56, Erick Erickson <erickerick...@gmail.com> a écrit : > In a word, "no". When you set stored="true", Solr (well > actually Lucene) puts a compressed verbatim copy on disk. > > "Disk space is cheap" is the usual response here ;) > > Best, > Erick > > On Tue, Mar 15, 2016 at 8:35 AM, Andreas Sewe > <andreas.s...@codetrails.com> wrote: > > Hi, > > > > I have an index in which each document has an indexed & stored "kind" > > StringField, which has a small set of possible values (about 10). > > > > Alas, Lucene (5.2.1) stores these field values over and over again, > > which seems wasteful. Is there a way to avoid this, while still having > > the fields' value available as stored? > > > > Best wishes, > > > > Andreas > > > > -- > > Codetrails GmbH > > The knowledge transfer company > > > > Robert-Bosch-Str. 7, 64293 Darmstadt > > Phone: +49-6151-276-7092 > > Mobile: +49-170-811-3791 > > http://www.codetrails.com/ > > > > Managing Director: Dr. Marcel Bruch > > Handelsregister: Darmstadt HRB 91940 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
