Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-57

Select fields not pushed down to rules when using a View definition

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Granted I don't understand this, but I'm filing a bug because I've sat here for days and can't figure out a way around it.

      If you use the MongoDB plugin it uses a View in the definition file. That view is then used during the query optimization process and the ProjectRel that are generated use the Select statement from the View when matching the rules.

      I would like to select only the fields used from Mongo rather than the whole table, this will minimise data transfer and enable Mongo Aggregation stuff, but currently all the fields are returned and I can't find a way to create a rule that is processed with just the fields selected.

      -Edit-

      Also, if I put break points into optiq-csv, the ProjectRels created there have the correct number of fields

      ---------------- Imported from GitHub ----------------
      Url: https://github.com/julianhyde/optiq/issues/57
      Created by: buggtb
      Labels:
      Created at: Tue Oct 01 12:02:47 CEST 2013
      State: closed

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              github-import GitHub Import
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: