Requesting access to hbase slack channel

[Madhur Pant]

Hi Team,

I was wondering if I could get access to the HBase user slack channel

https://apache-hbase.slack.com

It says here   that I
should email you guys  :)

Thanks,
Madhur Pant

Re: Seek for help to create an account on review.apache

[Misty Linville]

I think you may need to contact infra directly. I'm sorry you're facing
this trouble and I appreciate the extra effort you're going through to
contribute. I wonder if you can try creating a pull request on GitHub
instead of using Reviewboard until you get a resolution. I confess I am not
as familiar with the Gitbox functionality as I should be. Can anyone else
help out here? I've added the PMC list just in case it helps speed things
along.

On Tue, Jan 15, 2019, 6:59 PM wang huan  Hi, Zhang: https://reviews.apache.org have enabled LDAP,  can not log in
> with account on jira.
>
> On 16/1/19, 10:17 AM, "张铎(Duo Zhang)"  wrote:
>
> I think it uses the same account with jira? i.e, issues.apache.org.
>
> wang huan  于2019年1月16日周三 上午10:13写道：
>
> > Hi, All:
> > I want to login https://reviews.apache.org to upload my patch
> > onhttps://jira.apache.org/jira/browse/HBASE-21699,  all apache
> projects
> > told me go to https://reviews.apache.org and create an account, but
> no
> > register page on there !
> >  My colleague told me he got his account from dev@mesos, so I
> want to
> > know if someone can
> > help me create an account
> >
> > Best Regards,
> > huan
> >
> >
>
>

Re: Seek for help to create an account on review.apache

[wang huan]

Hi, Zhang: https://reviews.apache.org have enabled LDAP,  can not log in with 
account on jira.

On 16/1/19, 10:17 AM, "张铎(Duo Zhang)"  wrote:

I think it uses the same account with jira? i.e, issues.apache.org.

wang huan  于2019年1月16日周三 上午10:13写道：

> Hi, All:
> I want to login https://reviews.apache.org to upload my patch
> onhttps://jira.apache.org/jira/browse/HBASE-21699,  all apache projects
> told me go to https://reviews.apache.org and create an account, but no
> register page on there !
>  My colleague told me he got his account from dev@mesos, so I want to
> know if someone can
> help me create an account
>
> Best Regards,
> huan
>
>

[jira] [Created] (HBASE-21731) Do not need to use ClusterConnection in IntegrationTestBigLinkedListWithVisibility

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-21731:
-

 Summary: Do not need to use ClusterConnection in 
IntegrationTestBigLinkedListWithVisibility
 Key: HBASE-21731
 URL: https://issues.apache.org/jira/browse/HBASE-21731
 Project: HBase
  Issue Type: Task
Reporter: Duo Zhang


We could just use the RegionLocator instead of ClusterConnection.relocateRegion



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (HBASE-21675) Port HBASE-21642 (CopyTable by reading snapshot and bulkloading will save a lot of time) to branch-1

[Andrew Purtell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell reopened HBASE-21675:


> Port HBASE-21642 (CopyTable by reading snapshot and bulkloading will save a 
> lot of time) to branch-1
> 
>
> Key: HBASE-21675
> URL: https://issues.apache.org/jira/browse/HBASE-21675
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Andrew Purtell
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21730) Update hbase-book with the procedure based WAL splitting

[Jingyun Tian (JIRA)]

Jingyun Tian created HBASE-21730:


 Summary: Update hbase-book with the procedure based WAL splitting
 Key: HBASE-21730
 URL: https://issues.apache.org/jira/browse/HBASE-21730
 Project: HBase
  Issue Type: Sub-task
Reporter: Jingyun Tian






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21729) Extract ProcedureCoordinatorRpcs and ProcedureMemberRpcs from CoordinatedStateManager

[Jingyun Tian (JIRA)]

Jingyun Tian created HBASE-21729:


 Summary: Extract ProcedureCoordinatorRpcs and ProcedureMemberRpcs 
from CoordinatedStateManager
 Key: HBASE-21729
 URL: https://issues.apache.org/jira/browse/HBASE-21729
 Project: HBase
  Issue Type: Sub-task
Reporter: Jingyun Tian
Assignee: Jingyun Tian


If procedureV2 based WAL splitting is enabled, CoordinatedStateManager will not 
be initialized. Then ProcedureCoordinatorRpcs and ProcedureMemberRpcs will make 
backup not work. Let me extract these two method to another class.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Seek for help to create an account on review.apache

[Duo Zhang]

