[
https://issues.apache.org/jira/browse/HBASE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044383#comment-13044383
]
stack commented on HBASE-3873:
------------------------------
Much smoother running. This is great. Do you think we should actually ship
with snappy binaries, now its so easy to produce them (Your patch has a cdh
reference in it but easy fix which I can make on commit)? Asking because I
want to commit a bit of documentation on this new feature at same time. Thanks
A.
Here is something I ran into that you might be interested in building
hadoop-snappy.
After a clean build, I tried to rerun it and its weird that clean can't delete
the target dir... you know what that is about? (I can do a rm -rf on the
target dir as myself)
mvn clean install:
{code}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to delete directory: /home/stack/hadoop-snappy-read-only/target.
Reason: Unable to delete directory
/home/stack/hadoop-snappy-read-only/target/hadoop-snappy-0.0.1-SNAPSHOT-tar/hadoop-snappy-0.0.1-SNAPSHOT/lib/native/Linux-amd64-64
{code}
> Mavenize Hadoop Snappy JAR/SOs project dependencies
> ---------------------------------------------------
>
> Key: HBASE-3873
> URL: https://issues.apache.org/jira/browse/HBASE-3873
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.90.2
> Environment: Linux
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Labels: build
> Attachments: HBASE-3873.patch, HBASE-3873.patch
>
>
> (This JIRA builds on HBASE-3691)
> I'm working on simplifying how to use Hadoop Snappy from other based maven
> projects. The idea is that hadoop-snappy JAR and the SOs (snappy and
> hadoop-snappy) would be picked up from a Maven repository (like any other
> dependencies). SO files will be picked up based on the architecture where the
> build is running (32 or 64 bits).
> For Hbase this would remove the need to manually copy snappy JAR and SOs
> (snappy and hadoop-snappy) into HADOOP_HOME/lib or HBASE_HOME/lib and
> hadoop-snappy would be handled as a regular maven dependency (with a trick
> for the SOs file).
> The changes would affect only the pom.xml and the would be in a 'snappy'
> profile, thus requiring '-Dsnappy' option in Maven invocations to trigger the
> including of snappy JAR and SOs.
> Because hadoop-snappy (JAR and SOs) are not currently avail in public Maven
> repos, until that happens, Hbase developer would have to checkout and 'mvn
> install' hadoop-snappy. Which is (IMO) simpler than what will have to be done
> in once HBASE-3691 is committed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
