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

ASF GitHub Bot commented on HADOOP-18487:
-----------------------------------------

steveloughran commented on PR #4996:
URL: https://github.com/apache/hadoop/pull/4996#issuecomment-1713650781

   updated pr tries to address reviews, including building.txt details.
   
   regarding @apurtell's comment about static vs qualified import of 
`getRemoteException()` I started to convert, but got fed up with the needless 
repetition. So upgraded the RPC invocations to java 8 language level (!!) by 
adding a new operation `ipc()` to take a lambda expression and do the 
invocation, translating the result
   
   ```java
     public static <T> T ipc(IpcCall<T> call) throws IOException {
       try {
         return call.call();
       } catch (ServiceException e) {
         throw getRemoteException(e);
       }
     }
   ```
   
   this lets us have far simpler invocations in the code
   ```java
       status = ipc(() -> rpcProxy.getServiceStatus(NULL_CONTROLLER,
           GET_SERVICE_STATUS_REQ));
   ```
   
   I've done this for hadoop-common; if all are happy then I will do for the 
rest of the modules
       
   




> protobuf-2.5.0 dependencies => provided
> ---------------------------------------
>
>                 Key: HADOOP-18487
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18487
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build, ipc
>    Affects Versions: 3.3.4
>            Reporter: Steve Loughran
>            Priority: Major
>              Labels: pull-request-available
>
> uses of protobuf 2.5 and RpcEnginej have been deprecated since 3.3.0 in 
> HADOOP-17046
> while still keeping those files around (for a long time...), how about we 
> make the protobuf 2.5.0 export off hadoop common and hadoop-hdfs *provided*, 
> rather than *compile*
> that way, if apps want it for their own apis, they have to explicitly ask for 
> it, but at least our own scans don't break.
> i have no idea what will happen to the rest of the stack at this point, it 
> will be "interesting" to see



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to