[
https://issues.apache.org/jira/browse/HBASE-9997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John resolved HBASE-9997.
---
Resolution: Fixed
Hadoop Flags: Reviewed
> Add per KV security details to HBase book
>
Andrew Purtell created HBASE-10072:
--
Summary: Regenerate ClientProtos after HBASE-4811
Key: HBASE-10072
URL: https://issues.apache.org/jira/browse/HBASE-10072
Project: HBase
Issue Type: Bug
> Deveraj:
> Jonathan Hsieh, WAL per region (WALpr) would give you the locality (and
hence HDFS short
> circuit) of reads if you were to couple it with the favored nodes. The
cost is of course more WAL
> files... In the current situation (no WALpr) it would create quite some
traffic cross machine,
Fundamentally, I'd prefer focusing on making HBase "HBasier" instead of
tackling a feature that other systems architecturally can do better
(inconsistent reads). I consider consistent reads/writes being one of
HBase's defining features. That said, I think read replicas makes sense and
is a nice f
> Enis:
> I was trying to refer to not having co-location constraints for secondary
replicas whose primaries are hosted by the same
> RS. For example, if R1(replica=0), and R2(replica=0) are hosted on RS1,
R1(replica=1) and R2(replica=1) can be hosted by RS2
> and RS3 respectively. This can definit
HBASE-10070 [1] looks to be heading into a discussion more apt for the
mailing list than in the jira. Moving this to the dev list for threaded
discussion. I'll start a few threads by replying to this thread with
edited titles
[1] https://issues.apache.org/jira/browse/HBASE-10070
--
// Jonathan
On Mon, Dec 2, 2013 at 7:34 PM, Ted Yu wrote:
> bq. The lastest submitted trunk patch
>
> The proposal here wouldn't use minicluster.
>
> Great!
> Cheers
>
>
> On Mon, Dec 2, 2013 at 7:31 PM, Jonathan Hsieh wrote:
>
> > On Mon, Dec 2, 2013 at 1:13 PM, Ted Yu wrote:
> >
> > > bq. Would it be
cuijianwei created HBASE-10071:
--
Summary: support data type for get/scan in hbase shell
Key: HBASE-10071
URL: https://issues.apache.org/jira/browse/HBASE-10071
Project: HBase
Issue Type: Improve
[
https://issues.apache.org/jira/browse/HBASE-10068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl resolved HBASE-10068.
---
Resolution: Invalid
Yeah, there isn't much we can here.
Closing, but feel free to reopen.
>
bq. The lastest submitted trunk patch
The proposal here wouldn't use minicluster.
Cheers
On Mon, Dec 2, 2013 at 7:31 PM, Jonathan Hsieh wrote:
> On Mon, Dec 2, 2013 at 1:13 PM, Ted Yu wrote:
>
> > bq. Would it be possible just to have it focus on just a region/store
> > level instead?
> >
>
On Mon, Dec 2, 2013 at 1:13 PM, Ted Yu wrote:
> bq. Would it be possible just to have it focus on just a region/store
> level instead?
>
> TestStoreScanner doesn't start minicluster.
>
>
The lastest submitted trunk patch most certainly did.
I think you can just create a standalone region with d
Sounds reasonable to me. Maybe add .diff to that list?
On Mon, Dec 2, 2013 at 4:34 PM, Ted Yu wrote:
> During review of
> HBASE-10044 test-patch.sh should filter out documents by known file
> extensions
> Jesse made the suggestion that QA bot only accepts files with extensions
> .patch
> and
Enis Soztutar created HBASE-10070:
-
Summary: HBase read high-availability using eventually consistent
region replicas
Key: HBASE-10070
URL: https://issues.apache.org/jira/browse/HBASE-10070
Project: H
During review of
HBASE-10044 test-patch.sh should filter out documents by known file
extensions
Jesse made the suggestion that QA bot only accepts files with extensions .patch
and .txt
I want to get opinion from the community on this matter.
Thanks
Ted Yu created HBASE-10069:
--
Summary: Potential duplicate calls to log#appendNoSync() in
HRegion#doMiniBatchMutation()
Key: HBASE-10069
URL: https://issues.apache.org/jira/browse/HBASE-10069
Project: HBase
Shashi Singh created HBASE-10068:
Summary: Create Table Issue
Key: HBASE-10068
URL: https://issues.apache.org/jira/browse/HBASE-10068
Project: HBase
Issue Type: Bug
Components: shel
bq. Would it be possible just to have it focus on just a region/store
level instead?
TestStoreScanner doesn't start minicluster.
bq. Can you add enough info so that we don't need to consult the jira to
figure out what the unit test is testing?
Sure. I will add comments to the new test.
Cheers
Part of the reason the injection stuff was "needed" was because the test
crafted data using the higher level minicluster. Would it be possible just
to have it focus on just a region/store level instead? Along with the
focused unit test could a separate easy-to-read easy-to-maintain system
test be
Is the proposed approach below acceptable ?
Cheers
On Wed, Nov 20, 2013 at 9:48 AM, Ted Yu wrote:
> As requested by Jonathan, I am posting the following approach for testing
> fix of HBASE-9949 :
>
>
> 1. Introduce config parameter for StoreScanner implementation which would
> be used by HStor
Vikram Singh Chandel created HBASE-10067:
Summary: Filters are not applied to Coprocessor if columns are
added to the scanner
Key: HBASE-10067
URL: https://issues.apache.org/jira/browse/HBASE-10067
Andrew Purtell created HBASE-10066:
--
Summary: Use ByteArrayOutputStream#writeTo where appropriate
Key: HBASE-10066
URL: https://issues.apache.org/jira/browse/HBASE-10066
Project: HBase
Issue
Andrew Purtell created HBASE-10065:
--
Summary: Stronger validation of key unwrapping
Key: HBASE-10065
URL: https://issues.apache.org/jira/browse/HBASE-10065
Project: HBase
Issue Type: Improve
cuijianwei created HBASE-10064:
--
Summary: AggregateClient.validateParameters will throw
NullPointerException when set startRow/stopRow of scan to null
Key: HBASE-10064
URL: https://issues.apache.org/jira/browse/HBASE
Andrew Purtell created HBASE-10063:
--
Summary: Consider lighter weight generation of IVs for WAL entries
Key: HBASE-10063
URL: https://issues.apache.org/jira/browse/HBASE-10063
Project: HBase
24 matches
Mail list logo