If I turn off automatic indexing and refreshing, and continually execute
partial updates on the same document (say 100 times), do the updates change
the same record in the transaction log or will it create 100 changes? The
reason I'm curious is because when I ask ES to index (or refresh) after a
batch of partial updates, will it try to index the same document 100 times
or just once? So efficiency seems to be important here.
My data structure is a Customer with lots of Transactions with each record
containing a date, description, and dollar amount. I would like to see if
a denormalized data structure works here by keeping a list of transactions
on the customer, then updating new transactions into the same customer
record. But this would be very inefficient if the document would have to be
reindexed as many times as the number of incoming partial updates. I'm
hoping I can control this by turning off indexing/refreshing and let ES
update the same record in the Transaction log. I understand that Lucene
has immutable records, but that does not really mean that the Transaction
log has to have immutability, right?
Thanks for any feedback/thoughts!!
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fa6ba2b6-4e41-4470-811c-08e578c8c596%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.