flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10657) TPCHQuery3 fail with IllegalAccessException
Date Wed, 24 Oct 2018 09:40:00 GMT

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

ASF GitHub Bot commented on FLINK-10657:
----------------------------------------

zentol commented on issue #6912: [FLINK-10657] TPCHQuery3 fail with IllegalAccessException
URL: https://github.com/apache/flink/pull/6912#issuecomment-432587365
 
 
   ```00:58:26.665 [INFO] There is 1 error reported by Checkstyle 8.9 with /tools/maven/checkstyle.xml
ruleset.
   00:58:26.666 [ERROR] src/main/java/org/apache/flink/examples/java/relational/TPCHQuery3.java:[241]
(javadoc) JavadocType: Missing a Javadoc comment.
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> TPCHQuery3 fail with IllegalAccessException
> -------------------------------------------
>
>                 Key: FLINK-10657
>                 URL: https://issues.apache.org/jira/browse/FLINK-10657
>             Project: Flink
>          Issue Type: Bug
>          Components: E2E Tests
>            Reporter: JIN SUN
>            Assignee: JIN SUN
>            Priority: Trivial
>              Labels: easy-fix, pull-request-available
>             Fix For: 1.7.0
>
>
> Similar with [FLINK-7998|https://issues.apache.org/jira/browse/FLINK-7998], ShoppingPriorityItem in
example TPCHQuery3.java are set to private. This causes an IllegalAccessException exception
because of reflection check in dynamic class instantiation. Making them public resolves the
problem 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message