See https://builds.apache.org/job/hbase-0.95/117/changes
Changes:
[apurtell] HBASE-8226. HBaseTestingUtility#waitUntilAllRegionsAssigned won't
return if it counts 'too many' regions
--
[...truncated 3681 lines...]
Running
See https://builds.apache.org/job/HBase-0.94/933/
--
[...truncated 5939 lines...]
Running org.apache.hadoop.hbase.regionserver.TestCompactionWithCoprocessor
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.479 sec
Running
ramkrishna.s.vasudevan created HBASE-8235:
-
Summary: Adding inmemory CF attribute to LoadTest and
PerformanceEvaluation tool
Key: HBASE-8235
URL: https://issues.apache.org/jira/browse/HBASE-8235
Heya,
Thinking about data types and serialization. I think null support is an
important characteristic for the serialized representations, especially
when considering the compound type. However, doing so in directly
incompatible with fixed-width representations for numerics. For instance,
if we
HmmmŠ good question.
I think that fixed width support is important for a great many rowkey
constructs cases, so I'd rather see something like losing MIN_VALUE and
keeping fixed width.
On 4/1/13 2:00 PM, Nick Dimiduk ndimi...@gmail.com wrote:
Heya,
Thinking about data types and
On Fri, Mar 29, 2013 at 3:49 PM, Aleksandr Shulman al...@cloudera.comwrote:
*Potential Solution:*
I propose using IntegrationTest to bind to an existing remote cluster.
Better support for external clusters in IntegrationTest land will make a
big difference for us. I believe nkeywal started
stack created HBASE-8236:
Summary: Set finalName property in hbase-assembly else basename is
hbase-assembly rather than hbase.
Key: HBASE-8236
URL: https://issues.apache.org/jira/browse/HBASE-8236
Project:
[
https://issues.apache.org/jira/browse/HBASE-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-8236.
--
Resolution: Fixed
Fix Version/s: 0.95.0
Assignee: stack
Committed to 0.95 and trunk.
I spent some time this weekend extracting bits of our serialization code to
a public github repo at http://github.com/hotpads/data-tools.
Contributions are welcome - i'm sure we all have this stuff laying around.
You can see I've bumped into the NULL problem in a few places:
*
Alex Feinberg created HBASE-8237:
Summary: Integrate HDFS request profiling with HBase request
profiling
Key: HBASE-8237
URL: https://issues.apache.org/jira/browse/HBASE-8237
Project: HBase
St.Ack
See https://builds.apache.org/job/hbase-0.95/118/changes
Thanks for the thoughtful response (and code!).
I'm thinking I will press forward with a base implementation that does not
support nulls. The idea is to provide an extensible set of interfaces, so I
think this will not box us into a corner later. That is, a mirroring
package could be implemented
See https://builds.apache.org/job/HBase-0.94/934/changes
bq. with a base implementation that does not support nulls
+1
On Mon, Apr 1, 2013 at 1:32 PM, Nick Dimiduk ndimi...@gmail.com wrote:
Thanks for the thoughtful response (and code!).
I'm thinking I will press forward with a base implementation that does not
support nulls. The idea is to
Creating the HTable with a supplied executor and keeping the conf the same
should give you most of what an HTablePool gives you.
On Sun, Mar 31, 2013 at 8:42 AM, Ted Yu yuzhih...@gmail.com wrote:
Hi,
In HBASE-8218 pass HTable as a parameter to method of AggregationClient,
there is this
See https://builds.apache.org/job/HBase-TRUNK/4004/changes
Changes:
[stack] HBASE-8236 Set finalName property in hbase-assembly else basename is
hbase-assembly rather than hbase
[stack] HBASE-8164 TestTableLockManager fails intermittently in trunk builds
[apurtell] HBASE-8213. Global
That was the idea. See https://issues.apache.org/jira/browse/HBASE-4805.
From: Elliott Clark ecl...@apache.org
To: dev@hbase.apache.org dev@hbase.apache.org
Sent: Monday, April 1, 2013 2:48 PM
Subject: Re: alternative to HTablePool
Creating the HTable with a
[
https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-7904.
---
Resolution: Invalid
Fix Version/s: (was: 0.95.0)
(was:
See https://builds.apache.org/job/hbase-0.95-on-hadoop2/51/
--
[...truncated 24186 lines...]
Running org.apache.hadoop.hbase.rest.TestGzipFilter
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.081 sec
Forking command line: /bin/sh -c cd
From the SQL perspective, handling null is important. Phoenix supports
null in the following way:
- the absence of a key value
- an empty value in a key value
- an empty value in a multi part row key
- for variable length types (VARCHAR and DECIMAL) a null byte
separator would be used if not
On Mon, Apr 1, 2013 at 4:31 PM, James Taylor jtay...@salesforce.com wrote:
From the SQL perspective, handling null is important.
From your perspective, it is critical to support NULLs, even at the expense
of fixed-width encodings at all or supporting representation of a full
range of values.
On 04/01/2013 04:41 PM, Nick Dimiduk wrote:
On Mon, Apr 1, 2013 at 4:31 PM, James Taylor jtay...@salesforce.com wrote:
From the SQL perspective, handling null is important.
From your perspective, it is critical to support NULLs, even at the expense
of fixed-width encodings at all or
Here is our first 0.95.0 release candidate. Should we put this out as
0.95.0?
The 0.95.x series of releases are designated developer releases, a type
of release we have done in the past -- see the 0.89.x series -- where we
let out 'raw', barely-tested product so developers and those generally
All clear again.
Thanks,
St.Ack
On Mon, Apr 1, 2013 at 12:56 PM, Stack st...@duboce.net wrote:
St.Ack
This is huge!
Just looking at the JIRAs is staggering. There is many things I'm
eager to see on a production release.
Thanks for this develper release!
JM
2013/4/1 Stack st...@duboce.net:
Here is our first 0.95.0 release candidate. Should we put this out as
0.95.0?
The 0.95.x series of
Since SQL allows null valued composite key parts, we needed to support it.
On 04/01/2013 05:10 PM, Ted Yu wrote:
bq. I create a dummy qualifier with a dummy value
For any single application, the above can be done.
For generic applications, how would we do this ?
Thanks
On Mon, Apr 1, 2013
Great work.
How will we effectively communicate that this release can eat your computer
(developer release)? Any pointers from the last 0.89 attempt?
Going to hbase.apache.org - Downloads - might directly lead users to
download 0.95, and play with it. Should we add something to the home page?
Hi Stack,
What are the expectations regarding 0.95? Should we open JIRAs for the
issues we found like for the other releases?
I just tried to start it out of the box and it's failing. It tries to
write on the /var/folders/ directory, which doesn't exist.
Since it's a dev release, I can
Sergey Shelukhin created HBASE-8239:
---
Summary: ChaosMonkey actions for root and meta don't work
Key: HBASE-8239
URL: https://issues.apache.org/jira/browse/HBASE-8239
Project: HBase
Issue
On Mon, Apr 1, 2013 at 6:01 PM, Enis Söztutar enis@gmail.com wrote:
How will we effectively communicate that this release can eat your computer
(developer release)? Any pointers from the last 0.89 attempt?
Since Stack figured out the hadoop1, hadoop2 suffix business, how about
adding
Furthermore, is is more important to support null values than squeeze all
representations into minimum size (4-bytes for int32, c.)?
On Apr 1, 2013 4:41 PM, Nick Dimiduk ndimi...@gmail.com wrote:
On Mon, Apr 1, 2013 at 4:31 PM, James Taylor jtay...@salesforce.comwrote:
From the SQL
I just tried to start it out of the box and it's failing. It tries
to write on the /var/folders/ directory, which doesn't exist.
I think a failure to launch should sink the RC. :-) Beyond that I'd suggest
crash bugs or recurring ERRORS or data corruption / loss.
On Monday, April 1, 2013,
Ted Yu created HBASE-8240:
-
Summary: CompoundConfiguration should implement Iterable
Key: HBASE-8240
URL: https://issues.apache.org/jira/browse/HBASE-8240
Project: HBase
Issue Type: Bug
I think having Int32, and NullableInt32 would support minimum overhead, as
well as allowing SQL semantics.
On Mon, Apr 1, 2013 at 7:26 PM, Nick Dimiduk ndimi...@gmail.com wrote:
Furthermore, is is more important to support null values than squeeze all
representations into minimum size
[
https://issues.apache.org/jira/browse/HBASE-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rajeshbabu resolved HBASE-7925.
---
Resolution: Fixed
Back port HBASE-6881 into 0.94
--
On Mon, Apr 1, 2013 at 4:59 PM, Jean-Marc Spaggiari jean-m...@spaggiari.org
wrote:
This is huge!
Just looking at the JIRAs is staggering. There is many things I'm
eager to see on a production release.
I think my list included issues as yet not resolved... let me fix.
Good on you JM,
On Mon, Apr 1, 2013 at 6:01 PM, Enis Söztutar enis@gmail.com wrote:
Great work.
How will we effectively communicate that this release can eat your computer
(developer release)? Any pointers from the last 0.89 attempt?
I can add to the head of this document,
On Mon, Apr 1, 2013 at 6:05 PM, Jean-Marc Spaggiari jean-m...@spaggiari.org
wrote:
Hi Stack,
What are the expectations regarding 0.95? Should we open JIRAs for the
issues we found like for the other releases?
That'd be great JM.
I just tried to start it out of the box and it's failing.
Hi
I checked out a new trunk code base today. I tried the following commands
to create a tar ball.
mvn -X -DskipTests help:active-profiles package assembly:assembly -Prelease
-Dhadoop.profile=2.0
mvn clean install -Dhadoop.profile=2.0 -DskipTests assembly:assembly
mvn clean install
40 matches
Mail list logo
