great, lgtm!
On Thu, Apr 25, 2013 at 9:11 PM, Stack st...@duboce.net wrote:
Did as you suggest Jon in https://issues.apache.org/jira/browse/HBASE-8444
St.Ack
On Thu, Apr 25, 2013 at 5:21 PM, Jonathan Hsieh j...@cloudera.com wrote:
Want to add 1.0.3 and keep a 1.0.0-1.0.2 lines as is (if
Is there a valid reason for using a Hadoop version older than 1.0.3 if
compiling up your own deploy?
On Wed, Apr 24, 2013 at 6:29 PM, Enis Söztutar enis@gmail.com wrote:
While trying with older Hadoop versions, I noticed that we do not compile
against hadoop versions older than 1.0.3.
I
The only reason I see is that you might be stuck with an older version of
Hadoop for some other reason.
Enis
On Thu, Apr 25, 2013 at 11:13 AM, Andrew Purtell apurt...@apache.orgwrote:
Is there a valid reason for using a Hadoop version older than 1.0.3 if
compiling up your own deploy?
On
Sure. That's the question I have too: Is there anything about 1.0.3 or
later which would be an incompatibility with 1.0.0 - 1.0.2 or prevent a
rolling upgrade?
On Thu, Apr 25, 2013 at 11:22 AM, Enis Söztutar enis@gmail.com wrote:
The only reason I see is that you might be stuck with an
No, not that I know of.
That's why I suggested that one option to dealing with this issue is to
just document this case, and move on.
Enis
On Thu, Apr 25, 2013 at 11:28 AM, Andrew Purtell apurt...@apache.orgwrote:
Sure. That's the question I have too: Is there anything about 1.0.3 or
later
Doc'ing it seems good to me. Here is a suggested change (if good, i'll
commit against an issue so we have a note of what Enis found):
durruti:trunk stack$ svn diff --force src/main/docbkx/
Index: src/main/docbkx/configuration.xml
Want to add 1.0.3 and keep a 1.0.0-1.0.2 lines as is (if they are valid).
might want to rename 0.96 to 0.95 and possibly add a trunk column?
On Thu, Apr 25, 2013 at 4:59 PM, Stack st...@duboce.net wrote:
Doc'ing it seems good to me. Here is a suggested change (if good, i'll
commit against
While trying with older Hadoop versions, I noticed that we do not compile
against hadoop versions older than 1.0.3.
I think the programmatic kerberos jaas configuration broke the compat:
The error is:
[ERROR]