Github user paul-rogers commented on a diff in the pull request:
    --- Diff: 
    @@ -0,0 +1,91 @@
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.drill.exec.physical.rowSet;
    +import org.apache.drill.exec.physical.rowSet.impl.MaterializedSchema;
    +import org.apache.drill.exec.record.BatchSchema;
    +import org.apache.drill.exec.record.MaterializedField;
    + * Defines the schema of a tuple: either the top-level row or a nested
    + * "map" (really structure). A schema is a collection of columns (backed
    + * by vectors in the loader itself.) Columns are accessible by name or
    + * index. New columns may be added at any time; the new column takes the
    + * next available index.
    + */
    +public interface TupleSchema {
    +  public interface TupleColumnSchema {
    +    MaterializedField schema();
    +    /**
    +     * Report if a column is selected.
    +     * @param colIndex index of the column to check
    +     * @return true if the column is selected (data is collected),
    +     * false if the column is unselected (data is discarded)
    +     */
    +    boolean isSelected();
    --- End diff --
    Changed. Should be "isProjected". This means that the column (that, in this 
case, exists in a table), is projected into the result set. Assume a table has 
the schema
    (a, b, c)
    But the query is:
    ```SELECT c, a FROM ...```
    Then a and c are "projected", b is unprojected.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to