[jira] [Commented] (DRILL-7446) Eclipse compilation issue in AbstractParquetGroupScan

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975926#comment-16975926 ] 

ASF GitHub Bot commented on DRILL-7446:
---------------------------------------

paul-rogers commented on pull request #1900: DRILL-7446: Fix Eclipse compilation issue in AbstractParquetGroupScan
URL: https://github.com/apache/drill/pull/1900
 
 
   Adds dummy parameter types to several files to avoid compilation errors
   when loading Drill into Eclipse.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Eclipse compilation issue in AbstractParquetGroupScan
> -----------------------------------------------------
>
>                 Key: DRILL-7446
>                 URL: https://issues.apache.org/jira/browse/DRILL-7446
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Minor
>
> When the recent master branch is loaded in Eclipse, we get a compiler error in {{AbstractParquetGroupScan}}:
> {noformat}
> The method getFiltered(OptionManager, FilterPredicate) from the type AbstractGroupScanWithMetadata.GroupScanWithMetadataFilterer is not visible	AbstractParquetGroupScan.java	/drill-java-exec/src/main/java/org/apache/drill/exec/store/parquet	line 242	Java Problem
> Type mismatch: cannot convert from AbstractGroupScanWithMetadata.GroupScanWithMetadataFilterer to AbstractParquetGroupScan.RowGroupScanFilterer	AbstractParquetGroupScan.java	/drill-java-exec/src/main/java/org/apache/drill/exec/store/parquet	line 237	Java Problem
> {noformat}
> The issue appears to be due to using the raw type rather than using parameters with the type.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)