Hi Prem,
Using HTTPClient to establish connection and also i am *validating* whether
> the particular document is *available* in collection or not and after that
> updating the document.
Why do you need to validate the particular document before updating.
Atomic updates either update the
On 12/12/2019 10:00 PM, Prem wrote:
I am trying to partially update of 50M data in a collection from CSV using
Atomic script(solrj).But it is taking 2 hrs for 1M records.is there anyway i
can speed up my update.
How many documents are you sending in one request?
Using HTTPClient to establish
One needs to see the code or get more insights on your design. Do you reuse the
HTTPClient or do you create for every request a new one?
How often do you commit?
Do you do parallel updates from the client (multiple threads?).
> Am 13.12.2019 um 06:56 schrieb Prem :
>
> I am trying to partially
I am trying to partially update of 50M data in a collection from CSV using
Atomic script(solrj).But it is taking 2 hrs for 1M records.is there anyway i
can speed up my update.
Using HTTPClient to establish connection and also i am validating whether
the particular document is available in
Hi Andrea,
Thanks for the explanation on that. I ended up doing that, getting and
setting an UUID on the Java code.
On 08/08/2015 03:19 AM, Andrea Gazzarini wrote:
Hi Henrique,
I don't believe there's an easy way to do that.
As you noticed, the SolrInputDocument is not an I/O param, that
Hi Henrique,
I don't believe there's an easy way to do that.
As you noticed, the SolrInputDocument is not an I/O param, that is, it is
not sent back once data has been indexed and this is good, because here
you're sending just one document, but imagine what could happen if you do a
bulk
Hello all,
I am using SolrJ to do a index update on one of my collections. This
collection has a uniqueKey id field:
fields
field name=id type=string indexed=true stored=true/
field name=_version_ type=long indexed=true stored=true/
field name=name type=string indexed=true
