You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2017/12/22 19:08:00 UTC
[jira] [Assigned] (KNOX-1155) New Knox Gateway Service for
ElasticSearch
[ https://issues.apache.org/jira/browse/KNOX-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Larry McCay reassigned KNOX-1155:
---------------------------------
Assignee: Dequan Chen
> New Knox Gateway Service for ElasticSearch
> ------------------------------------------
>
> Key: KNOX-1155
> URL: https://issues.apache.org/jira/browse/KNOX-1155
> Project: Apache Knox
> Issue Type: New Feature
> Components: Build, Release
> Affects Versions: 0.9.0, 0.9.1, 0.10.0, 0.11.0
> Environment: Knox Gateway Servers
> Reporter: Dequan Chen
> Assignee: Dequan Chen
> Priority: Critical
> Labels: patch
> Fix For: Future
>
> Attachments: rewrite.xml, service.xml
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> We have used a lot of Knox Gateway Services and ElasticSearch service on our Big Data platforms. However there are no Knox Gateway Service for ElasticSearch yet. In our situation, we need such a Knox Gateway Service for ElasticSearch without Knox to do the …
> authentication but ElasticSearch Rest Server(s) to do the authentication. As per our use case, we have developed such a Knox Gateway ElasticSearch Service (services/elasticsearch/1.0.0), and we are in a mode to share the code to the Apache Knox community because it has been fully tested for the following scenarios:
> (1) No-LDAP, Local-LDAP or company-specific-LDAP authentication in the Knox gateway;
> (2) Any Elasitcsearch Index - creation, deletion, refresshing and data - writing, updating and retrieval;
> (3) Elasticsearch node root query.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)