Posted by
akashrn5 on
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/DISCUSSION-Merge-index-property-and-operations-improvement-tp103178p103427.html
Hi Ajantha,
Thanks for the reply, please find my comments
*a) and b)* agree to the point that, no need to make load success if the
merge index fails, we can fail the load
and update the status and segment file only after merge index to avoid many
reliability and concurrent and cache issues.
*c) for your point C*, please check my point 2, i have already mentioned
that the alter can be allowed on legacy stores, for new tables i was
planning to keep in case of update, but now since updated data is written to
new segment, that scenario will also be not required.
So we can agree on point that, if user triggers for new tables, we can check
and give warn message and exit gracefully.
*d) for your point D*, as i said in my point 1, we can deprecate that
property and hide from user and keep only for developer purpose for any
issue analysis or debug.
I think these above conclusions can be finalized.
Thanks for the suggestions
Regards,
Akash R
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/