rdblue commented on issue #23608: [SPARK-26682][SQL] Use taskAttemptID instead of attemptNumber for Hadoop. URL: https://github.com/apache/spark/pull/23608#issuecomment-456925746 I think that calling `toInt` should be fine. It is extremely unlikely that taskAttemptID will be larger than 2 billion and it would be fine for this purpose if it were truncated. It would still be unique enough for deduplicating across attempts of the same stage. The only case I can think of where this would be a problem is if the Hadoop TaskAttemptID can't handle a negative attempt number. I'll update this to `taskContext.taskAttemptId().toInt & Integer.MAX_VALUE` so that this wraps around to 0.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
