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

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

pan3793 commented on PR #8455:
URL: https://github.com/apache/hadoop/pull/8455#issuecomment-4312466022

   > At least claude is good at doing a lot of the low-level migration work 
-it's a lot easier now, isn't it?
   
   @steveloughran, yea, it's super fast and most of the time is reliable as 
long as I describe the task clearly and supply sufficient knowledge to the 
model.
   
   BTW, do we want to adopt the `Assisted-by: ...` tag in the commit message? 
It was just adopted formally by the Linux Kernel project. I think it's better 
than tag `Generated-by: ...`(ASF policy written in 2023 suggests it, but not 
enforced) or a statement like "Contains content generated by ..."
   
   
https://chyshkala.com/blog/linux-kernel-s-assisted-by-tag-sasha-levin-s-secret-ai-patch-sparks-contributor-guidelines
   
   https://docs.kernel.org/process/coding-assistants.html
   
   https://www.apache.org/legal/generative-tooling.html




> Cut WritableRPCEngine
> ---------------------
>
>                 Key: HADOOP-19864
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19864
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 3.6.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>
> Cut {{WritableRpcEngine}} from the code
> It's been obsolete for over a decade, with MAPREDUCE-6706 not needed 
> internally.
> Tez still uses it (TEZ-4708 ) so this removal will be incompatible for them. 



--
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