Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-1297

Control distribution order on dbroot / segment level

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Do
    • None
    • N/A
    • N/A
    • None

    Description

      Usual the distribution of storing data is not under control of the user.

      Data will be loaded in the order of loading.
      The only possiblitiy to control a bit, is to use mode 2 or 3 with cpimport for a certain PM.

      Sometimes it can make sense to have control over the distribution process.

      Similar to
      -P List of PMs ex: -P 1,2,3. Default is all PMs.

      -D  List if DBroot ex -D 1,2,3 Default is all DBroots. If a certain PM is not defined, PM1 will be  used.
      		 
       
      		 
      -S List of Segments ex -S 1,2,3 Default is all Segments. If a certain PM is not defined, PM1 will be  used.

      The same options should be possible for the bulk API
      createBulkInsert(const std::string &db, const
      std::string &table,
      uint8_t
      mode, uint16_t pm)

      Add uint16_t dbroot  and uint16_t segment
      		 
       
      		 
      createBulkInsert(const std::string &db, const
      		 
      std::string &table,
      		 
      uint8_t
      		 
      mode, uint16_t pm, uint16_t dbroot, uint_16_t segment)

      dbroot = 0 no preference. Otherwise the only the handed over dbroot will be filled.
      If pm = 0, PM1 will be choosen.

      segment = 0 no preference. Otherwise the only the handed over segment will be filled.
      If pm = 0, PM1 will be choosen.

      If batch data is greater then free space in specified available, the next in number will be taken.

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MCOL-3579 Manually set distribution key

          • Major - Major loss of function.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MCOL-4217 ColumnStore Partitioning

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. MCOL-5866 controlled redestribution

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. MCOL-6146 add mode 2 and 3 to CALL columnstore_info.load_from_s3

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. MDEV-37450 add mode 2 and 3 to CALL columnstore_info.load_from_s3

          • Major - Major loss of function.
          • Closed

          Activity

            People

              toddstoffel Todd Stoffel (Inactive)
              Richard Richard Stracke
              Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.