[
https://issues.apache.org/jira/browse/HBASE-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113665#comment-13113665
]
stack commented on HBASE-4463:
--
@Dhruba We need this too. How would we do it?
> Run more ag
[
https://issues.apache.org/jira/browse/HBASE-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113666#comment-13113666
]
stack commented on HBASE-4461:
--
+1
This for TRUNK only?
> Expose getRowOrBefore via Thrift
[
https://issues.apache.org/jira/browse/HBASE-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4131:
-
Resolution: Fixed
Fix Version/s: 0.94.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Pa
[
https://issues.apache.org/jira/browse/HBASE-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113676#comment-13113676
]
stack commented on HBASE-4296:
--
We can hold off till 2600 is done.
I don't think we can call
[
https://issues.apache.org/jira/browse/HBASE-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-4468.
--
Resolution: Fixed
Fix Version/s: 0.92.0
Hadoop Flags: [Reviewed]
Thanks for the patch nkeywal
> Wr
[
https://issues.apache.org/jira/browse/HBASE-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113685#comment-13113685
]
stack commented on HBASE-4468:
--
Applied TRUNK and 0.92 branch.
> Wrong resource name in an e
[
https://issues.apache.org/jira/browse/HBASE-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113688#comment-13113688
]
stack commented on HBASE-4467:
--
+1 on patch. If it works for you commit LarsG.
> Handle inc
[
https://issues.apache.org/jira/browse/HBASE-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4434:
-
Attachment: HBASE-4434.txt
Copied from rb.
> seek optimization: don't do eager HFile Scanner next() unless the n
[
https://issues.apache.org/jira/browse/HBASE-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4450:
-
Attachment: HBASE-4450.txt
>From rb
> test for number of blocks read: to serve as baseline for expected blocks r
[
https://issues.apache.org/jira/browse/HBASE-4450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113714#comment-13113714
]
stack commented on HBASE-4450:
--
Committed to 0.92 branch too.
> test for number of blocks re
[
https://issues.apache.org/jira/browse/HBASE-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-4434.
--
Resolution: Fixed
Fix Version/s: 0.92.0
Hadoop Flags: [Reviewed]
Committed to 0.92 branch and to TR
[
https://issues.apache.org/jira/browse/HBASE-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113723#comment-13113723
]
stack commented on HBASE-4470:
--
Related to HBASE-3446. Need retry. The HBASE-3446 fix is no
[
https://issues.apache.org/jira/browse/HBASE-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113762#comment-13113762
]
stack commented on HBASE-4418:
--
@Liyin I don't believe there is one. It came for free when w
[
https://issues.apache.org/jira/browse/HBASE-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113764#comment-13113764
]
stack commented on HBASE-4457:
--
@Praveen Yeah.. so I'd think there'd be a setHSL on the combi
[
https://issues.apache.org/jira/browse/HBASE-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113765#comment-13113765
]
stack commented on HBASE-4471:
--
Not doing pool shutdown like a bug to me (If you look in 0.92
[
https://issues.apache.org/jira/browse/HBASE-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113767#comment-13113767
]
stack commented on HBASE-4461:
--
I'd say commit to TRUNK then maybe run a vote or something if
[
https://issues.apache.org/jira/browse/HBASE-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4131:
-
Attachment: 4131-backedout.txt
Here is what I backed out.
> Make the Replication Service pluggable via a standar
[
https://issues.apache.org/jira/browse/HBASE-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-4131:
--
Backed out this patch. Was causing TestReplication failures. See
https://builds.apache.org/job/HBase-TRUNK/2246/
[
https://issues.apache.org/jira/browse/HBASE-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113817#comment-13113817
]
stack commented on HBASE-4387:
--
Does this cause TestLogRolling to fail?
https://builds.apac
[
https://issues.apache.org/jira/browse/HBASE-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reassigned HBASE-4388:
Assignee: stack (was: Ted Yu)
> Second start after migration from 90 to trunk crashes
> --
[
https://issues.apache.org/jira/browse/HBASE-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114818#comment-13114818
]
stack commented on HBASE-4481:
--
This looks we are attaching to a zk that has vestiges of a 0.
[
https://issues.apache.org/jira/browse/HBASE-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114819#comment-13114819
]
stack commented on HBASE-4481:
--
... does this test pick up the right zk client port?
> TestM
[
https://issues.apache.org/jira/browse/HBASE-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114813#comment-13114813
]
stack commented on HBASE-4335:
--
Patch looks good to me. Shall I try make a test?
This is no
[
https://issues.apache.org/jira/browse/HBASE-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-4471.
--
Resolution: Duplicate
Resolving as duplicate of:
{code}
HBASE-3712 HTable.close() doesn't shutdown thread
[
https://issues.apache.org/jira/browse/HBASE-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-4482:
-
Priority: Critical (was: Major)
> Race Condition Concerning Eviction in SlabCache
>
[
https://issues.apache.org/jira/browse/HBASE-4484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114825#comment-13114825
]
stack commented on HBASE-4484:
--
+1 Good doc.
> book - added information about the balancer i
[
https://issues.apache.org/jira/browse/HBASE-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447914#comment-15447914
]
stack commented on HBASE-16445:
---
That helps. Thanks [~Apache9]
> Refactor and reimplement
[
https://issues.apache.org/jira/browse/HBASE-16510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447942#comment-15447942
]
stack commented on HBASE-16510:
---
+1
What about RpcRetryingCallable and CancellableRegionSe
[
https://issues.apache.org/jira/browse/HBASE-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447945#comment-15447945
]
stack commented on HBASE-16516:
---
Agree. Timely. It started out as something else -- a CellS
[
https://issues.apache.org/jira/browse/HBASE-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448220#comment-15448220
]
stack commented on HBASE-16516:
---
Sure.
> Revisit the implementation of PayloadCarryingRpcC
[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448281#comment-15448281
]
stack commented on HBASE-16264:
---
Took a while, but Tactic #2 where I define my own system c
[
https://issues.apache.org/jira/browse/HBASE-16510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448287#comment-15448287
]
stack commented on HBASE-16510:
---
Sounds good (We have too many Callable types).
> Reset Rp
[
https://issues.apache.org/jira/browse/HBASE-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449362#comment-15449362
]
stack commented on HBASE-16516:
---
You forgot to add the new classes [~Apache9]
+1 Simple re
[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16264:
--
Attachment: 16264.tactic2.patch
Tactic #2 where we rewrite com.google.protobuf on class loading.
Adds a module
[
https://issues.apache.org/jira/browse/HBASE-16526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451014#comment-15451014
]
stack commented on HBASE-16526:
---
+1 Excellent.
On the white space, not sure... Hopefully y
[
https://issues.apache.org/jira/browse/HBASE-16535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451059#comment-15451059
]
stack commented on HBASE-16535:
---
Try it. +1. Looks good.
> Use regex to exclude generated
[
https://issues.apache.org/jira/browse/HBASE-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451064#comment-15451064
]
stack commented on HBASE-16531:
---
None. This is much better (I'm pretty sure I put the CellB
[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451276#comment-15451276
]
stack commented on HBASE-16264:
---
Digging in more, the above NoClassDefFoundError is a linka
[
https://issues.apache.org/jira/browse/HBASE-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15456081#comment-15456081
]
stack commented on HBASE-16538:
---
I was going to call BS since this has been working for eve
[
https://issues.apache.org/jira/browse/HBASE-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458628#comment-15458628
]
stack commented on HBASE-15513:
---
What tests are you pointing at [~vrodionov]? The above lin
[
https://issues.apache.org/jira/browse/HBASE-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458855#comment-15458855
]
stack commented on HBASE-15513:
---
Pool can also hamper performance as all cores have to coor
[
https://issues.apache.org/jira/browse/HBASE-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458871#comment-15458871
]
stack commented on HBASE-15513:
---
[~ram_krish] and [~anoopsamjohn] These are the offheap wri
[
https://issues.apache.org/jira/browse/HBASE-16538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459839#comment-15459839
]
stack commented on HBASE-16538:
---
+1 Try it.
> Version mismatch in HBaseConfiguration.check
[
https://issues.apache.org/jira/browse/HBASE-16229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15460332#comment-15460332
]
stack commented on HBASE-16229:
---
+1 Straight-forward rename (w/ nice making of HBaseRpContr
[
https://issues.apache.org/jira/browse/HBASE-16516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461379#comment-15461379
]
stack commented on HBASE-16516:
---
+1 Straight-forward rename with some nice cleanup (I like
[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15464927#comment-15464927
]
stack commented on HBASE-16264:
---
I updated the attached doc. with where I am at on Approach
[
https://issues.apache.org/jira/browse/HBASE-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466217#comment-15466217
]
stack commented on HBASE-16445:
---
Will the Call get notified whether sync or async?
Any cha
[
https://issues.apache.org/jira/browse/HBASE-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466239#comment-15466239
]
stack commented on HBASE-16445:
---
Sorry. Just took a look at the patch again and see the loc
stack created HBASE-16567:
-
Summary: Upgrade to protobuf3
Key: HBASE-16567
URL: https://issues.apache.org/jira/browse/HBASE-16567
Project: HBase
Issue Type: Task
Components: Protobufs
A
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16567:
--
Attachment: HBASE-16567.master.001.patch
> Upgrade to protobuf3
>
>
> Key:
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468971#comment-15468971
]
stack commented on HBASE-16567:
---
Attached patch is pretty much same as a patch that [~ram_k
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16567:
--
Status: Patch Available (was: Open)
> Upgrade to protobuf3
>
>
> Key: HBA
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469159#comment-15469159
]
stack commented on HBASE-16567:
---
Just a note to say that upgrading our pb to pb3 w/o runnin
[
https://issues.apache.org/jira/browse/HBASE-16264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16264:
--
Release Note: Shade/relocate the protobuf hbase uses internally. Even
though our API references protobufs -- to
[
https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15638:
--
Description:
We need to change our protobuf. Currently it is pb2.5.0. As is, protobufs
expect all buffers to b
[
https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15638:
--
Description:
We need to change our protobuf. Currently it is pb2.5.0. As is, protobufs
expect all buffers to b
[
https://issues.apache.org/jira/browse/HBASE-15638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15638:
--
Description:
We need to change our protobuf. Currently it is pb2.5.0. As is, protobufs
expect all buffers to b
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15469611#comment-15469611
]
stack commented on HBASE-16567:
---
[~ram_krish] I don't think I had your issues because proto
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16567:
--
Description:
Move master branch on to protobuf3. See
https://github.com/google/protobuf/releases We'd do it be
[
https://issues.apache.org/jira/browse/HBASE-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470479#comment-15470479
]
stack commented on HBASE-16567:
---
HBASE-15638 is where I'm trying to find the classloader m
stack created HBASE-16580:
-
Summary: [DOC] Spark chapter improvements
Key: HBASE-16580
URL: https://issues.apache.org/jira/browse/HBASE-16580
Project: HBase
Issue Type: Task
Components: doc
[
https://issues.apache.org/jira/browse/HBASE-16580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16580:
--
Attachment: doc.txt
A few edits. Need more.
> [DOC] Spark chapter improvements
> -
[
https://issues.apache.org/jira/browse/HBASE-16530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474154#comment-15474154
]
stack commented on HBASE-16530:
---
[~appy]!
> Reduce DBE code duplication
>
[
https://issues.apache.org/jira/browse/HBASE-16530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474251#comment-15474251
]
stack commented on HBASE-16530:
---
Can you look at the above failure?
I tried running it loc
[
https://issues.apache.org/jira/browse/HBASE-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475173#comment-15475173
]
stack commented on HBASE-16148:
---
Reviewed lastest version of the patch. This patch is great
[
https://issues.apache.org/jira/browse/HBASE-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477558#comment-15477558
]
stack commented on HBASE-16596:
---
Sounds good [~chenheng] (what is AP? thanks)
> Reduce red
[
https://issues.apache.org/jira/browse/HBASE-16596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477598#comment-15477598
]
stack commented on HBASE-16596:
---
+1 (pending hadoopqa passes).
> Reduce redundant interfac
[
https://issues.apache.org/jira/browse/HBASE-16583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477995#comment-15477995
]
stack commented on HBASE-16583:
---
Thanks [~apurtell]. Yeah, handoff between threads via a Qu
[
https://issues.apache.org/jira/browse/HBASE-16583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478105#comment-15478105
]
stack commented on HBASE-16583:
---
The 'Availability' issue -- how our current server 'archit
[
https://issues.apache.org/jira/browse/HBASE-16583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478105#comment-15478105
]
stack edited comment on HBASE-16583 at 9/9/16 8:14 PM:
---
The 'Availa
[
https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478593#comment-15478593
]
stack edited comment on HBASE-14070 at 9/9/16 11:56 PM:
The patch
[
https://issues.apache.org/jira/browse/HBASE-16491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16491:
--
Assignee: Umesh Agashe
> A few org.apache.hadoop.hbase.rsgroup classes missing @InterfaceAudience
> annotation
[
https://issues.apache.org/jira/browse/HBASE-16491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15479262#comment-15479262
]
stack commented on HBASE-16491:
---
[~uagashe] I added you as a contributor and assigned you t
[
https://issues.apache.org/jira/browse/HBASE-16607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15482950#comment-15482950
]
stack commented on HBASE-16607:
---
Makes sense. I currently have a patch that does same thing
[
https://issues.apache.org/jira/browse/HBASE-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16604:
--
Fix Version/s: (was: 1.2.3)
1.2.4
> Scanner retries on IOException can cause the scans t
[
https://issues.apache.org/jira/browse/HBASE-15624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484120#comment-15484120
]
stack commented on HBASE-15624:
---
Patch LGTM. The doc change is in branch-1 only? Do it on m
[
https://issues.apache.org/jira/browse/HBASE-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484159#comment-15484159
]
stack commented on HBASE-16388:
---
[~yangzhe1991] Can this be on by default rather than requi
[
https://issues.apache.org/jira/browse/HBASE-16613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484171#comment-15484171
]
stack commented on HBASE-16613:
---
+1 on fix (nice find). Let me rerun hadoopqa.
> Return th
[
https://issues.apache.org/jira/browse/HBASE-16613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-16613:
--
Attachment: HBASE-16613.branch-1.v1.patch
> Return the unused ByteBuffer to BoundedByteBufferPool when no cell
[
https://issues.apache.org/jira/browse/HBASE-16614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484189#comment-15484189
]
stack commented on HBASE-16614:
---
+1
> Use daemon thread for netty event loop
> ---
[
https://issues.apache.org/jira/browse/HBASE-16612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484198#comment-15484198
]
stack commented on HBASE-16612:
---
+1 Nice.
> Use array to cache Types for KeyValue.Type.cod
[
https://issues.apache.org/jira/browse/HBASE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484865#comment-15484865
]
stack commented on HBASE-7912:
--
I reviewed the doc. It is nice and high-level pitched properl
[
https://issues.apache.org/jira/browse/HBASE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484973#comment-15484973
]
stack commented on HBASE-7912:
--
Was there supposed to be a section on addressing failure mode
[
https://issues.apache.org/jira/browse/HBASE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15485158#comment-15485158
]
stack commented on HBASE-7912:
--
I am game to try it out again when you have something new pos
[
https://issues.apache.org/jira/browse/HBASE-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486221#comment-15486221
]
stack commented on HBASE-16388:
---
Where does the user get feedback on how well or how bad th
[
https://issues.apache.org/jira/browse/HBASE-16615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486276#comment-15486276
]
stack commented on HBASE-16615:
---
Skimmed. Looks good. Try it. +1
> Fix flaky TestScannerHe
[
https://issues.apache.org/jira/browse/HBASE-16611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486279#comment-15486279
]
stack commented on HBASE-16611:
---
Patch looks good. Keep running it here and if it passes, +
[
https://issues.apache.org/jira/browse/HBASE-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487161#comment-15487161
]
stack commented on HBASE-16388:
---
Ok. Expert config. If you are seeing SBE, then you have se
[
https://issues.apache.org/jira/browse/HBASE-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487230#comment-15487230
]
stack commented on HBASE-15968:
---
This 'fixed' behavior should be default in 2.0.0. Rather t
[
https://issues.apache.org/jira/browse/HBASE-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487266#comment-15487266
]
stack commented on HBASE-15968:
---
mvcc-sensitive is not a good name because the whole system
[
https://issues.apache.org/jira/browse/HBASE-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487269#comment-15487269
]
stack commented on HBASE-15968:
---
Oh, finally, this work is great.
> MVCC-sensitive semanti
[
https://issues.apache.org/jira/browse/HBASE-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487589#comment-15487589
]
stack commented on HBASE-16626:
---
Yes.
Master is jdk8 so you could make use of the new lang
[
https://issues.apache.org/jira/browse/HBASE-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487595#comment-15487595
]
stack commented on HBASE-16624:
---
I think this a good supposition but method looks too big t
[
https://issues.apache.org/jira/browse/HBASE-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487602#comment-15487602
]
stack commented on HBASE-16624:
---
+1 on the fix. Good find. Agree a test would be good but r
[
https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487623#comment-15487623
]
stack commented on HBASE-15921:
---
I've been in here over the last week or so. The variety of
[
https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487625#comment-15487625
]
stack commented on HBASE-15921:
---
Sorry, this remark was supposed to go w/ the suggestion th
[
https://issues.apache.org/jira/browse/HBASE-16627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487858#comment-15487858
]
stack commented on HBASE-16627:
---
Not a blocker. Warn sounds better but if not an issue can
[
https://issues.apache.org/jira/browse/HBASE-15968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487896#comment-15487896
]
stack commented on HBASE-15968:
---
How should visibility labels be done? In the compound trac
[
https://issues.apache.org/jira/browse/HBASE-16631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490827#comment-15490827
]
stack commented on HBASE-16631:
---
Is this a straight extraction or did you make other change
[
https://issues.apache.org/jira/browse/HBASE-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490850#comment-15490850
]
stack commented on HBASE-16388:
---
Findbugs issue is unrelated:
CodeWarning
RV Ret
1601 - 1700 of 37919 matches
Mail list logo
