You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uniffle.apache.org by "zuston (via GitHub)" <gi...@apache.org> on 2023/04/20 02:25:50 UTC

[GitHub] [incubator-uniffle] zuston commented on issue #731: [FEATURE] Adaptive length of different parts of blockId

zuston commented on issue #731:
URL: https://github.com/apache/incubator-uniffle/issues/731#issuecomment-1515621994

   @awdavidson 
   
   In PR #749, @advancedxy propose a new possibility to solving this. refer https://github.com/apache/incubator-uniffle/pull/749#issuecomment-1486540366
   
   But for my thought, it sounds good to me. But in the current codebase, the taskAttemptId must be a real value, some code will retrieve this from this blockId and do some validation. I'm not sure whether removing this part or optimize.
   
   > What’s the feasibility of using a combination of the stageId and taskId? What else can be done?
   
   I'm not sure what do you mean.  Could you help describe more?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@uniffle.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org