ajantha-bhat commented on a change in pull request #4013:
URL: https://github.com/apache/carbondata/pull/4013#discussion_r534713302



##########
File path: core/src/main/java/org/apache/carbondata/core/util/TrashUtil.java
##########
@@ -208,6 +205,14 @@ public static boolean isTrashRetentionTimeoutExceeded(long 
fileTimestamp) {
     return difference > retentionMilliSeconds;
   }
 
+  /**
+   * whether trash data outside of .Trash folder is time out
+   */
+  public static boolean isTrashDataTimeout(long fileTimestamp) {
+    return isTrashRetentionTimeoutExceeded(fileTimestamp) &&

Review comment:
       In the default case, when `isTrashRetentionTimeoutExceeded`  is true, 
then `isMaxQueryTimeoutExceeded` will always be true. 
   why not remove `queryMaxTimeout` from code and in query flow, clean the 
metadata indexed trash based on `trashRetentionTimeout` ??




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

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


Reply via email to