First off, the internal Lucene doc ID has never been stable as long as any segment merging of whatever style was going on, don't quite know where you're getting that idea.
It sounds like what you're really looking for is to export complete result sets to "do something with them later". That's what the export capability was built for (Solr 4.10 and later). See: https://cwiki.apache.org/confluence/display/solr/Exporting+Result+Sets Just make your Solr ID (<uniqueKey> or whatever) a DV field and export.. Best, Erick On Wed, Oct 7, 2015 at 7:32 PM, Trejkaz <trej...@trypticon.org> wrote: > On Thu, Oct 8, 2015 at 1:16 PM, Erick Erickson <erickerick...@gmail.com> > wrote: >> This may be an "XY" problem, you're asking how to do X thinking >> it will solve Y without telling us what Y is. >> >> What do you want to _do_ with the DV values you look up for each hit? > > Keep them around as the ID to use to look up information later. i.e., > what we used to do with the doc ID before Lucene decided the doc ID > wouldn't be stable. > > e.g., the search happens at some point, and then later you want to > render a row of a table, so you want to fetch the document. But you > can't use the doc ID to do that, so we use another ID which we map > back to the doc ID once we have a reader for that operation. > > TX > > --------------------------------------------------------------------- > 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
