It's possible to get near real-time adds and updates (every two
minutes in our case) with a multi-shard setup, if you have a shard
dedicated to new content and have the right combination of unique
identifiers on your data. I'll respond off-list with a full description
of my setup.
On 7/9/2
ltime-Batch-indexing-tp952293p955442.html
Sent from the Solr - User mailing list archive at Nabble.com.
Replication does not transfer files that already exist on the slave and
have the same metadata (size, last modified, etc) as the master. As far
as deleting files, it will only do so if they do not exist on the master.
In most cases, the only way that it would delete and copy the entire
index
size as
master after replication) so thought that SOLR just deletes the slave index
and then moves all the files from master..
Again, thanks for your help
Thanks,
BB
--
View this message in context:
http://lucene.472066.n3.nabble.com/Realtime-Batch-indexing-tp952293p953590.html
Sent from the
I am planning to implement the 2nd approach as we need to make
> changes to the UI code if we are going for shards.
>
> Thanks,
> BB
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Realtime-Batch-indexing-tp952293p953410.html
> Sent from
shards.
Thanks,
BB
--
View this message in context:
http://lucene.472066.n3.nabble.com/Realtime-Batch-indexing-tp952293p953410.html
Sent from the Solr - User mailing list archive at Nabble.com.
y usung
> /update handler some of the attributes are getting lost in the existing
> index. Any reason why this might be happening?
>
>
> Any help / suggestions would be of great help
>
> Thanks,
> BB
>
>
>
>
>
> --
> View this message in context:
>
getting lost in the existing
index. Any reason why this might be happening?
Any help / suggestions would be of great help
Thanks,
BB
--
View this message in context:
http://lucene.472066.n3.nabble.com/Realtime-Batch-indexing-tp952293p952293.html
Sent from the Solr - User mailing list
