Hi Nihal,
I appreciate the design but I don’t want to implement features with out
proper segment interfacing in place. With out segment refactoring if you
try to implement this type of features will make the code more dirty.
Once we bring the proper segment interfacing and transaction management in
place we can make parallel executions simpler and less error prone.
Regards,
Ravindra.
On Mon, 14 Sep 2020 at 10:31 PM, Nihal <
[hidden email]> wrote:
> Dear community,
>
>
>
> This mail is regarding the parallel compaction and update.
>
> Current behavior: Currently we are not supporting concurrent compaction and
>
> update because It may cause data inconsistency or incorrect result.
>
> We take the compaction and update lock before any of these operations.
>
> Because of this behavior if one is executing then others have to wait and
>
> sometimes this waiting time is very long.
>
>
>
> To come out with this problem we are planning to support parallel
> compaction
>
> and update. And here I have proposed one of the solutions to implement this
>
> feature.
>
> Paraller_Compaction_And_Update.pdf
>
> <
>
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/file/t443/Paraller_Compaction_And_Update.pdf>
>
>
> Please go through this solution document and provide your input if this
>
> approach is ok or any drawback is there.
>
>
>
>
>
> Thanks & Regards
>
> Nihal kumar ojha
>
>
>
>
>
>
>
> --
>
> Sent from:
>
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/>
> --
Thanks & Regards,
Ravi
Locked
