While you set the max versions to 1, that is only enforced on major
compactions.
So re-inserting all the data will actually mean you have double the data
for some period of time. After a certain amount of time, a major
compaction will occur in the background, and at that point only 1
version would remain.
When that happened, you would still be left with 84 regions, but they'd
be half the size that they were after you re-inserted the data.
Make sense?
JG
[email protected] wrote:
Hello, i would appreciate explanations concerning the following point.
I have an indexed table of 25M rows (44 regions after initial data insertion).
The IndexedTable has been created with all the default attributes except that
all columns are set with MaxVersions to 1. Only one column is indexed.
After one whole update of the table with exactly the same data (a kind of
rewrite of the whole table), the table ended up with 84 regions. In my mind, I
should have stayed (more or less) with the same amount of region ?
Thanks in advance.
Guillaume Viland ([email protected])
FT/TGPF/OPF/PORTAIL/DOP Sophia Antipolis
*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it
immediately and inform the sender.
********************************
