Posted by
akashrn5 on
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/DISCUSSION-Merge-index-property-and-operations-improvement-tp103178p103440.html
Hi david,
Thanks for reply
a) remove mergeIndex property and event listener, add mergeIndex as a part
of loading/compaction transaction.
==> yes, this can be done, as already discussed.
b) if the merging index failed, loading/compaction should fail directly.
==> Agree to this, same as replied to ajantha
c) keep merge_index command and mark it deprecated.
for a new table, maybe it will do nothing.
for an old table, maybe we need to tolerate the probable query issue
(not found index files).
It could be a deprecated feature in the future.
===> for new table we can follow similar to what i replied to ajantha, and
old tables we still need
and since we are avoiding to delete index files immediately for old tables,
we can avoid issue i think.
As you said, we can complete deprecate after sometime,
b). At the end of loading, retrying to finish index merging or
tablestatus update is a good suggestion.
===> Do you mean, retry count for table status updation and merge index
should be more?
Regards,
Akash
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/