[geomesa-dev] [JIRA] (GEOMESA-2522) Converters - specify id or user data

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

[geomesa-dev] [JIRA] (GEOMESA-2522) Converters - specify id or user data field in error messages

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 17 Jan 2019 16:52:35 +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/Jan/19 11:52 AM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

We include the field name if it's a field, but if it's the user data or id field we don't:
https://github.com/locationtech/geomesa/blob/geomesa_2.11-2.2.0/geomesa-convert/geomesa-convert-common/src/main/scala/org/locationtech/geomesa/convert2/AbstractConverter.scala#L131

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: Re: [geomesa-dev] RpcEndpointNotFoundException
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2523) Docs - delimited text converter example id-field is invalid
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2521) Fix cross-layer filtering typename in Query
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2523) Docs - delimited text converter example id-field is invalid
Index(es):
- Date
- Thread

Back to the top