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

stack commented on HBASE-15893:
-------------------------------

Hey [~sudeeps] Mind putting the putting the next patch after addressing the 
above up on review board? Its a biggie and putting it up on review board helps 
reviewing the big ones. Use the new submit-patch.py and it does most of this 
for you (don't worry about messing up... we'll help you through):

{code}
$ ./dev-support/submit-patch.py --help
usage: submit-patch.py [-h] [-b BRANCH] [-jid JIRA_ID] [-srb]
                       [--reviewers REVIEWERS] [--patch-dir PATCH_DIR]
                       [--rb-repo RB_REPO]

optional arguments:
  -h, --help            show this help message and exit
  -b BRANCH, --branch BRANCH
                        Branch to use for generating diff. If not specified, 
tracking branch is used. If there is no tracking branch, error will be thrown.
  -jid JIRA_ID, --jira-id JIRA_ID
                        Jira id of the issue. If set, we deduce next patch 
version from attachments in the jira and also upload the new patch. Script will 
ask for jira username/password for authentication. If not set, patch is named 
<branch>_v0.patch.
  -srb, --skip-review-board
                        Don't create/update the review board.
  --reviewers REVIEWERS
                        Comma separated list of users to add as reviewers.
  --patch-dir PATCH_DIR
                        Directory to store patch files. If it doesn't exist, it 
will be created. Default: ~/patches
  --rb-repo RB_REPO     Review board repository. Default: hbase-git

To avoid having to enter jira/review board username/password every time, setup 
an encrypted ~/.apache-cred files as follows:
1) Create a file with following single line:
{"jira_username" : "appy", "jira_password":"123", "rb_username":"appy", 
"rb_password" : "@#$"}
2) Encrypt it with openssl.
openssl enc -aes-256-cbc -in <file> -out ~/.apache-creds
3) Delete original file.
Now onwards, you'll need to enter this encryption key only once per run. If you 
forget the key, simply regenerate ~/.apache-cred file again.
{code}

> Get object
> ----------
>
>                 Key: HBASE-15893
>                 URL: https://issues.apache.org/jira/browse/HBASE-15893
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Sudeep Sunthankar
>         Attachments: HBASE-15893.HBASE-14850.v1.patch
>
>
> Patch for creating Get objects.  Get objects can be passed to the Table 
> implementation to fetch results for a given row. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to