Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-2281 Support Phoenix running on Drill
  3. PHOENIX-2282

Define serialization of sub scan for Drill to leverage Phoenix

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      I think there are two pieces:

      • the separate parallel unit (always a Scan for Phoenix)
      • the reader class to instantiate that will interpret the results.

      It be pretty easy to write code that combines multiple Scans together too, based on the start row/end row in the case that Phoenix over-parallelizes due to guideposts.

      FWIW, even the Phoenix DML (UPSERT SELECT and DELETE) fit this model of a Scan plus the reader code which would push the data back out for the writes (see UpsertCompiler and DeleteCompiler).

      Attachments

        Activity

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

          People

            jnadeau Jacques Nadeau
            jamestaylor James R. Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment