[jira] [Commented] (BIGTOP-2779) new hive charm

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025423#comment-16025423 ] 

ASF GitHub Bot commented on BIGTOP-2779:
----------------------------------------

GitHub user kwmonroe opened a pull request:

    https://github.com/apache/bigtop/pull/217

    BIGTOP-2779: new hive charm

    note to upstream: squash ~16 before commit
    
    Key notes:
    - new hive charm
    - readme: be like the other bigtop charms
    - readme: describe metastore/hbase/usage/config
    - include the right roles! (metastore+server2)
    - enable hbase integration
    - use systemctl services vs direct hive service
    - use a matrix to determine if/when to reinstall hive
    - use report_status
    - stop serving clients when appropriate

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/juju-solutions/bigtop feature/BIGTOP-2779/hive-charm

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/bigtop/pull/217.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 #217
    
----
commit 703f260a5c3675ba495f5812fa993b2de6a88008
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-06T15:06:41Z

    adding bigtop hive
    
    - cleanup kruft from old charm
    - add readme section describing embedded db vs external db
    - only send client relation info if we have an external db (ext db required for hiveserver2)

commit 2ad22c05a01b1b1f69761b3b666a2b9d495eb3aa
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-09T15:41:01Z

    alter directory structure to match upstream

commit 10793a324f39bb7d80f3039cd36d81c90e4ef9a6
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-09T15:41:50Z

    match recent rename changes; no work requried for hive_env template (hive.deb does it for us)

commit ae9d8b8b93e1ed1af70ab262c760c3916c7ccf77
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-09T18:28:20Z

    add license headers

commit 687f83889d5201f354772f1d5e5dc687b91d57d3
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-09T18:33:58Z

    readme update to tell people this is a bigtop service

commit 881e10a6af473538023232993a9f45a0904601f0
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-29T18:06:20Z

    update tests so we have a simple deployment along with a more complicated hadoop/hive deployment for smoke testing

commit 4b94000e5f88f486a22188c70e83208c6c552ee6
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-29T18:07:22Z

    use the bigtop smoke testing mechanism provided by the bigtop base layer

commit 71ac43c28a3f72e3cdb827f008492c226ea8a7d4
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-29T18:08:20Z

    various updates
    
    - export HIVE_HOME (needed by smoke-test)
    - copy the right template file; we need hive-env (not provided by bigtop)
    for our heap config instead of hive-site (which is provided by bigtop)
    - lowercase status
    - remove unneeded hive.db.configured state; just use database.available

commit ee6ed1ca97f2bff319f90f82f2cf3d98e3837f0a
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-29T18:26:03Z

    update readme with 2.0 instructions

commit c474b5bb57de154dd11aab95864dc5767f365e05
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-29T19:59:35Z

    bring back the hive.db.configured state
    
    I previously removed this state in favor of just using db.available, but this
    meant configure_with_x_db() was called every time update-status ran. Having
    the hive.db.configured state lets us only run those methods when the db
    landscape changes.

commit b1ecb1fa6305d4fcf1b6e314f254baf94e7056e7
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-06-30T15:08:36Z

    test tweaks

commit f6fdd17977db99dea7efa3b9b1ba2cf76696ae01
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2016-08-10T17:11:01Z

    make hive multi-series (trusty and xenial)

commit ebfc54fe5f649e404cfb77cc880ee7a51531ff4d
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2017-05-17T18:26:34Z

    Merge branch 'master' into hive
    
    sync this outdated branch with upstream

commit 10d1f2811783ff29b1889099ac9d7559489d052d
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2017-05-17T21:59:33Z

    make hive consistent with other bigtop charms

commit 279621c0cd483825a67341ed909d50a41bb82bd1
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2017-05-24T14:58:35Z

    initial hbase interface support

commit 45c3320a3151dd40bb63fbb454ff2e36245b3807
Author: Kevin W Monroe <ke...@canonical.com>
Date:   2017-05-25T20:32:03Z

    make hive great again
    
    - readme: be like the other bigtop charms
    - readme: describe metastore/hbase/usage/config
    - include the right roles! (metastore+server2)
    - enable hbase integration
    - use systemctl services vs direct hive service
    - use a matrix to determine if/when to reinstall hive
    - use report_status
    - stop serving clients when appropriate

----


> new hive charm
> --------------
>
>                 Key: BIGTOP-2779
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2779
>             Project: Bigtop
>          Issue Type: New Feature
>          Components: deployment
>    Affects Versions: 1.2.0
>            Reporter: Kevin W Monroe
>            Assignee: Kevin W Monroe
>            Priority: Minor
>
> Add a Hive charm.  Make sure it can integrate with existing Hadoop and HBase charms.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)