[jira] [Resolved] (HBASE-11386) Replication#table,CF config will be wrong if the table name includes namespace
[
https://issues.apache.org/jira/browse/HBASE-11386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-11386.
Resolution: Duplicate
Resolved by HBASE-11393 and HBASE-16653.
> Replication#table,CF config will be wrong if the table name includes namespace
> --
>
> Key: HBASE-11386
> URL: https://issues.apache.org/jira/browse/HBASE-11386
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Reporter: Qianxi Zhang
>Assignee: Ashish Singhi
>Priority: Critical
> Fix For: 1.5.0
>
> Attachments: HBASE_11386_trunk_v1.patch, HBASE_11386_trunk_v2.patch
>
>
> Now we can config the table and CF in Replication, but I think the parse will
> be wrong if the table name includes namespace
> ReplicationPeer#parseTableCFsFromConfig(line 125)
> {code}
> Map> tableCFsMap = null;
> // parse out (table, cf-list) pairs from tableCFsConfig
> // format: "table1:cf1,cf2;table2:cfA,cfB"
> String[] tables = tableCFsConfig.split(";");
> for (String tab : tables) {
> // 1 ignore empty table config
> tab = tab.trim();
> if (tab.length() == 0) {
> continue;
> }
> // 2 split to "table" and "cf1,cf2"
> // for each table: "table:cf1,cf2" or "table"
> String[] pair = tab.split(":");
> String tabName = pair[0].trim();
> if (pair.length > 2 || tabName.length() == 0) {
> LOG.error("ignore invalid tableCFs setting: " + tab);
> continue;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: [DISCUSS] Becoming a Committer
I’m a good case study here. I have contributed a lot to the HBase project but almost none of it code. But I’ve helped move the project forward and I think I’ve added value. I wouldn’t have been considered for the PMC without the commit bit even though almost nothing I’m doing in the PMC capacity required a commit bit. So clearly the commit bit has significance apart from the actual ability to commit code or to specifically write Java. I’d argue that more physical code is not necessarily what makes a project great. On Thu, Nov 9, 2017 at 1:31 PM Josh Elser wrote: > Hey Csaba, > > I think you might be falling into a common-trap :). A committer's > "status" is often acquired via repeated contributions of code to a > project -- you're absolutely right. This stems from the fact that, most > times, people contribute to a project via code. Committership (for > HBase) is commonly helping contributors do more without needing the help > of others. Committership can also be looked at as a stepping stone > towards PMC. > > This discuss was more about how the HBase project acknowledges that > contributions can come in various forms. As such, the path to "merit" > doesn't have to only be achieved via code contributions. There's nothing > wrong with this, from both an HBase and an ASF perspective. I think you > have a good number of people here that would happily vote in the > positive for individuals who contribute (in some of the ways listed > below) to become a PMC member, charged with the guidance and health of > the project. > > In short, "committer" and "PMC" are really just plateaus given to folks > in recognition of their contributions, regardless of form. What were > trying to do was be more explicit about the various definitions of > "contribution" we hold. Does this help clarify it? > > - Josh > > On 11/9/17 11:41 AM, Csaba Skrabak wrote: > > Wow, this list just made me think. Is the Committer status clearly a > reward for contributing in any way? Or is it a very pragmatic decision by > the PMC that some fellow needs right to commit? I think it's kind of both > but the ratio should be clear and consensual. > > > > People who answer questions, file issues, write blogs, demo applications > and do stuff that does not involve coding, they can continue helping the > community just fine without a Committer title. Maybe PMC could invent a Big > Thank You event for them but not give the Committer status. Or just give > them a Committer status because why not? > > > > > > > > > > On 21/09/17 22:41, "Misty Stanley-Jones" wrote: > > > >> I feel like I inject this note into all discussions like this, but I'm > >> going to do it again. "Act like a committer" does not ONLY mean to > produce > >> code for HBase. It means to support the project. This may mean any of > the > >> following, plus a long list of other things I'm sure I'm not thinking of > >> right now: > >> > >> - Contribute to the docs (yay!) > >> - Help fix and improve testing > >> - Participate in release candidate votes, even if non-binding > >> - Review other people's work > >> - Help newbies > >> - Answer questions > >> - Update the website > >> - File issues > >> - Mentor new contributors of all sorts > >> - Give talks about HBase > >> - Write blogs about HBase > >> - Participate in design discussions > >> - Provide UX feedback > >> - Write demo applications > >> - Help us attract and retain a diverse community > >> - Interact with other projects in ways that benefit HBase and those > other > >> projects > >> > >> I would personally consider all of these bullet points to be super > >> significant in "act like a committer" type discussions. I think that > >> contributing code is only one aspect. For some reason it seems to be the > >> most appealing aspect to lots of people, but IMHO that makes for a poor > >> community experience. > >> > >> On Wed, Sep 20, 2017 at 11:48 AM, Mike Drob wrote: > >> > >>> Hi folks, > >>> > >>> I've been chatting with folks off and on about this for a while, and > was > >>> told that this made sense as a discussion on the dev@ list. > >>> > >>> How does the PMC select folks for committership? The most common > answer is > >>> that folks should 'act like a committer' but that's painfully nebulous > and > >>> easy to get sidetracked onto other topics. The problem is compounded > >>> because what may be great on one project is inconsistently applied on > other > >>> projects in the ASF, and yet we are all very tightly coupled as > communities > >>> and as project dependencies. > >>> > >>> Ideally, this is something that we can document in the book. Misty > gently > >>> pointed out > http://hbase.apache.org/book.html#_guide_for_hbase_committers > >>> but > >>> also noted that it's for what happens after somebody becomes a > committer. > >>> Still, if the standard is "act like one until you become one" then it's > >>> useful reading for people. Also, there doesn't seem to be any > guidelines > >>> like this for PMC. > >>> > >
Re: Failure: hbase.apache.org HTML Checker
Seems like transient problems with Jenkins. On Fri, Nov 10, 2017 at 5:10 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Failure > > Either the Jenkins job failed, or (more likely) HTML errors were found. > > Unless the Jenkins job itself failed, the HTML and link-checking report > for http://hbase.apache.org is available at > https://builds.apache.org/job/HBase%20Website%20Link%20Checker/122/artifact/link_report/index.html > . > > Otherwise, see > https://builds.apache.org/job/HBase%20Website%20Link%20Checker/122/console > .
[jira] [Created] (HBASE-19297) Nightly job for master timing out in unit tests
Sean Busbey created HBASE-19297: --- Summary: Nightly job for master timing out in unit tests Key: HBASE-19297 URL: https://issues.apache.org/jira/browse/HBASE-19297 Project: HBase Issue Type: Task Components: test Affects Versions: 3.0.0 Reporter: Sean Busbey Assignee: Sean Busbey master now timing out at 6 hours in master. looks like it was making progress still, just in the midst of hte hbase-rest module -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19296) Fix findbugs and error-prone warnings (branch-2)
Andrew Purtell created HBASE-19296: -- Summary: Fix findbugs and error-prone warnings (branch-2) Key: HBASE-19296 URL: https://issues.apache.org/jira/browse/HBASE-19296 Project: HBase Issue Type: Task Reporter: Andrew Purtell Assignee: Andrew Purtell Fix For: 2.0.0-beta-1 Fix important findbugs and error-prone warnings on branch-2 / master. Start with a forward port pass from HBASE-19239. Assume rejected hunks need a new analysis. Do that analysis. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (HBASE-19239) Fix findbugs and error-prone warnings (branch-1)
[ https://issues.apache.org/jira/browse/HBASE-19239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-19239. Resolution: Fixed Hadoop Flags: Reviewed Pushed to branch-1 and branch-1.4 > Fix findbugs and error-prone warnings (branch-1) > > > Key: HBASE-19239 > URL: https://issues.apache.org/jira/browse/HBASE-19239 > Project: HBase > Issue Type: Improvement >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 1.4.0 > > Attachments: HBASE-19239-branch-1.patch, HBASE-19239-branch-1.patch > > > Fix important findbugs and error-prone warnings on branch-1.4 / branch-1. > Forward port as appropriate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19295) The Configuration returned by CPEnv should be read-only.
stack created HBASE-19295: - Summary: The Configuration returned by CPEnv should be read-only. Key: HBASE-19295 URL: https://issues.apache.org/jira/browse/HBASE-19295 Project: HBase Issue Type: Task Reporter: stack The Configuration a CP gets when it does a getConfiguration on the environment is that of the RegionServer. The CP should not be able to modify this config. We should throw exception if they try to write us. Ditto w/ the Connection they can get from the env. They should not be able to close it at min. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19294) When user trying to create table , master is getting aborted in execution phase
chiranjeevi created HBASE-19294: --- Summary: When user trying to create table , master is getting aborted in execution phase Key: HBASE-19294 URL: https://issues.apache.org/jira/browse/HBASE-19294 Project: HBase Issue Type: Bug Components: hbase, master, proc-v2 Affects Versions: 1.3.1 Reporter: chiranjeevi when create table failed in execute phase master got aborted. DEBUG [RpcServer.FifoWFPBQ.default.handler=8,queue=3,port=16000] ipc.RpcServer: RpcServer.FifoWFPBQ.default.handler=8,queue=3,port=16000: callId: 443 service: MasterService methodName: ListTableDescriptorsByNamespace size: 51 connection: java.io.InterruptedIOException: Retry interrupted java.lang.RuntimeException: HMaster Aborted at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:239) at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:137) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126) at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:3207) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19293) Support add a disabled state replication peer directly
Guanghao Zhang created HBASE-19293: -- Summary: Support add a disabled state replication peer directly Key: HBASE-19293 URL: https://issues.apache.org/jira/browse/HBASE-19293 Project: HBase Issue Type: Improvement Reporter: Guanghao Zhang Now when add a replication peer, the default state is enabled. If you want add a disabled replication peer, you need add a peer first, then disable it. It need two step to finish now. Use case for add a disabled replication peer. When user want sync data from a cluster A to a new peer cluster. 1. Add a disabled replication peer. And config the table to peer config. 2. Take a snapshot of table and export snapshot to peer cluster. 3. Restore snapshot in peer cluster. 4. Enable the peer and wait all stuck replication log replicated to peer cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
