Thanks for the reply. Actually in our case we want the timestamp to be populated locally on each node in the SolrCloud cluster. We want to see if there is any delay in the document being distributed within the cluster. Just want to confirm that the timestamp can be use for that purpose.
Bill On Sat, May 9, 2015 at 11:37 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 5/9/2015 8:41 PM, Bill Au wrote: > > Is the behavior of document being indexed independently on each node in a > > SolrCloud cluster new in 5.x or is that true in 4.x also? > > > > If the document is indexed independently on each node, then if I query > the > > document from each node directly, a timestamp could hold different values > > since the document is indexed independently, right? > > > > <field name="timestamp" type="date" indexed="true" stored="true" > > default="NOW" /> > > SolrCloud has had that behavior from day one, when it was released in > version 4.0. You are correct that it can result in a different > timestamp on each replica if the default comes from schema.xml. > > I am pretty sure that the solution for this problem is to set up an > update processor chain that includes TimestampUpdateProcessorFactory to > populate the timestamp field before the document is distributed to each > replica. > > https://cwiki.apache.org/confluence/display/solr/Update+Request+Processors > > Thanks, > Shawn > >
