locationtech / locationtech/geomesa

Document tips for upgrading HBase coprocessors

Open Beginner friendly
#10,052 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.5k
Forks
446
Avg merge
1d 8h
Merged PRs (30d)
31

Description

Document tips for upgrading HBase coprocessors

The HBase shell is based on JRuby and allows for light scripting. For example,

'''
list.grep(/geomesa/).each
{ |table| describe table }

'''
Would describe all the tables which have 'geomesa' in their name.

Similarly a routine maintenance operation like updating all the coprocessor jars could be achieved with

'''
list.grep(/geomesa/).each{ |table| alter table,
{METHOD => 'table_att_unset', NAME => 'coprocessor$1'}
,
{'coprocessor'=>'s3:///geomesa-hbase-distributed-runtime-hbase1_2.11-3.0.0-SNAPSHOT.jar|org.locationtech.geomesa.hbase.coprocessor.GeoMesaCoprocessor|1073741823|'}
}
'''


Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2839

Key: GEOMESA-2839
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: James Hughes
Created: Wed, 29 Apr 2020 17:03:38 -0400
Updated: Wed, 29 Apr 2020 17:03:38 -0400

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the HBase shell examples in the issue and locate the project documentation for HBase coprocessors and routine maintenance. Verify the JRuby commands against the supported HBase version; done means the documentation explains how to upgrade coprocessor jars and includes working examples for selecting and altering tables.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
databases, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.