[geomesa-dev] [JIRA] (GEOMESA-2402) Use one-side bounded filters in tier

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

[geomesa-dev] [JIRA] (GEOMESA-2402) Use one-side bounded filters in tiered range planning

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 17 Sep 2018 21:00:16 +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

Issue Type:	Improvement
Assignee:	Unassigned
Created:	17/Sep/18 5:00 PM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

for example, if we have "foo = 'bar' and dtg > '2018'", our attribute index won't use any of the secondary z-index b/c the date filter won't generate any z3 ranges. However, given that we have an implicit lower and upper bound based on the primary range, we could potentially trim off a lot of ranges by just generating a tiered lower or upper range.

Add Comment

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-2401) Handle exceptions in URL Config provider
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2403) Default transforms in Converters
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2401) Handle exceptions in URL Config provider
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2403) Default transforms in Converters
Index(es):
- Date
- Thread

Breadcrumbs