Uploaded image for project: 'CarbonData'
  1. CarbonData
  2. CARBONDATA-4162

Leverage Secondary Index till segment level with SI as datamap and SI with plan rewrite

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.2.0
    • None
    • None

    Description

      Background:

      Secondary index tables are created as indexes and managed as child tables internally by Carbondata. In the existing architecture, if the parent(main) table and SI table don’t
      have the same valid segments then we disable the SI table. And then from the
      next query onwards, we scan and prune only the parent table until we trigger
      the next load or REINDEX command (as these commands will make the
      parent and SI table segments in sync). Because of this, queries take more
      time to give the result when SI is disabled.

      Proposed Solution:
      We are planning to leverage SI till the segment level. It means at place
      of disabling the SI table(when parent and child table segments are not in sync)
      we will do pruning on SI tables for all the valid segments(segments with status
      success, marked for update and load partial success) and the rest of the
      segments will be pruned by the parent table.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            nihal Nihal kumar ojha
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 4h 20m
                4h 20m

                Slack

                  Issue deployment