[geomesa-dev] [JIRA] (GEOMESA-2641) CQEngine

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

[geomesa-dev] [JIRA] (GEOMESA-2641) CQEngine - don't return mutable 'live' features from queries

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 3 Jun 2019 19:10:53 +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:	03/Jun/19 3:10 PM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

Currently CQEngine returns the feature stored in the index. If you then mutate the feature (i.e. setAttribute), it changes the feature in the store, and the indices get out of sync.

Potential solution: use immutable features. Would be nice, if someone tried to mutate one, to have a good error message related to CQEngine.

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-2640) Spark - Saving a dataframe to an existing schema fails
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2642) Upgrade to geotools 21.x
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2640) Spark - Saving a dataframe to an existing schema fails
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2642) Upgrade to geotools 21.x
Index(es):
- Date
- Thread

Breadcrumbs