[geomesa-dev] [JIRA] (GEOMESA-3084) Spark - use same authorizations logi

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

[geomesa-dev] [JIRA] (GEOMESA-3084) Spark - use same authorizations logic as regular scans

From: "Emilio Lahr-Vivaz (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 25 May 2021 14:17:18 +0000 (UTC)
Atlassianmail-meta-obsolete-id: 01F6HY653ZKTYAGFT8SF037Q00
Atlassianmail-meta-transaction-id: 01F6HY653ZKTYAGFT8SF037Q00
Auto-submitted: auto-generated
Delivered-to: geomesa-dev@xxxxxxxxxxx
Delivered-to: geomesa-dev@997229fffb4f
List-archive: <https://www.eclipse.org/mailman/private/geomesa-dev/>
List-help: <mailto:geomesa-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/geomesa-dev>, <mailto:geomesa-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/geomesa-dev>, <mailto:geomesa-dev-request@eclipse.org?subject=unsubscribe>

Title: Message Title

Issue Type:	Bug
Assignee:	Unassigned
Created:	25/May/21 10:17 AM
Priority:	Major
Reporter:	Emilio Lahr-Vivaz

I.e. in accumulo we use the connection user's auths by default if nothing else is configured. but in spark, we only use the geomesa.security.auths param value.

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-3083) DWithin filters do not always calculate correct distance
Next by Date: [geomesa-dev] [JIRA] (GEOMESA-3085) geomesa 3.1.0 Hbase NPE
Previous by thread: [geomesa-dev] [JIRA] (GEOMESA-3083) DWithin filters do not always calculate correct distance
Next by thread: [geomesa-dev] [JIRA] (GEOMESA-3085) geomesa 3.1.0 Hbase NPE
Index(es):
- Date
- Thread

Breadcrumbs