Lars Hofhansl created HBASE-10225:
-
Summary: Bug is calls to RegionObsever.postScannerFilterRow
Key: HBASE-10225
URL: https://issues.apache.org/jira/browse/HBASE-10225
Project: HBase
Issue Ty
Ted Yu created HBASE-10224:
--
Summary: Line length check in test-patch.sh is broken
Key: HBASE-10224
URL: https://issues.apache.org/jira/browse/HBASE-10224
Project: HBase
Issue Type: Test
[
https://issues.apache.org/jira/browse/HBASE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl resolved HBASE-10047.
---
Resolution: Later
Can't measure any meaningful perf enhancement in a real world setup. I mig
+1
Downloaded and verified the signature.
Created one table put some data and read back..
Some random commands executed from shell...
Run PE in sequential write and read modes ...
All look good.
-Anoop-
On Fri, Dec 20, 2013 at 5:53 PM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:
> I a
Congrats Liang!
On Fri, Dec 20, 2013 at 2:11 PM, Sergey Shelukhin wrote:
> Congrats!
>
>
> On Thu, Dec 19, 2013 at 2:05 PM, Nick Dimiduk wrote:
>
> > Congrats Liang!
> >
> >
> > On Wed, Dec 18, 2013 at 4:47 PM, Stack wrote:
> >
> > > 谢良 has been doing great work for ages now; we're glad to hav
[
https://issues.apache.org/jira/browse/HBASE-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Feng Honghua reopened HBASE-7226:
-
provide fix and unit-test
> HRegion.checkAndMutate uses incorrect comparison result for <, <=, > and
With the restrictions and optimizations that HBase does, this change in
behavior is simply not possible.
In your usecase, can't you just retrieve the latest state of a row and then
check the timestamps of the KeyValues?
-- Lars
From: Niels Basjes
To: dev@hba
I saw that the issue was closed with a "Won't fix".
Now I would like to know what the optimal solution is for the functional
effect I'm looking for?
"Get the latest value for only those columns that have not been modified
for more than X time"
Is it writing a custom filter or is there a better way
Hello, Thank you for your reply.
If use only 1 or 2 CFs, why Hbase say it's a column data store? It's actually
row-based data store!!
I understand, there's some trade-off if use a lot of CFs. However, I'd like to
say, we should have that option! We can have SSDs in the backend to support
this
Anoop Sam John created HBASE-10223:
--
Summary: [VisibilityController] cellVisibility presence check on
Delete mutation is wrong
Key: HBASE-10223
URL: https://issues.apache.org/jira/browse/HBASE-10223
10 matches
Mail list logo