[jira] [Created] (HBASE-5522) hbase 0.92 test artifacts are missing from Maven central

2012-03-05 Thread Roman Shaposhnik (Created) (JIRA) 
hbase 0.92 test artifacts are missing from Maven central


 Key: HBASE-5522
 URL: https://issues.apache.org/jira/browse/HBASE-5522
 Project: HBase
  Issue Type: Bug
  Components: build
Affects Versions: 0.92.0
Reporter: Roman Shaposhnik


Could someone with enough karma, please, publish the test artifacts for 0.92.0?

--
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] [Created] (HBASE-5284) TestLogRolling.java doesn't compile against the latest 0.23.1-SNAPSHOT

2012-01-26 Thread Roman Shaposhnik (Created) (JIRA) 
TestLogRolling.java doesn't compile against the latest 0.23.1-SNAPSHOT
--

 Key: HBASE-5284
 URL: https://issues.apache.org/jira/browse/HBASE-5284
 Project: HBase
  Issue Type: Bug
  Components: test
Affects Versions: 0.92.0
Reporter: Roman Shaposhnik


Here's how to reproduce:

{noformat}
$ mvn clean -DskipTests -Dhadoop.profile=23 -Dinstall site assembly:assembly 
-Dmaven.repo.local=/home/rvs/.m2/repository

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:testCompile 
(default-testCompile) on project hbase: Compilation failure
[ERROR] 
/home/rvs/src/bigtop/output/hbase/hbase-0.92.0/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRolling.java:[341,33]
 cannot find symbol
[ERROR] symbol  : variable dnRegistration
[ERROR] location: class org.apache.hadoop.hdfs.server.datanode.DataNode
[ERROR] - [Help 1]
{noformat}

--
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] [Created] (HBASE-5286) bin/hbase's logic of adding Hadoop jar files to the classpath is fragile when presented with split packaged Hadoop 0.23 installation

2012-01-26 Thread Roman Shaposhnik (Created) (JIRA) 
bin/hbase's logic of adding Hadoop jar files to the classpath is fragile when 
presented with split packaged Hadoop 0.23 installation


 Key: HBASE-5286
 URL: https://issues.apache.org/jira/browse/HBASE-5286
 Project: HBase
  Issue Type: Bug
  Components: scripts
Affects Versions: 0.92.0
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik


Here's the bit from bin/hbase that might need TLC now that Hadoop can be 
spotted in the wild in split-package configuration:

{noformat}
#If avail, add Hadoop to the CLASSPATH and to the JAVA_LIBRARY_PATH
if [ ! -z $HADOOP_HOME ]; then
  HADOOPCPPATH=
  if [ -z $HADOOP_CONF_DIR ]; then
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} ${HADOOP_HOME}/conf)
  else
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} ${HADOOP_CONF_DIR})
  fi
  if [ `echo ${HADOOP_HOME}/hadoop-core*.jar` != 
${HADOOP_HOME}/hadoop-core*.jar ] ; then
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} `ls 
${HADOOP_HOME}/hadoop-core*.jar | head -1`)
  else
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} `ls 
${HADOOP_HOME}/hadoop-common*.jar | head -1`)
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} `ls 
${HADOOP_HOME}/hadoop-hdfs*.jar | head -1`)
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} `ls 
${HADOOP_HOME}/hadoop-mapred*.jar | head -1`)
  fi
{noformat}

There's a couple of issues with the above code:
   0. HADOOP_HOME is now deprecated in Hadoop 0.23
   1. the list of jar files added to the class-path should be revised
   2. we need to figure out a more robust way to get the jar files that are 
needed to the classpath (things like hadoop-mapred*.jar tend to match src/test 
jars as well)

Better yet, it would be useful to look into whether we can transition HBase's 
bin/hbase onto using bin/hadoop as a launcher script instead of direct JAVA 
invocations (Pig, Hive, Sqoop and Mahout already do that)

--
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] [Created] (HBASE-5068) RC1 can not build its hadoop-0.23 profile

2011-12-19 Thread Roman Shaposhnik (Created) (JIRA) 
RC1 can not build its hadoop-0.23 profile
-

 Key: HBASE-5068
 URL: https://issues.apache.org/jira/browse/HBASE-5068
 Project: HBase
  Issue Type: Bug
  Components: build
Affects Versions: 0.92.0
Reporter: Roman Shaposhnik
 Attachments: HBASE-5068.patch.txt

The hadoop .23 version needs to be bumped to 0.23.1-SNAPSHOT

