[jira] Resolved: (HBASE-3393) Update Avro gateway to use Avro 1.4.1 and the new server.join() method
[ https://issues.apache.org/jira/browse/HBASE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-3393. -- Resolution: Fixed Fix Version/s: 0.92.0 Hadoop Flags: [Reviewed] Applied to TRUNK. Thanks for the patch Jeff (and the amendment Lars). Let me know if you want it on branch though it probably doesn't belong there. > Update Avro gateway to use Avro 1.4.1 and the new server.join() method > -- > > Key: HBASE-3393 > URL: https://issues.apache.org/jira/browse/HBASE-3393 > Project: HBase > Issue Type: Sub-task > Components: avro >Reporter: Jeff Hammerbacher >Assignee: Jeff Hammerbacher > Fix For: 0.92.0 > > Attachments: HBASE-3393-2.patch, HBASE-3393-3.patch, HBASE-3393.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975706#action_12975706 ] Hudson commented on HBASE-3387: --- Integrated in HBase-TRUNK #1699 (See [https://hudson.apache.org/hudson/job/HBase-TRUNK/1699/]) HBASE-3387 Pair does not deep check arrays for equality > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Priority: Minor > Fix For: 0.90.1, 0.92.0 > > Attachments: HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-3387. -- Resolution: Fixed Committed to branch after tagging RC2 > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Priority: Minor > Fix For: 0.90.1, 0.92.0 > > Attachments: HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reopened HBASE-3387: -- Reopening to commit 0.90.1 > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Priority: Minor > Fix For: 0.90.1, 0.92.0 > > Attachments: HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-3387: - Resolution: Fixed Fix Version/s: 0.92.0 Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) Committed to TRUNK. Thanks for the patch Jesse. Will leave it in 0.90.1 bucket so it gets committed there too. > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Priority: Minor > Fix For: 0.90.1, 0.92.0 > > Attachments: HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated HBASE-3387: --- Attachment: HBASE-3387.patch Sorry about the non-working patch - turns out it was b/c git diff (at least in my setup) appends a/ and b/ to the directories of the original and new versions. This means that the patch will necessarily fail. Went back through, edited by hand and double checked that it works this time. Sorry again! > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Priority: Minor > Fix For: 0.90.1 > > Attachments: HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3387) Pair does not deep check arrays for equality.
[ https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse Yates updated HBASE-3387: --- Attachment: (was: HBASE-3387.patch) > Pair does not deep check arrays for equality. > -- > > Key: HBASE-3387 > URL: https://issues.apache.org/jira/browse/HBASE-3387 > Project: HBase > Issue Type: Bug > Components: util >Affects Versions: 0.90.1 > Environment: Any (discovered in Ubuntu 10.10 using TRUNK). >Reporter: Jesse Yates >Priority: Minor > Fix For: 0.90.1 > > Attachments: HBASE-3387.patch > > Original Estimate: 0h > Remaining Estimate: 0h > > Pair does not deep check arrays for equality. It merely does x.equals(y) for > the sent Object. However, with any type of array this is merely going to > compare the array pointers, rather than the underlying data structure. > It requires a rewriting of the private equals method in Pair to check for > elements being an array, then checking the underlying elements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3393) Update Avro gateway to use Avro 1.4.1 and the new server.join() method
[ https://issues.apache.org/jira/browse/HBASE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Hammerbacher updated HBASE-3393: - Attachment: HBASE-3393-3.patch This one should work. Tests pass, and I was able to use pyhbase to throw some data at a local cluster. > Update Avro gateway to use Avro 1.4.1 and the new server.join() method > -- > > Key: HBASE-3393 > URL: https://issues.apache.org/jira/browse/HBASE-3393 > Project: HBase > Issue Type: Sub-task > Components: avro >Reporter: Jeff Hammerbacher >Assignee: Jeff Hammerbacher > Attachments: HBASE-3393-2.patch, HBASE-3393-3.patch, HBASE-3393.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3387) Pair does not deep check arrays for equality.
[
https://issues.apache.org/jira/browse/HBASE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975634#action_12975634
]
stack commented on HBASE-3387:
--
@Jesse When I try to apply this patch I get this:
{code}
stack:trunk Stack$ patch -p1 < HBASE-3387.patch
patching file src/main/java/org/apache/hadoop/hbase/util/Pair.java
patch: malformed patch at line 34: * @param
{code}
Does it apply for you?
> Pair does not deep check arrays for equality.
> --
>
> Key: HBASE-3387
> URL: https://issues.apache.org/jira/browse/HBASE-3387
> Project: HBase
> Issue Type: Bug
> Components: util
>Affects Versions: 0.90.1
> Environment: Any (discovered in Ubuntu 10.10 using TRUNK).
>Reporter: Jesse Yates
>Priority: Minor
> Fix For: 0.90.1
>
> Attachments: HBASE-3387.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Pair does not deep check arrays for equality. It merely does x.equals(y) for
> the sent Object. However, with any type of array this is merely going to
> compare the array pointers, rather than the underlying data structure.
> It requires a rewriting of the private equals method in Pair to check for
> elements being an array, then checking the underlying elements.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3391) Translate The Apache HBase Book into Japanese
[ https://issues.apache.org/jira/browse/HBASE-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975632#action_12975632 ] stack commented on HBASE-3391: -- @Tatsuya What if we put the jp book under a jp subdir in src/docbook/book.xml and then had maven generate the docbook into a jp subdir under site. Will that work for Apache? It'll pick up the jp version if the browser has pref for japanese? We'd also add a link to the japanese book under the english one. When you thinking of making a start? I was thinking that once 0.90.0 was out, that I'd make a pass over the wiki moving what should be in the book from the wiki down into xml. That might be good time for you to startup. I'm a little worried the book is a bit raw. It needs greasing? And it needs a bit more substance. Other than the 'how to start hbase', its a little bare. What you think? Good stuff. > Translate The Apache HBase Book into Japanese > - > > Key: HBASE-3391 > URL: https://issues.apache.org/jira/browse/HBASE-3391 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 0.90.0 >Reporter: Tatsuya Kawano >Priority: Minor > Fix For: 0.90.1 > > > Translate The Apache HBase Book into Japanese. > This is my spare-time project and it will take a couple of weeks to translate. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-3399) upsert doesn't matchFamily() before removing key
[
https://issues.apache.org/jira/browse/HBASE-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prakash Khemani resolved HBASE-3399.
Resolution: Not A Problem
Release Note: just realized that memstore/store is per family
> upsert doesn't matchFamily() before removing key
>
>
> Key: HBASE-3399
> URL: https://issues.apache.org/jira/browse/HBASE-3399
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.90.0
>Reporter: Prakash Khemani
>Assignee: Jonathan Gray
>
> org.apache.hadoop.hbase.regionserver.MemStore.upsert(KeyValue) doesn't match
> family before deciding to remove a kv in the memstore
> // if the qualifier matches and it's a put, remove it
> if (kv.matchingQualifier(cur)) {
> // to be extra safe we only remove Puts that have a memstoreTS==0
> if (kv.getType() == KeyValue.Type.Put.getCode() &&
> kv.getMemstoreTS() == 0) {
> // false means there was a change, so give us the size.
> addedSize -= heapSizeChange(kv, true);
> it.remove();
> }
> shouldn't it be "if the family and qualifier match and it's a Put, remove it"?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HBASE-3399) upsert doesn't matchFamily() before removing key
upsert doesn't matchFamily() before removing key
Key: HBASE-3399
URL: https://issues.apache.org/jira/browse/HBASE-3399
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.0
Reporter: Prakash Khemani
Assignee: Jonathan Gray
org.apache.hadoop.hbase.regionserver.MemStore.upsert(KeyValue) doesn't match
family before deciding to remove a kv in the memstore
// if the qualifier matches and it's a put, remove it
if (kv.matchingQualifier(cur)) {
// to be extra safe we only remove Puts that have a memstoreTS==0
if (kv.getType() == KeyValue.Type.Put.getCode() &&
kv.getMemstoreTS() == 0) {
// false means there was a change, so give us the size.
addedSize -= heapSizeChange(kv, true);
it.remove();
}
shouldn't it be "if the family and qualifier match and it's a Put, remove it"?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (HBASE-3398) increment(Increment, Integer, boolean) might fail
increment(Increment, Integer, boolean) might fail
-
Key: HBASE-3398
URL: https://issues.apache.org/jira/browse/HBASE-3398
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.0
Reporter: Prakash Khemani
Assignee: Jonathan Gray
In org.apache.hadoop.hbase.regionserver.HRegion.increment(Increment, Integer,
boolean) the following loop assumes that the result from geLastIncrement() has
a single entry for a given . But that is not necessarily
true. getLastIncrement() does a union of all entries found in each of the store
files ... and multiple versions of the same key are quite possible.
List results = getLastIncrement(get);
// Iterate the input columns and update existing values if they were
// found, otherwise add new column initialized to the increment amount
int idx = 0;
for (Map.Entry column : family.getValue().entrySet()) {
long amount = column.getValue();
if (idx < results.size() &&
results.get(idx).matchingQualifier(column.getKey())) {
amount += Bytes.toLong(results.get(idx).getValue());
idx++;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3393) Update Avro gateway to use Avro 1.4.1 and the new server.join() method
[ https://issues.apache.org/jira/browse/HBASE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975604#action_12975604 ] Jeff Hammerbacher commented on HBASE-3393: -- Hey Stack, Huh, that's a new one for me. I was getting a different error (the NoSuchFieldError quoted above). Your error is easier to fix. I need to figure out the GenericArray --> List API change that happened during Avro 1.3.3 --> 1.4.1 and get this working. Will do what I can today. Regards, Jeff > Update Avro gateway to use Avro 1.4.1 and the new server.join() method > -- > > Key: HBASE-3393 > URL: https://issues.apache.org/jira/browse/HBASE-3393 > Project: HBase > Issue Type: Sub-task > Components: avro >Reporter: Jeff Hammerbacher >Assignee: Jeff Hammerbacher > Attachments: HBASE-3393-2.patch, HBASE-3393.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3393) Update Avro gateway to use Avro 1.4.1 and the new server.join() method
[
https://issues.apache.org/jira/browse/HBASE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975594#action_12975594
]
stack commented on HBASE-3393:
--
I applied the patch along w/ Lars qualification on the jboss repo and got this
compiling:
{code}
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/Users/Stack/checkouts/trunk/src/main/java/org/apache/hadoop/hbase/avro/AvroUtil.java:[140,26]
incompatible types
found : org.apache.avro.generic.GenericData.Array
required: java.util.List
{code}
You get that Jeff?
> Update Avro gateway to use Avro 1.4.1 and the new server.join() method
> --
>
> Key: HBASE-3393
> URL: https://issues.apache.org/jira/browse/HBASE-3393
> Project: HBase
> Issue Type: Sub-task
> Components: avro
>Reporter: Jeff Hammerbacher
>Assignee: Jeff Hammerbacher
> Attachments: HBASE-3393-2.patch, HBASE-3393.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3223) Get VersionInfo for Running HBase Process
[ https://issues.apache.org/jira/browse/HBASE-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975591#action_12975591 ] stack commented on HBASE-3223: -- @Lars. Ignore my remark. N is on it. > Get VersionInfo for Running HBase Process > - > > Key: HBASE-3223 > URL: https://issues.apache.org/jira/browse/HBASE-3223 > Project: HBase > Issue Type: Improvement >Reporter: Nicolas Spiegelberg >Assignee: Nicolas Spiegelberg > Fix For: 0.90.1 > > Attachments: HBASE-3223-fix.patch > > > bin/hbase VersionInfo is a great existing utility to provide version info > about Hbase jar files. Unfortunately, there is no way to currently get this > information for the running process. For this jira, add an easy/quick way to > see verify the rev of the running jar. > We got recently bit internally because our running jar was a different > version from the jar that we had recently pushed and caused havoc on our > cluster. This problem is more important to fix now that we have rolling > upgrades and will regularly have cluster scenarios with mixed-version RSs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3223) Get VersionInfo for Running HBase Process
[ https://issues.apache.org/jira/browse/HBASE-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975586#action_12975586 ] Nicolas Spiegelberg commented on HBASE-3223: @Lars: correct assumption. The idea is that 'bin/hbase VersionInfo' gives info about the jar that is resident in the HBase dir, whereas JMX will give you the info about the currently running HBase process. I guess you could build a JMX client into VersionInfo to give you both pieces of information, but I see a couple things problematic with that: 1. you would need to refactor the Hadoop VersionInfo for consistency 2. you would want to have JMX also give you static info for consistency. That's a little hacky to accomplish. 3. you run into a little bit of confusion in psuedo-distributed mode, where you have multiple JMX servers but only one HBase dir. I guess you do a JMX port scan and query every candidate you find? > Get VersionInfo for Running HBase Process > - > > Key: HBASE-3223 > URL: https://issues.apache.org/jira/browse/HBASE-3223 > Project: HBase > Issue Type: Improvement >Reporter: Nicolas Spiegelberg >Assignee: Nicolas Spiegelberg > Fix For: 0.90.1 > > Attachments: HBASE-3223-fix.patch > > > bin/hbase VersionInfo is a great existing utility to provide version info > about Hbase jar files. Unfortunately, there is no way to currently get this > information for the running process. For this jira, add an easy/quick way to > see verify the rev of the running jar. > We got recently bit internally because our running jar was a different > version from the jar that we had recently pushed and caused havoc on our > cluster. This problem is more important to fix now that we have rolling > upgrades and will regularly have cluster scenarios with mixed-version RSs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3223) Get VersionInfo for Running HBase Process
[ https://issues.apache.org/jira/browse/HBASE-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975587#action_12975587 ] stack commented on HBASE-3223: -- @Lars Say more. I don't follow. VersionInfo is static info, yeah. What would you add? > Get VersionInfo for Running HBase Process > - > > Key: HBASE-3223 > URL: https://issues.apache.org/jira/browse/HBASE-3223 > Project: HBase > Issue Type: Improvement >Reporter: Nicolas Spiegelberg >Assignee: Nicolas Spiegelberg > Fix For: 0.90.1 > > Attachments: HBASE-3223-fix.patch > > > bin/hbase VersionInfo is a great existing utility to provide version info > about Hbase jar files. Unfortunately, there is no way to currently get this > information for the running process. For this jira, add an easy/quick way to > see verify the rev of the running jar. > We got recently bit internally because our running jar was a different > version from the jar that we had recently pushed and caused havoc on our > cluster. This problem is more important to fix now that we have rolling > upgrades and will regularly have cluster scenarios with mixed-version RSs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HBASE-3397) Rename 'getRow' method of the org.apache.hadoop.hbase.client.Result Class to 'getRowKey'
Rename 'getRow' method of the org.apache.hadoop.hbase.client.Result Class to 'getRowKey' Key: HBASE-3397 URL: https://issues.apache.org/jira/browse/HBASE-3397 Project: HBase Issue Type: Improvement Components: client Affects Versions: 0.89.20100924 Environment: Centos 5.5 Reporter: Pete Haidinyak The 'getRow' method can be misleading and should be renamed to 'getRowKey' to better describe its functionality. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (HBASE-3396) getLastIncrement() can miss some key-values
getLastIncrement() can miss some key-values
---
Key: HBASE-3396
URL: https://issues.apache.org/jira/browse/HBASE-3396
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.0
Reporter: Prakash Khemani
Assignee: Jonathan Gray
In getLastIncrement() there is an assumption that memstore only scan will never
return multiple versions of a kv
// found everything we were looking for, done
if (results.size() == expected) {
return results;
}
Based on this assumption the code does an early out after it finds the expected
number of key-value pairs in the memstore. But what if there were multiple
versions of the same kv returned by the memstore scan? I think it is possible
when the memstore has a snapshot pending to be written out. A version of the
key can be returned each from the online and from the snapshot memory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3393) Update Avro gateway to use Avro 1.4.1 and the new server.join() method
[ https://issues.apache.org/jira/browse/HBASE-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975485#action_12975485 ] Lars Francke commented on HBASE-3393: - The correct JBoss repository is: http://repository.jboss.org/nexus/content/groups/public-jboss/ the "public" one also mirrors central. The Netty page should be updated. > Update Avro gateway to use Avro 1.4.1 and the new server.join() method > -- > > Key: HBASE-3393 > URL: https://issues.apache.org/jira/browse/HBASE-3393 > Project: HBase > Issue Type: Sub-task > Components: avro >Reporter: Jeff Hammerbacher >Assignee: Jeff Hammerbacher > Attachments: HBASE-3393-2.patch, HBASE-3393.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3223) Get VersionInfo for Running HBase Process
[ https://issues.apache.org/jira/browse/HBASE-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975457#action_12975457 ] Lars George commented on HBASE-3223: Just a question, wouldn't it make sense to add this to VersionInfo too? Or is that for static/build-time into only? > Get VersionInfo for Running HBase Process > - > > Key: HBASE-3223 > URL: https://issues.apache.org/jira/browse/HBASE-3223 > Project: HBase > Issue Type: Improvement >Reporter: Nicolas Spiegelberg >Assignee: Nicolas Spiegelberg > Fix For: 0.90.1 > > Attachments: HBASE-3223-fix.patch > > > bin/hbase VersionInfo is a great existing utility to provide version info > about Hbase jar files. Unfortunately, there is no way to currently get this > information for the running process. For this jira, add an easy/quick way to > see verify the rev of the running jar. > We got recently bit internally because our running jar was a different > version from the jar that we had recently pushed and caused havoc on our > cluster. This problem is more important to fix now that we have rolling > upgrades and will regularly have cluster scenarios with mixed-version RSs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