I think it uses the same account with jira? i.e, issues.apache.org.

wang huan  于2019年1月16日周三 上午10:13写道：

> Hi, All:
> I want to login https://reviews.apache.org to upload my patch
> onhttps://jira.apache.org/jira/browse/HBASE-21699,  all apache projects
> told me go to https://reviews.apache.org and create an account, but no
> register page on there !
>  My colleague told me he got his account from dev@mesos, so I want to
> know if someone can
> help me create an account
>
> Best Regards,
> huan
>
>

Seek for help to create an account on review.apache

[wang huan]

Hi, All:
I want to login https://reviews.apache.org to upload my patch 
onhttps://jira.apache.org/jira/browse/HBASE-21699,  all apache projects told me 
go to https://reviews.apache.org and create an account, but no register page on 
there !
 My colleague told me he got his account from dev@mesos, so I want to know 
if someone can
help me create an account

Best Regards,
huan

[jira] [Resolved] (HBASE-21674) Port HBASE-21652 (Refactor ThriftServer making thrift2 server inherited from thrift1 server) to branch-1

[Andrew Purtell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell resolved HBASE-21674.

   Resolution: Later
Fix Version/s: (was: 1.5.0)

Not going to have time for this. At best it is a nice-to-have. Resolving as 
Later

> Port HBASE-21652 (Refactor ThriftServer making thrift2 server inherited from 
> thrift1 server) to branch-1
> 
>
> Key: HBASE-21674
> URL: https://issues.apache.org/jira/browse/HBASE-21674
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Andrew Purtell
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-21675) Port HBASE-21642 (CopyTable by reading snapshot and bulkloading will save a lot of time) to branch-1

