HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-751620885
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-692523314
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-692387211
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-679866088
Just rebased. I haven't reached consensus around the discussion in dev
mailing list though. I'll bump it again.
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-675298909
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-675250207
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-661645101
FYI, I've initiated the discussion around this in dev@ mailing list, how to
deal with "latestFirst" option and metadata growing.
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-657271083
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-643729336
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-643706117
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-643705743
I can even tolerate the fact maxFileAge is originated from path's latest
timestamp. If we don't believe the node's wall time (I suspect other logic
works well in such case
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-641097576
I agree the new addition of the similar option feels tricky.
Maybe you've already indicated there're some cases `maxFileAge` has to be
ignored which means Spark is
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-640424887
> Maybe the user group reference can be added as a comment and not as commit
msg.
I'll move it to the JIRA description - personally I'd be OK to leave the
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-634491641
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-634421190
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-634305928
retest this, please
This is an automated message from the Apache Git Service.
To respond to the message,
HeartSaVioR commented on pull request #28422:
URL: https://github.com/apache/spark/pull/28422#issuecomment-621796985
cc. @tdas @zsxwing @jose-torres @gaborgsomogyi
This is an automated message from the Apache Git Service.
To
17 matches
Mail list logo