[
https://issues.apache.org/jira/browse/HIVE-25582?focusedWorklogId=681964&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-681964
]
ASF GitHub Bot logged work on HIVE-25582:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/21 11:56
Start Date: 16/Nov/21 11:56
Worklog Time Spent: 10m
Work Description: kgyrtkirk commented on pull request #2693:
URL: https://github.com/apache/hive/pull/2693#issuecomment-970199038
Wouldn't it be possible to somehow fix the default cache implementation
instead of hacking that condition with !tez further?
And from the above comments I suspect that this could be covered with a test
- or it needs some special circumstances?
--
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: gitbox-unsubscr...@hive.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 681964)
Time Spent: 1h 20m (was: 1h 10m)
> Empty result when using offset limit with MR
> --------------------------------------------
>
> Key: HIVE-25582
> URL: https://issues.apache.org/jira/browse/HIVE-25582
> Project: Hive
> Issue Type: Bug
> Components: Operators
> Affects Versions: 4.0.0
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The _mr.ObjectCache_ caches nothing, every time when the limit [retrieving
> global counter from the
> cache|https://github.com/apache/hive/blob/7b3ecf617a6d46f48a3b6f77e0339fd4ad95a420/ql/src/java/org/apache/hadoop/hive/ql/exec/LimitOperator.java#L150-L161],
> a new AtomicInteger will be returned. This make offset _<=
> currentCountForAllTasksInt_ always be evaluated to false, as _offset > 0_,
> the operator will skip all rows.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