[Andrew Purtell (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Purtell resolved HBASE-21675.

   Resolution: Later
Fix Version/s: (was: 1.5.0)

The backport was simple enough but deceptively so. New test for 
snapshot+bulkload did not pass. Spent some time looking at it but didn't make 
progress. This is only a nice to have at best so not worth more time. Resolving 
as Later. 

> Port HBASE-21642 (CopyTable by reading snapshot and bulkloading will save a 
> lot of time) to branch-1
> 
>
> Key: HBASE-21675
> URL: https://issues.apache.org/jira/browse/HBASE-21675
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Andrew Purtell
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Did the branch-2.1 need the patch HBASE-21657 ?

[OpenInx]

Well, thanks all, Let me push this patch to branch-2 and master.

On Tue, Jan 15, 2019 at 11:58 AM 张铎(Duo Zhang) 
wrote:

> Sean Busbey  于2019年1月15日周二 上午11:33写道：
>
> > I'd much rather see this in 2.2.0 rather than squeeze it into a 2.1
> > maintenance release.
> >
> > Can 2.2 do rolling upgrade from earlier 2.y releases? There's nothing in
> > the ref guide, but I thought it didn't work due to some assignment
> change.
> >
> Need to make sure that there are ongoing RITs when upgrading the HMaster.
> If so the new master will quit and you have to start old HMaster again to
> finish them first.
> If we want to release 2.2.0, at least we need to document this out.
>
> >
> > On Mon, Jan 14, 2019, 20:07 OpenInx  >
> > > bq. For me, I would say that let's start the 2.2.x release line soon?
> So
> > > user could benefit from the change after they upgrade to 2.2.x.
> > > Sound good.
> > >
> > > On Tue, Jan 15, 2019 at 11:05 AM OpenInx  wrote:
> > >
> > > > b
> > > >
> > > > On Tue, Jan 15, 2019 at 10:54 AM 张铎(Duo Zhang) <
> palomino...@gmail.com>
> > > > wrote:
> > > >
> > > >> For me, I would say that let's start the 2.2.x release line soon? So
> > > user
> > > >> could benefit from the change after they upgrade to 2.2.x.
> > > >>
> > > >> OpenInx  于2019年1月15日周二 上午10:21写道：
> > > >>
> > > >> > Sorry, here is a typo.
> > > >> >
> > > >> > > but not quite sure for branch-1 . Discussion are welcome
> (smile).
> > > >> > but not quite sure for branch-2.1
> > > >> >
> > > >> > On Tue, Jan 15, 2019 at 10:17 AM OpenInx 
> wrote:
> > > >> >
> > > >> > > Hi:
> > > >> > >
> > > >> > > In HBASE-21657,  I simplified the path of
> > estimatedSerialiedSize() &
> > > >> > > estimatedSerialiedSizeOfCell() by moving the general
> > > >> getSerializedSize()
> > > >> > > and heapSize() from ExtendedCell to Cell interface. It's a
> > > >> incompatible
> > > >> > > change in some case, such as if the upstream user implemented
> > their
> > > >> > > own Cells, although it's rare but can happen, then their compile
> > > will
> > > >> be
> > > >> > > error.
> > > >> > >
> > > >> > > We gain almost ~40% throughput improvement in 100% scan case for
> > > >> branch-2
> > > >> > > (cacheHitRatio~100%)[1], it's a good thing. but I'm not sure
> > > >> > > whether the patch should go to branch-2.1 ?   in here [2], stack
> > > says
> > > >> > > branch-2.0 won't need this Cell interface change (Agree, maybe
> the
> > > >> > > following
> > > >> > > change can be included, will file issue for it), but not quite
> > sure
> > > >> for
> > > >> > > branch-1 . Discussion are welcome (smile).
> > > >> > >
> > > >> > > Anyway,  patch can be included to branch-2/master because we've
> > not
> > > >> made
> > > >> > a
> > > >> > > release yet.
> > > >> > >
> > > >> > > BTW, the patch also included some other improvments:
> > > >> > > 1.  for 99%  of case, our cells has no tags, so let the
> > > >> HFileScannerImpl
> > > >> > > just return the NoTagsByteBufferKeyValue if no tags, which means
> > we
> > > >> can
> > > >> > > save
> > > >> > >  lots of cpu time when sending no tags cell to rpc because
> can
> > > >> just
> > > >> > > return the length instead of getting the serialize size by
> > > caculating
> > > >> > > offset/length
> > > >> > >  of each fields(row/cf/cq..)
> > > >> > > 2. Move the subclass's getSerializedSize implementation from
> > > >> ExtendedCell
> > > >> > > to their own class, which mean we did not need to call
> > > ExtendedCell's
> > > >> > > getSerialiedSize() firstly, then forward to subclass's
> > > >> > > getSerializedSize(withTags).
> > > >> > > 3.  Give a estimated result arraylist size for avoiding the
> > frequent
> > > >> list
> > > >> > > extension when in a big scan, now we estimate the array size as
> > > >> > > min(scan.rows, 512).
> > > >> > >  it's also help a lot.
> > > >> > >
> > > >> > > Thanks.
> > > >> > >
> > > >> > > 1.
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://issues.apache.org/jira/browse/HBASE-21657?focusedCommentId=16735455=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16735455
> > > >> > > 2.
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://issues.apache.org/jira/browse/HBASE-21657?focusedCommentId=16742330=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16742330
> > > >> > >
> > > >> >
> > > >>
> > > >
> > >
> >
>

[jira] [Resolved] (HBASE-20917) MetaTableMetrics#stop references uninitialized requestsMap for non-meta region

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-20917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved HBASE-20917.
-
   Resolution: Fixed
Fix Version/s: 2.1.3

> MetaTableMetrics#stop references uninitialized requestsMap for non-meta region
> --
>
> Key: HBASE-20917
> URL: https://issues.apache.org/jira/browse/HBASE-20917
> Project: HBase
>  Issue Type: Bug
>  Components: meta, metrics
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Major
> Fix For: 3.0.0, 1.5.0, 2.2.0, 2.1.3, 2.0.4, 1.4.6
>
> Attachments: 20917.addendum, 20917.v1.txt, 20917.v2.txt
>
>
> I noticed the following in test output:
> {code}
> 2018-07-21 15:54:43,181 ERROR [RS_CLOSE_REGION-regionserver/172.17.5.4:0-1] 
> executor.EventHandler(186): Caught throwable while processing event 
> M_RS_CLOSE_REGION
> java.lang.NullPointerException
>   at 
> org.apache.hadoop.hbase.coprocessor.MetaTableMetrics.stop(MetaTableMetrics.java:329)
>   at 
> org.apache.hadoop.hbase.coprocessor.BaseEnvironment.shutdown(BaseEnvironment.java:91)
>   at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$RegionEnvironment.shutdown(RegionCoprocessorHost.java:165)
>   at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.shutdown(CoprocessorHost.java:290)
>   at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$4.postEnvCall(RegionCoprocessorHost.java:559)
>   at 
> org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:622)
>   at 
> org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.postClose(RegionCoprocessorHost.java:551)
>   at org.apache.hadoop.hbase.regionserver.HRegion.doClose(HRegion.java:1678)
>   at org.apache.hadoop.hbase.regionserver.HRegion.close(HRegion.java:1484)
>   at 
> org.apache.hadoop.hbase.regionserver.handler.CloseRegionHandler.process(CloseRegionHandler.java:104)
>   at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> {code}
> {{requestsMap}} is only initialized for the meta region.
> However, check for meta region is absent in the stop method:
> {code}
>   public void stop(CoprocessorEnvironment e) throws IOException {
> // since meta region can move around, clear stale metrics when stop.
> for (String meterName : requestsMap.keySet()) {
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved HBASE-21590.
-
   Resolution: Fixed
Fix Version/s: 2.1.3

> Optimize trySkipToNextColumn in StoreScanner a bit
> --
>
> Key: HBASE-21590
> URL: https://issues.apache.org/jira/browse/HBASE-21590
> Project: HBase
>  Issue Type: Improvement
>  Components: Performance, Scanners
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.2.0, 1.4.10, 2.1.3, 2.0.4
>
> Attachments: 21590-1.5.txt, HBASE-21590-master.txt, 
> HBASE-21590.addendum.v1.patch
>
>
> See latest comment on HBASE-17958



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (HBASE-21590) Optimize trySkipToNextColumn in StoreScanner a bit

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey reopened HBASE-21590:
-

looks like I missed branch-2.1 after all. reopening while I push it.

> Optimize trySkipToNextColumn in StoreScanner a bit
> --
>
> Key: HBASE-21590
> URL: https://issues.apache.org/jira/browse/HBASE-21590
> Project: HBase
>  Issue Type: Improvement
>  Components: Performance, Scanners
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
>Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.2.0, 2.1.2, 2.0.4, 1.4.10
>
> Attachments: 21590-1.5.txt, HBASE-21590-master.txt, 
> HBASE-21590.addendum.v1.patch
>
>
> See latest comment on HBASE-17958



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21728) Backport to branch-2 (and maybe branch-1) HBASE-21684 Throw DNRIOE when connection or rpc client is closed

[stack (JIRA)]

stack created HBASE-21728:
-

 Summary: Backport to branch-2 (and maybe branch-1) HBASE-21684 
Throw DNRIOE when connection or rpc client is closed
 Key: HBASE-21728
 URL: https://issues.apache.org/jira/browse/HBASE-21728
 Project: HBase
  Issue Type: Sub-task
Reporter: stack


Backport the parent. May need a few changes. See suggestions in parent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[ANNOUNCE] Apache Roadshow Chicago, Call for Presentations

[Trevor Grant]

Hello Devs!


You're receiving this email because you are subscribed to one or more
Apache developer email lists.

I’m writing to let you know about an exciting event coming to the Chicago
area: The Apache Roadshow Chicago.  It will be held May 13th and 14th at
three bars in the Logan Square neighborhood (Revolution Brewing, The
Native, and the Radler).

There will be six tracks:

   -

   Apache in Adtech:  Tell us how Apache works in your advertising stack
   -

   Apache in Fintech: Tell us how Apache works in your finance/insurance
   business
   -

   Apache in Startups: Tell us how you’re using Apache in your startup
   -

   Diversity in Apache: How do we increase and encourage diversity in
   Apache and tech fields overall?
   -

   Made in Chicago: Apache related things made by people in Chicago that
   don’t fall into other buckets
   -

   Project Shark Tank: Do you want more developers or users for your Apache
   project? Come here and pitch it!


This is an exciting chance to learn about how Apache Projects are in use in
production around Chicago, how business users make the decision to use
Apache projects, to learn about exciting new projects that want help from
developers like you, and how/why to increase diversity in tech and IT.

If you have any use cases of Apache products in Adtech, Fintech, or
Startups; if you represent a minority working in tech and have perspectives
to share, if you live in the Chicagoland area and want to highlight some
work you’ve done on an Apache project, or if you want to get other people
excited to come work on your project, then please submit a CFP before the
deadline on February 15th!

Tickets to the Apache Roadshow Chicago are $100; speakers will get a
complimentary ticket.

We’re looking forward to reading your submissions and seeing you there on
May 13-14!

Sincerely,

Trevor Grant

https://www.apachecon.com/chiroadshow19/cfp.html

https://www.apachecon.com/chiroadshow19/register.html

[jira] [Created] (HBASE-21727) Simplify documentation around client timeout

[Peter Somogyi (JIRA)]

Peter Somogyi created HBASE-21727:
-

 Summary: Simplify documentation around client timeout
 Key: HBASE-21727
 URL: https://issues.apache.org/jira/browse/HBASE-21727
 Project: HBase
  Issue Type: Sub-task
Reporter: Peter Somogyi
Assignee: Peter Somogyi
 Fix For: 3.0.0, 2.2.0, 2.1.3


Client rpc timeouts are not easy to understand from the documentation. [~stack] 
also had an idea to point to doc when exception is thrown.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21726) Add getAllRegionLocations method to AsyncTableRegionLocator

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-21726:
-

 Summary: Add getAllRegionLocations method to 
