Presuming this is the using the C++ client that is under active
development and not yet in a release, please limit discussion of it to
the dev@hbase list.
(I have sent this to the dev list and moved the user@ list to bcc)
On Thu, Oct 5, 2017 at 12:41 AM, Andrzej wrote:
>
Test on my meager VirtualBox environment:
put 100'000 rows with 5 column per row : 20 to 21 seconds
but if I printf to stdout each 1000 row: 29 seconds
it is too big difference, alone printfs with screen scrolling give me
only <0.1 s.
W dniu 05.10.2017 o 10:56, Andrzej pisze:
Test on my meager VirtualBox environment:
put 100'000 rows with 5 column per row : 20 to 21 seconds
but if I printf to stdout each 1000 row: 29 seconds
it is too big difference, alone printfs with screen scrolling give me
only <0.1 s.
Mean speed is
W dniu 05.10.2017 o 09:23, Ted Yu pisze:
Did you use scan ?
Cheers
I compare speed : native client Put columns and Thrift client.mutateRow
(Thrift1) because in Thrift1 I can't find Put columns.
Speed difference is significant
Sincerely
W dniu 05.10.2017 o 08:01, Sean Busbey pisze:
Presuming this is the using the C++ client that is under active
development and not yet in a release, please limit discussion of it to
the dev@hbase list.
(I have sent this to the dev list and moved the user@ list to bcc)
Is anywhere features of
Did you use scan ?
Cheers
Original message From: Andrzej Date:
10/5/17 12:03 AM (GMT-08:00) To: dev Subject: Re: If
possible read families from tables and (more important) qualifiers?
W dniu 05.10.2017 o 08:01, Sean Busbey pisze:
Amit Kabra created HBASE-18947:
--
Summary: HBase backups backup all tables once backed up
irrespective of the table names passed to it.
Key: HBASE-18947
URL: https://issues.apache.org/jira/browse/HBASE-18947
Hello
Can someone please add me to the HBase slack channel?
Thanks.
-Srinivas
(I think I understand the problems enough to comment, but, admittedly,
my 5minute read is probably lacking)
I think the only argument against what you all have outlined here is if,
in the future, we have some intent to create new implementations of
HRegion or HStore. If that's the case,
[
https://issues.apache.org/jira/browse/HBASE-6301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob resolved HBASE-6301.
--
Resolution: Not A Problem
Yetus seems to be behaving properly, closing issue.
> Fix hadoopqa script
I think Google's style is good enough. But for us, I'm +1 on moving the
imports of hbase-thirdparty, i.e., the shaded ones, to a new block.
2017-10-03 0:30 GMT+08:00 Andrew Purtell :
> I think whatever offers lower overall effort for committers would be the
> better choice.
Duo Zhang created HBASE-18949:
-
Summary: Remove the CompactionRequest parameter in
preCompactSelection
Key: HBASE-18949
URL: https://issues.apache.org/jira/browse/HBASE-18949
Project: HBase
I believe there is an umbrella jira tracking the progress of the
feature on its branch. I haven't kept up with development enough to know if
it's accurate and/or if things have reached the stage of explicitly
documenting things.
@Ted Y might be able to provide a pointer?
On Thu, Oct 5, 2017 at
Duo Zhang created HBASE-18952:
-
Summary: Remove the Optional(Int) usage in the constructors of
HStore
Key: HBASE-18952
URL: https://issues.apache.org/jira/browse/HBASE-18952
Project: HBase
See Enis' comment:
https://issues.apache.org/jira/browse/HBASE-14850?focusedCommentId=15840799=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15840799
though it was half year old.
On Thu, Oct 5, 2017 at 8:53 AM, Sean Busbey wrote:
> I believe there
Duo Zhang created HBASE-18950:
-
Summary: Remove Optional parameters in AsyncAdmin interface
Key: HBASE-18950
URL: https://issues.apache.org/jira/browse/HBASE-18950
Project: HBase
Issue Type:
Thiriguna Bharat Rao created HBASE-18948:
Summary: HBase tags are server side only.
Key: HBASE-18948
URL: https://issues.apache.org/jira/browse/HBASE-18948
Project: HBase
Issue Type:
Duo Zhang created HBASE-18951:
-
Summary: Use Builder pattern to remove nullable parameters in
RawAsyncTable/AsyncTable interface
Key: HBASE-18951
URL: https://issues.apache.org/jira/browse/HBASE-18951
[
https://issues.apache.org/jira/browse/HBASE-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashu Pachauri resolved HBASE-17117.
---
Resolution: Cannot Reproduce
After multiple attempts, we could not reproduce this issue.
As far as I know, Facebook's one use case is the only remaining known place
we are experience FNFE related issues in long scanning / compaction, and
since the time we last talked about it some more fixes have gone in. Our
testing looks good. If they also see good results with latest branch-1.3 I
Appy created HBASE-18954:
Summary: Make *CoprocessorHost classes private
Key: HBASE-18954
URL: https://issues.apache.org/jira/browse/HBASE-18954
Project: HBase
Issue Type: Sub-task
Ted Yu created HBASE-18953:
--
Summary: Use hadoop shaded jars for hadoop-3 profile
Key: HBASE-18953
URL: https://issues.apache.org/jira/browse/HBASE-18953
Project: HBase
Issue Type: Improvement
As said in HBASE-18786 some exception handling for FileNot Found
Exception was the reason for the issues posted by FB. All were actually
related one way or the other. HBASE-18771 has fixed the issue when that
FileNotFound happens.
If facebook can provide feedback post HBASE-18771 I think that
[
https://issues.apache.org/jira/browse/HBASE-17892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashu Pachauri resolved HBASE-17892.
---
Resolution: Duplicate
Closing this as duplicate because HBASE-14247 is actively being worked
Josh Elser created HBASE-18955:
--
Summary: HBase client queries stale hbase:meta location with
half-dead RegionServer
Key: HBASE-18955
URL: https://issues.apache.org/jira/browse/HBASE-18955
Project:
25 matches
Mail list logo