[jira] [Created] (HBASE-12297) Support DBB usage in Bloom and HFileIndex area
Anoop Sam John created HBASE-12297: -- Summary: Support DBB usage in Bloom and HFileIndex area Key: HBASE-12297 URL: https://issues.apache.org/jira/browse/HBASE-12297 Project: HBase Issue Type: Sub-task Reporter: Anoop Sam John Assignee: Anoop Sam John -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12298) Support DBB usage in PrefixTree
Anoop Sam John created HBASE-12298: -- Summary: Support DBB usage in PrefixTree Key: HBASE-12298 URL: https://issues.apache.org/jira/browse/HBASE-12298 Project: HBase Issue Type: Sub-task Reporter: Anoop Sam John Assignee: ramkrishna.s.vasudevan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12300) Hadoop QA should attempt to execute common Maven goals
Dima Spivak created HBASE-12300: --- Summary: Hadoop QA should attempt to execute common Maven goals Key: HBASE-12300 URL: https://issues.apache.org/jira/browse/HBASE-12300 Project: HBase Issue Type: Test Components: test Reporter: Dima Spivak HBASE-12299 and HBASE-12294 have exposed a hole in our pre-commit testing; we need to confirm that commits don't break common Maven goals (like those used to build documentation and assemble HBase). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12301) user_permission command does not show global permissions
Jerry He created HBASE-12301:
Summary: user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions on
the hbase:acl table.
Anyway we need a way to show the global permissions as part of user_permission
request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12302) VisibilityClient getAuths does not propagate remote service exception correctly
Jerry He created HBASE-12302:
Summary: VisibilityClient getAuths does not propagate remote
service exception correctly
Key: HBASE-12302
URL: https://issues.apache.org/jira/browse/HBASE-12302
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 0.98.7, 2.0.0
Reporter: Jerry He
Priority: Minor
Fix For: 2.0.0, 0.98.8
From hbase shell, run 'get_auths' with a non-superuser:
{code}
hbase(main):002:0 get_auths 'user2'
ERROR:
Here is some help for this command:
Get the visibility labels set for a particular user
Syntax : get_auths 'user1'
For example:
hbase get_auths 'user1'
{code}
We should expect a AccessDeniedException from the server.
From a Java client, AccessDeniedException was dumped out, but the end
exception is
{code}
java.util.NoSuchElementException
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1124)
at java.util.TreeMap$ValueIterator.next(TreeMap.java:1171)
at
org.apache.hadoop.hbase.security.visibility.VisibilityClient.getAuths(VisibilityClient.java:148)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (HBASE-12294) Can't build the docs after the hbase-checkstyle module was added
[
https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark reopened HBASE-12294:
---
Seems like adding the parent back is the only thing that will work. I think
this breaks older mavens 2.x (they are pretty ancient now). Worth it? or should
we just revert this whole debacle ?
Can't build the docs after the hbase-checkstyle module was added
Key: HBASE-12294
URL: https://issues.apache.org/jira/browse/HBASE-12294
Project: HBase
Issue Type: Bug
Components: build
Reporter: Misty Stanley-Jones
Assignee: Elliott Clark
Priority: Blocker
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: 0001-HBASE-12294-Fix-site-generation.patch,
HBASE-12294.patch
Since the 15th, I have not been able to build the docs. I get these errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project
hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) - [Help 1]
{code}
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Missing
distribution management in project HBase - Checkstyle
(org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
I'm able to resolve it by adding the attached patch to the POM. [~eclark], is
there a specific reason you didn't use inheritance in the checkstyles module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
HBase code coverage
Hi Everyone, I'm trying to get the hbase UT code coverage report, using the built-in clover configuration, with the following mvn command: mvn clean test -fn -PrunLargeTests,hadoop-2.0,clover -Dzookeeper.version=3.4.5 -Dhadoop-two.version=2.4.1 mvn clover2:aggregate clover2:clover -Pclover HBase version: 0.98.5 No change is made to the POM file or source code. Unfortunately, the build always fails, as shown by the following log. I'm not sure if it's due to my improper mvn arguments or other reason. So could anyone help me on how to run hbase ut code coverage? [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [INFO] Reactor Summary: [INFO] [INFO] HBase . FAILURE [1.110s] [INFO] HBase - Common SKIPPED [INFO] HBase - Protocol .. SKIPPED [INFO] HBase - Client SKIPPED [INFO] HBase - Hadoop Compatibility .. SKIPPED [INFO] HBase - Hadoop Two Compatibility .. SKIPPED [INFO] HBase - Prefix Tree ... SKIPPED [INFO] HBase - Server SKIPPED [INFO] HBase - Testing Util .. SKIPPED [INFO] HBase - Thrift SKIPPED [INFO] HBase - Shell . SKIPPED [INFO] HBase - Integration Tests . SKIPPED [INFO] HBase - Examples .. SKIPPED [INFO] HBase - Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 26.648s [INFO] Finished at: Mon Oct 20 08:57:46 PDT 2014 [INFO] Final Memory: 38M/1428M [INFO] [ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-clover2-plugin:2.6.3:clover (default-cli) on project hbase: An error has occurred in Clover report generation. Could not resolve report descriptor: /data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar: Failed to load resource as file [/data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar]: Could not find resource '/data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar'. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Build step 'Execute shell' marked build as failure
Re: HBase code coverage
In one of recent Jiras, Jacoco code coverage plugin was added to the pom. Now you can get code coverage using the following command line : mvn clean install -DskipTests ; mvn clean package -Dhbase.skip-jacoco=false Best, Manukranth. On Mon, Oct 20, 2014 at 5:30 PM, 肖春君 chunjun.x...@hotmail.com wrote: Hi Everyone, I'm trying to get the hbase UT code coverage report, using the built-in clover configuration, with the following mvn command: mvn clean test -fn -PrunLargeTests,hadoop-2.0,clover -Dzookeeper.version=3.4.5 -Dhadoop-two.version=2.4.1 mvn clover2:aggregate clover2:clover -Pclover HBase version: 0.98.5 No change is made to the POM file or source code. Unfortunately, the build always fails, as shown by the following log. I'm not sure if it's due to my improper mvn arguments or other reason. So could anyone help me on how to run hbase ut code coverage? [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [INFO] Reactor Summary: [INFO] [INFO] HBase . FAILURE [1.110s] [INFO] HBase - Common SKIPPED [INFO] HBase - Protocol .. SKIPPED [INFO] HBase - Client SKIPPED [INFO] HBase - Hadoop Compatibility .. SKIPPED [INFO] HBase - Hadoop Two Compatibility .. SKIPPED [INFO] HBase - Prefix Tree ... SKIPPED [INFO] HBase - Server SKIPPED [INFO] HBase - Testing Util .. SKIPPED [INFO] HBase - Thrift SKIPPED [INFO] HBase - Shell . SKIPPED [INFO] HBase - Integration Tests . SKIPPED [INFO] HBase - Examples .. SKIPPED [INFO] HBase - Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 26.648s [INFO] Finished at: Mon Oct 20 08:57:46 PDT 2014 [INFO] Final Memory: 38M/1428M [INFO] [ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-clover2-plugin:2.6.3:clover (default-cli) on project hbase: An error has occurred in Clover report generation. Could not resolve report descriptor: /data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar: Failed to load resource as file [/data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar]: Could not find resource '/data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar'. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Build step 'Execute shell' marked build as failure -- Manukranth Kolloju
Re: HBase code coverage
The following JIRA introduced jacoco code coverage report: https://issues.apache.org/jira/browse/HBASE-12208 Can you use that ? Cheers On Mon, Oct 20, 2014 at 5:30 PM, 肖春君 chunjun.x...@hotmail.com wrote: Hi Everyone, I'm trying to get the hbase UT code coverage report, using the built-in clover configuration, with the following mvn command: mvn clean test -fn -PrunLargeTests,hadoop-2.0,clover -Dzookeeper.version=3.4.5 -Dhadoop-two.version=2.4.1 mvn clover2:aggregate clover2:clover -Pclover HBase version: 0.98.5 No change is made to the POM file or source code. Unfortunately, the build always fails, as shown by the following log. I'm not sure if it's due to my improper mvn arguments or other reason. So could anyone help me on how to run hbase ut code coverage? [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [INFO] Reactor Summary: [INFO] [INFO] HBase . FAILURE [1.110s] [INFO] HBase - Common SKIPPED [INFO] HBase - Protocol .. SKIPPED [INFO] HBase - Client SKIPPED [INFO] HBase - Hadoop Compatibility .. SKIPPED [INFO] HBase - Hadoop Two Compatibility .. SKIPPED [INFO] HBase - Prefix Tree ... SKIPPED [INFO] HBase - Server SKIPPED [INFO] HBase - Testing Util .. SKIPPED [INFO] HBase - Thrift SKIPPED [INFO] HBase - Shell . SKIPPED [INFO] HBase - Integration Tests . SKIPPED [INFO] HBase - Examples .. SKIPPED [INFO] HBase - Assembly .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 26.648s [INFO] Finished at: Mon Oct 20 08:57:46 PDT 2014 [INFO] Final Memory: 38M/1428M [INFO] [ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-clover2-plugin:2.6.3:clover (default-cli) on project hbase: An error has occurred in Clover report generation. Could not resolve report descriptor: /data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar: Failed to load resource as file [/data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar]: Could not find resource '/data/jenkins/workspace/hbase-0_98_5-UT/maven-clover2-plugin-2.6.3.jar'. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Build step 'Execute shell' marked build as failure
[jira] [Created] (HBASE-12303) Seek to next row after family delete markers
Lars Hofhansl created HBASE-12303: - Summary: Seek to next row after family delete markers Key: HBASE-12303 URL: https://issues.apache.org/jira/browse/HBASE-12303 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Currently we seek to the next column when we encounter a family delete marker. I think we safely seek the current store to next row. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Any strong feelings about Maven versions?
The version of Maven we require for building came up in a comment on HBASE-12294[1]. Before I file a patch to add an enforcer line in the pom, does anyone have any strong concerns one way or another on what version it's set to? FWIW, most of our jenkins jobs currently run on 3.0.3 (trunk, 0.98). The 0.94 related builds pick Maven 3 (latest), and I suspect the precommit job uses latest since it just relies on the path. The latest available on asf jenkins appears to be 3.2.1. [1]: *http://s.apache.org/4JGP http://s.apache.org/4JGP* -- Sean
