[
https://issues.apache.org/jira/browse/HIVE-16186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946738#comment-15946738
]
Lefty Leverenz commented on HIVE-16186:
---------------------------------------
[~vgumashta], why are the fix versions set to 2.2.0 and 2.3.0?
The commit went to master, which is now for 3.0.0, and I don't see the patch in
branch-2 (for 2.3.0) or branch-2.2 (dunno what that's for) or Owen's branch-2.2
(for 2.2.0).
See commit 5d83302907887ace2bf35d1d4487f030c93d09a3.
Release information:
* [About next 2.3 release |
http://mail-archives.apache.org/mod_mbox/hive-dev/201703.mbox/%3ccams4yue4wn3zabeet-acn6smhup0k8ffgeu3w6m4y9wgjfs...@mail.gmail.com%3e]
* [Re: Backward incompatible changes |
http://mail-archives.apache.org/mod_mbox/hive-dev/201703.mbox/%3cCAHfHakEL-+C=q5rnrunxfcmqabnpm5m_h6qrokcrns24cv2...@mail.gmail.com%3e]
> REPL DUMP shows last event ID of the database even if we use LIMIT option.
> --------------------------------------------------------------------------
>
> Key: HIVE-16186
> URL: https://issues.apache.org/jira/browse/HIVE-16186
> Project: Hive
> Issue Type: Sub-task
> Components: repl
> Affects Versions: 2.1.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Labels: DR
> Fix For: 2.2.0, 2.3.0
>
> Attachments: HIVE-16186.01.patch, HIVE-16186.02.patch,
> HIVE-16186.03.patch
>
>
> Looks like LIMIT option doesn't work well with REPL DUMP.
> 0: jdbc:hive2://localhost:10001/default> REPL DUMP default FROM 170 LIMIT 1;
> +--------------------------+---------------+
> | dump_dir | last_repl_id |
> +--------------------------+---------------+
> | /tmp/dump/1489395053411 | 195 |
> +--------------------------+---------------+
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
