[geomesa-dev] [JIRA] (GEOMESA-2554) defer shapely udt registration until

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

[geomesa-dev] [JIRA] (GEOMESA-2554) defer shapely udt registration until pyspark is on path

From: "Tom Kunicki (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 12 Feb 2019 20:11:31 +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

Tom Kunicki created an issue

Issue Type:	Bug
Assignee:	Unassigned
Created:	12/Feb/19 3:11 PM
Priority:	Critical
Reporter:	Tom Kunicki

Current implementation attempts to import geomesa_pyspark.types before the deferred addition of pyspark to python system path. This requires users to register a pyspark installation in their environment which is inconvenient and unnecessary.

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-2553) Converters - use CopyingInputStream in DelimitedTextConverter instead of re-creating the row for $0
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-2555) NiFi - support NiFi expressions and variables in configuration
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-2553) Converters - use CopyingInputStream in DelimitedTextConverter instead of re-creating the row for $0
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-2555) NiFi - support NiFi expressions and variables in configuration
Index(es):
- Date
- Thread

Breadcrumbs