locationtech / locationtech/geomesa

Explore packaging distros of specific back-end versions

Open
#9,704 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

Explore packaging distros of specific back-end versions

E.g. geomesa-accumulo-dist-nodeps, geomesa-accumulo-dist-hadoop-2.8.5-accumulo-1.9.2, etc
This would simplify installation for common setups, both for the CLI tools and geoserver.

Ideally this would be a downstream project that build up tar.gzs based on the nodeps ones coming from geomesa. This may create a maintenance burden to ensure that the packages all work, so we should consider that.

Similarly, we may want to do the same with geomesa-*-spark-runtime.

This may also have IP implications with regards to locationtech, so we need to consider that.


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

Key: GEOMESA-2450
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Thu, 1 Nov 2018 12:44:36 -0400
Updated: Fri, 17 Apr 2020 13:57:09 -0400


Comments:

557058:48912df4-0004-4f90-9915-db26684ec006 (Fri, 17 Apr 2020 13:29:46 -0400):

Is there a part score for this ticket which would be easy?

557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Fri, 17 Apr 2020 13:57:09 -0400):

Not that I can think of...

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 by assessing the proposed downstream project and the existing nodeps and spark-runtime distributions. Determine how tar.gz packages for common Accumulo, Hadoop, and Spark setups would support the CLI tools and GeoServer, then document the maintenance and LocationTech IP implications before defining what a viable package set would be.

Written by the indexing model from the issue text.

Assessment

Tech stack
hadoop, spark
Domain
backend, build-system, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.