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

Akira Ajisaka commented on HDFS-15950:
--------------------------------------

Note: I didn't backport this to branch-2.10 because the build failed with the 
patch.
{noformat}
[INFO] --- protobuf-maven-plugin:0.5.1:compile (src-compile-protoc) @ 
hadoop-hdfs-client ---
[INFO] Compiling 9 proto file(s) to 
/Users/aajisaka/git/github/hadoop/hadoop-hdfs-project/hadoop-hdfs-client/target/generated-sources/java
[ERROR] PROTOC FAILED: inotify.proto:77:12: "hadoop.hdfs.FsPermissionProto" 
seems to be defined in "hdfs.proto", which is not imported by "inotify.proto".  
To use it here, please add the necessary import.
inotify.proto:115:12: "hadoop.hdfs.FsPermissionProto" seems to be defined in 
"hdfs.proto", which is not imported by "inotify.proto".  To use it here, please 
add the necessary import.
ClientNamenodeProtocol.proto: Import "inotify.proto" was not found or had 
errors.
ClientNamenodeProtocol.proto:747:12: "EventsListProto" is not defined.{noformat}

> Remove unused hdfs.proto import
> -------------------------------
>
>                 Key: HDFS-15950
>                 URL: https://issues.apache.org/jira/browse/HDFS-15950
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 3.4.0
>            Reporter: Gautham Banasandra
>            Assignee: Gautham Banasandra
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.3.1, 3.4.0, 3.1.5, 3.2.3
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> hdfs.proto is imported in inotify.proto and is unused. This causes the 
> following warning to be generated -
> {code}
> inotify.proto:35:1: warning: Import hdfs.proto is unused.
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to