[geomesa-dev] [JIRA] (GEOMESA-2634) Converters

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

[geomesa-dev] [JIRA] (GEOMESA-2634) Converters - separate out file-based vs stream-based processing

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 31 May 2019 18:07:48 +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:	31/May/19 2:07 PM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

Some of our converters require random file access, so they can't handle input streams. Originally, this was just the ShpFile converter, and we handled it with kind of a hack to set the file in the evaluation context. But now we've added parquet as well, so we should probably separate out stream vs file based processing and type inference somehow.

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-2633) Shade and relocate json4s in spark runtime JARs
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2635) SparkSQL - error saving dataframe back to data store due to schema mismatch
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2633) Shade and relocate json4s in spark runtime JARs
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2635) SparkSQL - error saving dataframe back to data store due to schema mismatch
Index(es):
- Date
- Thread

Breadcrumbs