When is 0.92 set to be released?
On Sun, Sep 18, 2011 at 11:34 PM, Stack st...@duboce.net wrote:
I just branched 0.92 and set up a new build for it up on jenkins [1].
Only bug fixes, doc improvements, and fixes for the still outstanding
blockers and criticals can be committed to the 0.92
Hi, Guys,
When I use the client.Scan class to get a set of rows back from
RegionServer, i found one interesting code, the script i used is like:
Scan scan = new Scan(Bytes.toBytes(a), Bytes.toBytes(f));
scan.addColumn(famA, col1);
scan.setCaching(1);
2 might be explained by gc. Could you give a bit more information about case 1?
Thanks
C
- Original Message -
From: Ma, Ming min...@ebay.com
To: u...@zookeeper.apache.org u...@zookeeper.apache.org
Cc: dev@hbase.apache.org dev@hbase.apache.org
Sent: Mon Sep 19 01:28:44 2011
Subject:
See https://builds.apache.org/job/HBase-0.92/1/
--
[...truncated 1618 lines...]
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.316 sec
Running org.apache.hadoop.hbase.mapred.TestTableMapReduce
Tests run: 1, Failures: 0, Errors: 0,
(replying to user@, dev@ in BCC)
AFAIK the HBase handler doesn't have the wits to understand that you
are doing a prefix scan and thus limit the scan to only the required
rows. There's a bunch of optimizations like that that need to be done.
I'm pretty sure Pig does the same thing, but don't
On Sun, Sep 18, 2011 at 3:35 PM, Jesse Yates jesse.k.ya...@gmail.com wrote:
I know this was brought up almost a year ago, but it might be time to
revisit breaking out the tests into an integration test suite and a regular
unit test suite. We can use the the maven failsafe plugin (
See https://builds.apache.org/job/HBase-0.92/2/
I'm not too familiar with the Maven Failsafe plugin, but I've been
reviewing the timings of some 'client' unit tests and where the unit test
framework spends it's time...
Anything that uses HBaseTestingUtility and does something like...
protected void setUp() throws Exception {
On Mon, Sep 19, 2011 at 12:18 PM, Doug Meil
doug.m...@explorysmedical.comwrote:
I'm not too familiar with the Maven Failsafe plugin, but I've been
reviewing the timings of some 'client' unit tests and where the unit test
framework spends it's time...
Anything that uses HBaseTestingUtility
I'm glad you like the factory idea - it's the only thing I can think of to
keep the same test infrastructure (I.e., not completely re-write
everything), but still address a sizable performance problem. I'm working
on a prototype of it now, I'l attach to a Jira.
On 9/19/11 4:06 PM, Jesse
Also, any test that extends from HBaseClusterTestCase needs to be
refactored. This class is already deprecated but it won't be able to take
advantage of such a factory because it does the cluster setup differently.
E.g.,...
public class TestGetRowVersions extends HBaseClusterTestCase {
On Mon, Sep 19, 2011 at 1:31 PM, N Keywal nkey...@gmail.com wrote:
Hi,
Something that would be useful as well is being able to match a given
version of the trunk with the test results. For example:
- Dev pull the last version of the trunk at time t
- Dev do its modification locally to the
Thanks St.Ack!
Joep
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: Sunday, September 18, 2011 12:12 PM
To: dev@hbase.apache.org
Subject: Re: Branching for 0.92 [WAS - Re: [DISCUSSION] Accumulo, another
BigTable clone, has shown up on
At Salesforce we annotate tests (with Java annotation). We distinguish between
basic, normal, and extended.
basic can reasonably be expected to be run before every check-in. normal is
then run by the build system for a small set of changes. extended is for very
long running tests and is run
Michael,
Should the version in the pom on the 0.92 branch point to 0.92.0-SNAPSHOT?
If so I can file a bug and supply patch for same.
Or are you updating that only when you get ready for a release?
Thanks,
Joep
-Original Message-
From: Rottinghuis, Joep [mailto:jrottingh...@ebay.com]
That makes sense. Let me make the change.
St.Ack
On Mon, Sep 19, 2011 at 8:02 PM, Rottinghuis, Joep
jrottingh...@ebay.com wrote:
Michael,
Should the version in the pom on the 0.92 branch point to 0.92.0-SNAPSHOT?
If so I can file a bug and supply patch for same.
Or are you updating that
Trunk should probably go to get a newer version as well (0.93?)
Can you make the version a property that I can override using
-Dhbase.version=0.92-my-own-name?
Thanks,
Joep
-Original Message-
From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
Sent: Monday,
I changed versions. How would you make hbase.version work? Looks
like you can't set project.version. I could change it to
${hbase.version} but then how to do the default value?
St.Ack
On Mon, Sep 19, 2011 at 8:24 PM, Rottinghuis, Joep
jrottingh...@ebay.com wrote:
Trunk should probably go to
You should be able to pretty easily set in in the pom (under properties),
and then just use in the version tag.
That way whenever you want to to bump version numbers, its one easy change.
-Jesse Yates
On Mon, Sep 19, 2011 at 8:47 PM, Stack st...@duboce.net wrote:
I changed versions. How
On Mon, Sep 19, 2011 at 1:06 PM, Jesse Yates jesse.k.ya...@gmail.com wrote
... will spent (at least on my laptop) about 10.7 seconds setting up the
cluster, and 7.3 seconds tearing down. Assuming that we aren't running in
a separate JVM each test invocation, sharing the same instance of
On Mon, Sep 19, 2011 at 1:31 PM, N Keywal nkey...@gmail.com wrote:
Hi,
Something that would be useful as well is being able to match a given
version of the trunk with the test results. For example:
- Dev pull the last version of the trunk at time t
- Dev do its modification locally to the
On Mon, Sep 19, 2011 at 8:53 PM, Jesse Yates jesse.k.ya...@gmail.com wrote:
You should be able to pretty easily set in in the pom (under properties),
and then just use in the version tag.
Where are the pom properties Jesse?
Thanks,
St.Ack
That way whenever you want to to bump version
I was just pushing back at the idea of 'turn everything into
interfaces! problem solved!', and thinking about what was really
necessary to get to where you want to go...
On Mon, Sep 19, 2011 at 3:26 PM, Matt Corgan mcor...@hotpads.com wrote:
Ryan - i answered your question on another thread
One other thought is that exposing ByteRange, ByteBuffer, and v1 array
stuff in Interface seems like you are exposing 'implementation'
details that perhaps shouldn't show through. I'm guessing its
unavoidable though if the Interface is to be used in a few different
contexts: i.e. v1 has to work
So if the HCell or whatever ends up returning ByteBuffers, then that
plays straight in to scatter/gather NIO calls, and if some of them are
DBB, then so much the merrier.
For example, the thrift stuff takes ByteBuffers when its calling for a
byte sequence.
-ryan
On Mon, Sep 19, 2011 at 10:39
25 matches
Mail list logo
