[
https://issues.apache.org/jira/browse/HIVE-16186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930665#comment-15930665
]
ASF GitHub Bot commented on HIVE-16186:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/161
HIVE-16186: REPL DUMP shows last event ID of the database even if we use
LIMIT option.
Returned proper last repl Id if LIMIT option is used.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-16186
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/161.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #161
----
commit de8eb79ef9ec2aac2c31474af04834850947acb6
Author: Sankar Hariappan <mailtosank...@gmail.com>
Date: 2017-03-17T20:21:08Z
HIVE-16186: REPL DUMP shows last event ID of the database even if we use
LIMIT option.
----
> 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
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Labels: DR
> Attachments: HIVE-16186.01.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)
