[geomesa-dev] [JIRA] (GEOMESA-2322) Kafka - allow for specifying SSI tie

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[geomesa-dev] [JIRA] (GEOMESA-2322) Kafka - allow for specifying SSI tier sizes through configuration

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 17 Jul 2018 13:11:31 +0000 (UTC)
Auto-submitted: auto-generated
Delivered-to: geomesa-dev@xxxxxxxxxxxxxxxx
List-archive: <https://dev.locationtech.org/mhonarc/lists/geomesa-dev>
List-help: <mailto:geomesa-dev-request@locationtech.org?subject=help>
List-subscribe: <https://dev.locationtech.org/mailman/listinfo/geomesa-dev>, <mailto:geomesa-dev-request@locationtech.org?subject=subscribe>
List-unsubscribe: <https://dev.locationtech.org/mailman/options/geomesa-dev>, <mailto:geomesa-dev-request@locationtech.org?subject=unsubscribe>

Title: Message Title

Emilio Lahr-Vivaz created an issue

Issue Type:	Improvement
Assignee:	Unassigned
Created:	17/Jul/18 9:11 AM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

in SizeSeparatedBucketIndex, we chose somewhat arbitrary tier sizes. Probably would be good to allow users to specify the tiers.

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira

Prev by Date: [geomesa-dev] [JIRA] (GEOMESA-2321) Look into using TransformFeatureStore for relational projection handling
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2323) Kafka - better handling for anti-meridian crossing geometries
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2321) Look into using TransformFeatureStore for relational projection handling
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2323) Kafka - better handling for anti-meridian crossing geometries
Index(es):
- Date
- Thread

Back to the top