[ https://issues.apache.org/jira/browse/CARBONDATA-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Venkata Ramana G updated CARBONDATA-2827: ----------------------------------------- Attachment: Segment Status Management interface design_V1_Ramana_reviewed.docx > 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 Status Management interface design_V1.docx, > Segment Status Management interface design_V1_Ramana_reviewed.docx > > > 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 (v7.6.3#76005)