| Summary: | [patch] databases/hbase: Update to 1.2.0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Kevin Bowling <kbowling> | ||||||
| Component: | Individual Port(s) | Assignee: | Dmitry Sivachenko <demon> | ||||||
| Status: | Closed FIXED | ||||||||
| Severity: | Affects Only Me | CC: | demon | ||||||
| Priority: | --- | Keywords: | patch | ||||||
| Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(demon) |
||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
|
Description
Kevin Bowling
2016-02-28 03:15:19 UTC
Created attachment 167499 [details]
hbase 1.2.0 patch JDK7
Fall back to JDK7, I think hadoop2 port would need to come along for the JDK8 ride the way things are currently set up.
Ok, I've completed live testing. The second JDK7 patch is safe. The other one can introduce opaque problems where native is used, for instance I had some LZ4 tables and HBase running on JDK8 could not use the Hadoop2 JDK7 build for that. I would advise applying the JDK7 of my patch until we can figure out how to move hadoop2 to JDK8. Apache's site lists 1.1.3 as stable. Why to update to 1.2? If you are just talking about the symlink in FTP that is an oversight. The next notable release will be 2.0 which should have a port copy, otherwise we should closely follow the minor versions. Please commit this is a solid release with no serious regressions from 1.1 A commit references this bug: Author: demon Date: Sat Mar 19 22:01:44 UTC 2016 New revision: 411424 URL: https://svnweb.freebsd.org/changeset/ports/411424 Log: Update to version 1.2.0 PR: 207549 Submitted by: Kevin Bowling <kbowling@freebsd.org> Changes: head/databases/hbase/Makefile head/databases/hbase/distinfo head/databases/hbase/files/extra-patch-hbase-annotations-pom.xml head/databases/hbase/pkg-plist Port updated. Thanks for submission and sorry for the delay! |