You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2013/12/13 22:56:07 UTC

[jira] [Comment Edited] (HBASE-10150) Write attachment Id of tested patch into JIRA comment

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

Ted Yu edited comment on HBASE-10150 at 12/13/13 9:54 PM:
----------------------------------------------------------

Consider this scenario:
patch A was tested on day 1.
On day 2, the following attachments are made, in this order:
* patchB
* design-doc.pdf

Retrieving latest attachment wouldn't pass filter, to be activated in HBASE-10044
When we get to patchB, we need to know whether it has been tested - this is done by searching for attachment Id of patchB in JIRA text.

Does this answer your question ?


was (Author: yuzhihong@gmail.com):
Consider this scenario:
patch A was tested on day 1.
On day 2, the following attachments are made, in this order:
* patchB
* design-doc.pdf
Retrieving latest attachment wouldn't pass filter, to be activated in HBASE-10044
When we get to patchB, we need to know whether it has been tested - this is done by searching for attachment Id of patchB in JIRA text.

Does this answer your question ?

> Write attachment Id of tested patch into JIRA comment
> -----------------------------------------------------
>
>                 Key: HBASE-10150
>                 URL: https://issues.apache.org/jira/browse/HBASE-10150
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 0.99.0
>
>         Attachments: 10150-v1.txt
>
>
> The optimization proposed in HBASE-10044 wouldn't work if QA bot doesn't know the attachment Id of the most recently tested patch.
> The first step is to write attachment Id of tested patch into JIRA comment.
> For details, see HADOOP-10163



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)