[geomesa-dev] [JIRA] (GEOMESA-2501) Query planning discards lower date b

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

[geomesa-dev] [JIRA] (GEOMESA-2501) Query planning discards lower date bound equal to the Java epoch

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 20 Dec 2018 15:56:08 +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:	Bug
Affects Versions:	2.0.0, 1.3.4, 1.3.5, 1.3.6, 2.1.0, 2.0.1, 2.0.2
Assignee:	Unassigned
Created:	20/Dec/18 10:56 AM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

Querying for "dtg > '1970-01-01T00:00:00' AND dtg < '...'" seems to ignore the lower bound, and not use the z3 index, resulting in a full table scan. "dtg > '1970-01-01T00:00:01'" works as expected.

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-2500) Add support to the KDS for reading confluent' avro-serialized topics
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2502) Cache immutable simple feature type instances to avoid repeated spec parsing
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2500) Add support to the KDS for reading confluent' avro-serialized topics
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2502) Cache immutable simple feature type instances to avoid repeated spec parsing
Index(es):
- Date
- Thread

Breadcrumbs