You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2012/05/16 09:32:09 UTC
[jira] [Created] (BOOKKEEPER-262) Implement a meta store based
hedwig metadata manager.
Sijie Guo created BOOKKEEPER-262:
------------------------------------
Summary: Implement a meta store based hedwig metadata manager.
Key: BOOKKEEPER-262
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-262
Project: Bookkeeper
Issue Type: Sub-task
Components: hedwig-server
Reporter: Sijie Guo
Fix For: 4.2.0
We had provided a metadata manager interface by BOOKKEEPER-250 & BOOKKEEPER-259. we need a metadata manager implementation use meta store API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BOOKKEEPER-262) Implement a meta store based
hedwig metadata manager.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504586#comment-13504586 ]
Hadoop QA commented on BOOKKEEPER-262:
--------------------------------------
Testing JIRA BOOKKEEPER-262
WARNING: Running test-patch on a dirty local svn workspace
Patch <a href="/jira/secure/attachment/12553314/BOOKKEEPER-262.diff">/jira/secure/attachment/12553314/BOOKKEEPER-262.diff</a> downloaded at Tue Nov 27 12:34:31 UTC 2012
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 14 line(s) longer than 120 characters
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
. {color:red}WARNING{color}: the current HEAD has 8 Javadoc warning(s)
{color:red}-1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:red}-1{color} patch does not compile
. {color:green}+1{color} the patch does not seem to introduce new javac warnings
. {color:red}WARNING{color}: the current HEAD has 9 javac warning(s)
{color:green}+1 FINDBUGS{color}
. {color:green}+1{color} the patch does not seem to introduce new Findbugs warnings
. {color:red}WARNING: the current HEAD has Findbugs warning(s), they should be addressed ASAP{color}
{color:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
. {color:red}-1{color} distro tarball fails with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/34/
> Implement a meta store based hedwig metadata manager.
> -----------------------------------------------------
>
> Key: BOOKKEEPER-262
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-262
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: hedwig-server
> Reporter: Sijie Guo
> Assignee: Jiannan Wang
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-262.diff
>
>
> We had provided a metadata manager interface by BOOKKEEPER-250 & BOOKKEEPER-259. we need a metadata manager implementation use meta store API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BOOKKEEPER-262) Implement a meta store based
hedwig metadata manager.
Posted by "Jiannan Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiannan Wang updated BOOKKEEPER-262:
------------------------------------
Assignee: Jiannan Wang
> Implement a meta store based hedwig metadata manager.
> -----------------------------------------------------
>
> Key: BOOKKEEPER-262
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-262
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: hedwig-server
> Reporter: Sijie Guo
> Assignee: Jiannan Wang
> Fix For: 4.2.0
>
>
> We had provided a metadata manager interface by BOOKKEEPER-250 & BOOKKEEPER-259. we need a metadata manager implementation use meta store API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BOOKKEEPER-262) Implement a meta store based
hedwig metadata manager.
Posted by "Jiannan Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiannan Wang updated BOOKKEEPER-262:
------------------------------------
Attachment: BOOKKEEPER-262.diff
Attach an implementation patch. Also post it in review board:
https://reviews.apache.org/r/8038/
> Implement a meta store based hedwig metadata manager.
> -----------------------------------------------------
>
> Key: BOOKKEEPER-262
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-262
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: hedwig-server
> Reporter: Sijie Guo
> Assignee: Jiannan Wang
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-262.diff
>
>
> We had provided a metadata manager interface by BOOKKEEPER-250 & BOOKKEEPER-259. we need a metadata manager implementation use meta store API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira