locationtech / locationtech/geomesa
CassandraSpatialRDDProvider Implementation
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
CassandraSpatialRDDProvider Implementation
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2755
Key: GEOMESA-2755
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: James Hughes
Reporter: Lucas Chen
Created: Wed, 11 Dec 2019 00:40:22 -0500
Updated: Fri, 16 Dec 2022 14:13:11 -0500
Affects Version(s): 2.4.1
Component(s): Cassandra
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Fri, 2 Dec 2022 15:04:51 -0500):
Documenting some WIPs/partial efforts:
https://github.com/rayjzeng/geomesa/tree/CassandraSparkIntegration
https://github.com/urbanit/geomesa
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the original GEOMESA-2755 issue and the referenced CassandraSparkIntegration, urbanit/geomesa, and cspark branches to determine the intended provider scope. The issue names no files, tests, API details, or completion criteria, so confirm those before starting and define what a completed CassandraSpatialRDDProvider implementation must include.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100