[
https://issues.apache.org/jira/browse/EAGLE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429972#comment-15429972
]
ASF GitHub Bot commented on EAGLE-472:
--------------------------------------
Github user baibaichen commented on the issue:
https://github.com/apache/incubator-eagle/pull/357
This is the environment issue, for running in windows you need
1. let hadoop.dll could be loaded, this is usually done by setting path
variable or manually set library path, i,e,
**-Djava.library.path=D:\Devtool\hadoop-util\bin**
2 To avoid path exceeding 255, run with
**-Dtest.build.data.basedirectory=d:\t** ,
> Fix HBase unit test
> --------------------
>
> Key: EAGLE-472
> URL: https://issues.apache.org/jira/browse/EAGLE-472
> Project: Eagle
> Issue Type: Sub-task
> Affects Versions: v0.5.0
> Reporter: Chang chen
> Assignee: Chang chen
> Labels: test
> Fix For: v0.5.0
>
>
> HBase UT is broken due to wrong configuration and guava conflict
> # [EAGLE-331 ingestion+alert engine
> preview|https://github.com/apache/incubator-eagle/commit/eef4930c3b9cac7d8c596af684ba098ec2b2229d],
> see what is added in EmbeddedHbase.java. To Fix it, we needn't specify
> *hbase.master.ipc.address*, using default value is fine, which is 0.0.0.0,
> means all IPv4 addresses on the local machine. Please note RegionServer will
> not use 127.0.0.1 and localhost to contact master.
> # [Rebase code
> base|https://github.com/apache/incubator-eagle/commit/72a1501c3ff645d93067b4fd9907f8183c2763b6]
> , guava is upgraded to *19.0*, however the dependent HBase
> version(0.98.4.2.2.5.1-3-hadoop2) uses 12.01. It is OK in product
> environment, but failed in UT, see HBASE-11694. To Fix it, we can downgrade
> to guava 15.0 which works for eagle(*Stopwatch.createStarted*) and
> HBase(*StopWatch.elapsedMillis*)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
