[
https://issues.apache.org/jira/browse/CARBONDATA-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327125#comment-17327125
]
Ajantha Bhat commented on CARBONDATA-2827:
------------------------------------------
will be handled as part of *CARBONDATA-4171*
*https://issues.apache.org/jira/browse/CARBONDATA-4171*
> Refactor Segment Status Manager Interface
> -----------------------------------------
>
> Key: CARBONDATA-2827
> URL: https://issues.apache.org/jira/browse/CARBONDATA-2827
> Project: CarbonData
> Issue Type: Improvement
> Reporter: Ravindra Pesala
> Priority: Major
> Attachments: Segment Management interface design_V3.pdf, Segment
> Status Management interface design_V1.docx, Segment Status Management
> interface design_V1_Ramana_reviewed.docx, Segment Status Management interface
> design_V2.pdf
>
>
> Carbon uses tablestatus file to record segment status and details of each
> segment during each load. This tablestatus enables carbon to support
> concurrent loads and reads without data inconsistency or corruption.
> So it is very important feature of carbondata and we should have clean
> interfaces to maintain it. Current tablestatus updation is shattered to
> multiple places and there is no clean interface, so I am proposing to
> refactor current SegmentStatusManager interface and bringing all tablestatus
> operations to single interface.
> This new interface allows to add table status to any other storage like DB.
> This is needed for S3 type object stores as these are eventually consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
