[ 
https://issues.apache.org/jira/browse/KNOX-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301931#comment-16301931
 ] 

Larry McCay commented on KNOX-1155:
-----------------------------------

Hmmm - that seems like you are trying to commit to a remote branch which you 
will not have access to obviously.

We just want to create a patch.
Here is what I usually do actually:

1. Make some changes in your private repo
2. Stage the changes using git stage or GitX or some similar tool.
3. Create a patch from the staged changes via "git diff --no-prefix --staged > 
my.patch" change the name of my.patch to your JIRA KNOX-1155-001.patch
4. Attach the patch to the JIRA

The benefit of doing it from staged changes rather than commits is that you can 
easily continue to work on it based on review comments and the like.

Hope that helps.

> 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: 1.1.0
>
>         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)

Reply via email to