You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Vinoth Chandar (Jira)" <ji...@apache.org> on 2019/11/26 10:45:00 UTC
[jira] [Commented] (HUDI-363) Refactor codes based on ImportOrder
code style rule
[ https://issues.apache.org/jira/browse/HUDI-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982336#comment-16982336 ]
Vinoth Chandar commented on HUDI-363:
-------------------------------------
High level question... [~vbalaji] did we turn on spotless again? I think we had some issues during the release?
Can we have spotless autofix these rules as well?
> Refactor codes based on ImportOrder code style rule
> ---------------------------------------------------
>
> Key: HUDI-363
> URL: https://issues.apache.org/jira/browse/HUDI-363
> Project: Apache Hudi (incubating)
> Issue Type: Improvement
> Reporter: lamber-ken
> Priority: Critical
>
> Refactor codes based on ImportOrder code style rules. Manay places need to refactor, so this rule may needs some subtasks.
> follow bellow steps to fix:
> 1, set the severity ImportOrder to error level in local env.
> 2, use command to check which module you are working on.
> {code:java}
> mvn -pl hudi-common checkstyle:check
> {code}
> 3, remember to reset severity to info before commiting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)