[
https://issues.apache.org/jira/browse/HIVE-17523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163992#comment-16163992
]
ASF GitHub Bot commented on HIVE-17523:
---------------------------------------
GitHub user b-slim opened a pull request:
https://github.com/apache/hive/pull/249
[HIVE-17523] Fix insert into bug
https://issues.apache.org/jira/browse/HIVE-17523
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/b-slim/hive fix_insert_into
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/249.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 #249
----
commit 579483ee878a16491d61c0eada5891880f507302
Author: Slim Bouguerra <slim.bougue...@gmail.com>
Date: 2017-09-09T00:12:14Z
set max tries to zero to make test faster.
Change-Id: Ia1523f3b565f4b08c76067fa0bac32d5171fb46e
commit ca5c7ccb1cc41dc3c8c76ccefb2d05b7d096a4ca
Author: Slim Bouguerra <slim.bougue...@gmail.com>
Date: 2017-09-11T22:39:40Z
Make insert into use data segment pusher to avoid duplication of logic some
refactoring of exeception logging and handeling
Change-Id: I7bd8f29a83720f4cfba338acf27fb85b9774eafe
commit 3f2dd91c04839df7c068e1608b3e2af98babdc11
Author: Slim Bouguerra <slim.bougue...@gmail.com>
Date: 2017-09-13T01:04:05Z
cleaning and refactor
Change-Id: I9e2b14e6e32af095d2c4d2f9f1fbe8a9cced30ad
----
> Insert into druid table hangs Hive server2 in an infinit loop
> --------------------------------------------------------------
>
> Key: HIVE-17523
> URL: https://issues.apache.org/jira/browse/HIVE-17523
> Project: Hive
> Issue Type: Bug
> Components: Druid integration
> Reporter: slim bouguerra
> Assignee: Nishant Bangarwa
> Labels: pull-request-available
> Attachments: HIVE-17523.patch
>
>
> Inserting data via insert into table backed by druid can lead to a Hive
> server hang.
> This is due to some bug in the naming of druid segments partitions.
> To reproduce the issue
> {code}
> drop table login_hive;
> create table login_hive(`timecolumn` timestamp, `userid` string, `num_l`
> double);
> insert into login_hive values ('2015-01-01 00:00:00', 'user1', 5);
> insert into login_hive values ('2015-01-01 01:00:00', 'user2', 4);
> insert into login_hive values ('2015-01-01 02:00:00', 'user3', 2);
> insert into login_hive values ('2015-01-02 00:00:00', 'user1', 1);
> insert into login_hive values ('2015-01-02 01:00:00', 'user2', 2);
> insert into login_hive values ('2015-01-02 02:00:00', 'user3', 8);
> insert into login_hive values ('2015-01-03 00:00:00', 'user1', 5);
> insert into login_hive values ('2015-01-03 01:00:00', 'user2', 9);
> insert into login_hive values ('2015-01-03 04:00:00', 'user3', 2);
> insert into login_hive values ('2015-03-09 00:00:00', 'user3', 5);
> insert into login_hive values ('2015-03-09 01:00:00', 'user1', 0);
> insert into login_hive values ('2015-03-09 05:00:00', 'user2', 0);
> drop table login_druid;
> CREATE TABLE login_druid
> STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler'
> TBLPROPERTIES ("druid.datasource" = "druid_login_test_tmp",
> "druid.segment.granularity" = "DAY", "druid.query.granularity" = "HOUR")
> AS
> select `timecolumn` as `__time`, `userid`, `num_l` FROM login_hive;
> select * FROM login_druid;
> insert into login_druid values ('2015-03-09 05:00:00', 'user4', 0);
> {code}
> This patch unifies the logic of pushing and segments naming by using Druid
> data segment pusher as much as possible.
> This patch also has some minor code refactoring and test enhancements.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