--
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] [Created] (HBASE-4850) hbase tests need to be made Hadoop version agnostic

2011-11-22 Thread Roman Shaposhnik (Created) (JIRA) 
hbase tests need to be made Hadoop version agnostic
---

 Key: HBASE-4850
 URL: https://issues.apache.org/jira/browse/HBASE-4850
 Project: HBase
  Issue Type: Improvement
  Components: test
Affects Versions: 0.92.0, 0.94.0, 0.92.1
Reporter: Roman Shaposhnik


Currently it is possible to have a single hbase jar that can work with multiple 
versions of Hadoop. It would be nice if hbase-test.jar also followed the suit. 
For now I'm aware of the following problems (but there could be more):

1. org.apache.hadoop.hbase.mapreduce.NMapInputFormat is failing because
org.apache.hadoop.mapreduce.JobContext is either class or interface
depending on which version of Hadoop you compile it against.



--
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] [Created] (HBASE-4851) hadoop maven dependency needs to be an optional one

2011-11-22 Thread Roman Shaposhnik (Created) (JIRA) 
hadoop maven dependency needs to be an optional one
---

 Key: HBASE-4851
 URL: https://issues.apache.org/jira/browse/HBASE-4851
 Project: HBase
  Issue Type: Improvement
  Components: build
Affects Versions: 0.92.0, 0.94.0, 0.92.1
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik


Given that HBase 0.92/0.94 is likely to be used with at least 3 different 
versions of Hadoop (0.20, 0.22 and 0.23) it seems appropriate to make hadoop 
maven dependencies into optional ones (IOW, the build of HBase will see NO 
changes in behavior, but any component that has HBase as a dependency will be 
in control of what version of Hadoop gets used).

--
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] [Created] (HBASE-4854) it seems that CLASSPATH elements coming from Hadoop change HBase behaviour

2011-11-22 Thread Roman Shaposhnik (Created) (JIRA) 
it seems that CLASSPATH elements coming from Hadoop change HBase behaviour
--

 Key: HBASE-4854
 URL: https://issues.apache.org/jira/browse/HBASE-4854
 Project: HBase
  Issue Type: Bug
  Components: shell
Affects Versions: 0.92.0
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik


It looks like HBASE-3465 introduced a slight change in behavior. The ordering 
of classpath elements makes Hadoop ones go before the HBase ones, which leads 
to log4j properties picked up from the wrong place, etc. It seems that the 
easies way to fix that would be to revert the ordering of classpath.

--
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] [Created] (HBASE-4719) HBase script assumes pre-Hadoop 0.21 layout of jar files

2011-11-01 Thread Roman Shaposhnik (Created) (JIRA) 
HBase script assumes pre-Hadoop 0.21 layout of jar files


 Key: HBASE-4719
 URL: https://issues.apache.org/jira/browse/HBASE-4719
 Project: HBase
  Issue Type: Bug
  Components: scripts
Affects Versions: 0.92.0
Reporter: Roman Shaposhnik


The following in the bin/hbase:

{noformat}
HADOOPCPPATH=$(append_path ${HADOOPCPPATH} `ls 
${HADOOP_HOME}/hadoop-core*.jar`)
{noformat}

assumes a pre-21 Hadoop layout. It'll be better to dynamically account for 
either hadoop-core* or hadoop-common*, hadoop-hdfs*, hadoop-mapreduce*


--
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] [Created] (HBASE-4526) special case for stopping master in hbase-daemon.sh is no longer required

2011-09-30 Thread Roman Shaposhnik (Created) (JIRA) 
special case for stopping master in hbase-daemon.sh is no longer required
-

 Key: HBASE-4526
 URL: https://issues.apache.org/jira/browse/HBASE-4526
 Project: HBase
  Issue Type: Bug
  Components: scripts
Affects Versions: 0.90.4
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Priority: Minor


Now that HBASE-4209 is finally done (many thanks to stack for help and 
encouragement!) I don't think there's any reason to keep this bit of code in 
hbase-daemon.sh:

{noformat}
if [ $command = master ]; then
  echo `date` Killing $command  $loglog
  kill -9 `cat $pid`  /dev/null 21
else
  echo `date` Killing $command  $loglog
  kill `cat $pid`  /dev/null 21
fi
{noformat}

I suggest we remove the special case completely, since I don't think it serves 
any useful purpose (patch attached).

Now, as an additional precautionary measure. We can try to follow up with a 
SIGKILL once a certain timeout expires.
Let me know if you think it is necessary to do so and I'll update the patch.

--
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