creation order. Does anyone have knowledge and experience with the
internals of the Lucene _docid_ field?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-x-auto-increment-sequence-counter-functionality-tp4045125p4046137.html
Sent from the Solr - User mailing list archive at Nabble.com.
mychain
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-x-auto-increment-sequence-counter-functionality-tp4045125p4045725.html
Sent from the Solr - User mailing list archive at Nabble.com.
ow in Solr, the only
> > *free* uniqueness check is with the "id" declaration
> > in "schema.xml". Are there other options that I should be considering?
> >
> >
> >
> > --
> > View this message in context:
> > http://lucene.472066.
idering?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-4-x-auto-increment-sequence-counter-functionality-tp4045125p4045239.html
> Sent from the Solr - User mailing list archive at Nabble.com.
sidering?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-x-auto-increment-sequence-counter-functionality-tp4045125p4045239.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
How about a custom UpdateRequestProcessor that uses milliseconds or even
nanoseconds and stores them in some field? If that is enough resolution
and you still want to avoid collision, append a random letter/string/number
to it, a la _.
Otis
--
Solr & ElasticSearch Support
http://sematext.com