AsyncTableRegionLocator
 Key: HBASE-21726
 URL: https://issues.apache.org/jira/browse/HBASE-21726
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21725) Implement BufferedMutator Based on AsyncBufferedMutator

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-21725:
-

 Summary: Implement BufferedMutator Based on AsyncBufferedMutator
 Key: HBASE-21725
 URL: https://issues.apache.org/jira/browse/HBASE-21725
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21724) Introduce a createClusterConnection method in ClusterConnectionFactory

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-21724:
-

 Summary: Introduce a createClusterConnection method in 
ClusterConnectionFactory
 Key: HBASE-21724
 URL: https://issues.apache.org/jira/browse/HBASE-21724
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang


When we want a  cluster connection in the code, we should use this method to 
create one directly, instead of casting the one created by ConnectionFactory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-21723) Remove ConnectionImplementation and related classes

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-21723:
-

 Summary: Remove ConnectionImplementation and related classes
 Key: HBASE-21723
 URL: https://issues.apache.org/jira/browse/HBASE-21723
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang


This is the final goal here. Especially to get rid of the complicated 
AsyncProcess class.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-21685) Change repository urls to Gitbox

[Peter Somogyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Somogyi resolved HBASE-21685.
---
   Resolution: Fixed
Fix Version/s: 1.2.11
   1.3.4
   2.0.5
   2.1.3
   1.4.10
   2.2.0
   1.5.0

Backported to all branches.

> Change repository urls to Gitbox
> 
>
> Key: HBASE-21685
> URL: https://issues.apache.org/jira/browse/HBASE-21685
> Project: HBase
>  Issue Type: Task
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.2.0, 1.4.10, 2.1.3, 2.0.5, 1.3.4, 1.2.11
>
> Attachments: HBASE-21685.master.001.patch, 
> HBASE-21685.master.001.patch
>
>
> Moving to Gitbox is approaching and references to git-wip-us need to be 
> changed to gitbox.
> Some of the Jenkins jobs are referring to git-wip-us which if going to be 
> locked after the migration. We could move them to github so the build flow 
> will remain intact.
> Previous discussion on dev@: 
> [https://lists.apache.org/thread.html/3496568d6cc002f74f5c3bcce46ed44b7ee9e90d7d53af2c65b6f785@%3Cdev.hbase.apache.org%3E]
>  After this notify INFRA to make the change



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (HBASE-21685) Change repository urls to Gitbox

[Peter Somogyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Somogyi reopened HBASE-21685:
---

Reopen for backporting.

> Change repository urls to Gitbox
> 
>
> Key: HBASE-21685
> URL: https://issues.apache.org/jira/browse/HBASE-21685
> Project: HBase
>  Issue Type: Task
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HBASE-21685.master.001.patch, 
> HBASE-21685.master.001.patch
>
>
> Moving to Gitbox is approaching and references to git-wip-us need to be 
> changed to gitbox.
> Some of the Jenkins jobs are referring to git-wip-us which if going to be 
> locked after the migration. We could move them to github so the build flow 
> will remain intact.
> Previous discussion on dev@: 
> [https://lists.apache.org/thread.html/3496568d6cc002f74f5c3bcce46ed44b7ee9e90d7d53af2c65b6f785@%3Cdev.hbase.apache.org%3E]
>  After this notify INFRA to make the change



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (HBASE-21712) Make submit-patch.py python3 compatible

[Peter Somogyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-21712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Somogyi reopened HBASE-21712:
---

Reopening to add addendum and backport to active branches. [~tommyzli] could 
you attach the patch here?

> Make submit-patch.py python3 compatible
> ---
>
> Key: HBASE-21712
> URL: https://issues.apache.org/jira/browse/HBASE-21712
> Project: HBase
>  Issue Type: Improvement
>  Components: tooling
>Reporter: Tommy Li
>Assignee: Tommy Li
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-21712.master.001.patch, 
> HBASE-21712.master.002.patch
>
>
> Attached patch was submitted with `python3 dev-support/submit-patch.py -b 
> master -srb -jid HBASE-21712`



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)