|Table of Contents|
Goals of the Roadmap
We'd like to capture the current state of GeoMesa in terms of major work items, desired features, and crazy new ideas! Feel free to add notes or updates, etc. Please don't delete ideas but make them
strickthrough unless its really just not needed. If you do add a new item, try to flush it out with a good description so that its useful to other people who may pick up your idea in the future.
Tooling & Automation
|Installation automation||- AWS, Cloudera, Hortonworks, general|
|Data modeling tooling|
|JEMA like workflow tooling|
- hosted analytics
- YARN app for load balancing workflows
- data and analytic hosting platform?
|Tools for Hbase, Cassandra, Dynamo, etc||We have accumulo and kafka. maybe add some basic tools for the other ones|
|Push Button Deploys||Everything|
Indexing, Performance, Optimization
S2 evaluation, Hilbert, etc. The Nasa thing Andrew Annex (Deactivated) please put it in here, metro hash?
start and end times
- summary stats
- vacuum analyze
Move these out into separate line items as we flush them out
- Aggregate/batch simple features in iterator like we do for bin queries
- don't double store feature ID (once in row, once in simple feature) - would require changes to deserializationn and might complicate batching simple features
- automatically sample results for WMS queries based on expected result size
- use lazy deserialization in client
|Pan and zoom caching|
|Configurable z shards|
- currently hard-coded at four shards
- number of ranges we compute might need to be based on the shards so we don't create too many
|Complex Feature Support|
Integration of GeoMesa with new Open Source tools, databases, platforms, etc
Metrics/graphite and predefined dashboards
- streaming metrics
|Nifi||- flow definitions for canonical setups|
|Hive||(see Hortonworks visual sql builder)|
|Cloud native storage|
You can't afford to use AWS for petabytes?
S3 Storage - store binary files, fairly static
Use case: Using weather stuff
|Avro WFS MimeType plugin||need to open source||GEOMESA-840|
What do we need additional Documentation for?
Should we open up Confluence? What about documentation that changes or new tutorials?
|FAQ page||for common errors, configuration, etc|
|Data defined ageoff||Need to be able to age off data based on some criteria in the SFT or visibilities||GEOMESA-899|
Need to be able to audit all queries against a GeoServer WFS/WMS/WPS/REST/ETC
Seapy, Thomas, Chris, Jim
|Accumulo 1.7||Support for Accumulo 1.7|
- open source
New Features, Capabilities, & Brainstorms
|Area||Description/Ideas||POC/Lead||JIRA Tickets||Importance/Usefullness (low/medium/high)|
|Schema Evolution||ability to gracefully evolve schemas|
- quotas, rate limiting, geofencing, filtering
|SQL||Support for SQL queries|
finishing it, almost done.
merge with blob store?
no schema evolution concerns
|Blob Store||More file formats (S3, other image formats, etc)|
Don't transform to SFs, store native avro/json as "blobs" and index them
|Binary File Datastores|
|Count Min Sketch|
|Attribute Bloom filters?|