Re: [DISCUSS] Move stable pointer to 2.5.x

2023-05-05 Thread Andrew Purtell 
+1


> On May 5, 2023, at 12:13 AM, 张铎  wrote:
> 
> As discussed in the online meeting, and also other places, before EOL
> 2.4.x, we should first move our stable pointer to 2.5.x.
> 
> And there are also som2.5.x  usages around the community on large clusters
> which proves that the release can be considered as 'stable'.
> 
> Let's do a lazy consensus here. If no big concerns within several days, I
> will open a issue to change the stable pointer to 2.5.x.
> 
> Thanks.

Re: [DISCUSS] Move stable pointer to 2.5.x

2023-05-05 Thread Tak Lon (Stephen) Wu 
+1 and thanks !

-Stephen

On Fri, May 5, 2023 at 6:50 AM Bryan Beaudreault 
wrote:

> +1
>
> On Fri, May 5, 2023 at 9:42 AM Chintaguntla, Rajeshbabu
>  wrote:
>
> > +1
> >
> > Get Outlook for Android
> > 
> > From: Nick Dimiduk 
> > Sent: Friday, May 5, 2023 3:00:19 PM
> > To: dev@hbase.apache.org 
> > Subject: Re: [DISCUSS] Move stable pointer to 2.5.x
> >
> > +1
> >
> > On Fri, 5 May 2023 at 09:13, 张铎(Duo Zhang) 
> wrote:
> >
> > > As discussed in the online meeting, and also other places, before EOL
> > > 2.4.x, we should first move our stable pointer to 2.5.x.
> > >
> > > And there are also som2.5.x  usages around the community on large
> > clusters
> > > which proves that the release can be considered as 'stable'.
> > >
> > > Let's do a lazy consensus here. If no big concerns within several
> days, I
> > > will open a issue to change the stable pointer to 2.5.x.
> > >
> > > Thanks.
> > >
> >
>
-- 
Sent from Gmail Mobile

Re: [ANNOUNCE] New HBase committer Nihal Jain

2023-05-05 Thread Pankaj Kumar 
Congratulations Nihal !!

Regards,
Pankaj


On Wed, May 3, 2023 at 5:42 PM Nick Dimiduk  wrote:

> Hello!
>
> On behalf of the Apache HBase PMC, I am pleased to announce that Nihal Jain
> has accepted the PMC's invitation to become a committer on the project. We
> appreciate all of Nihal's generous contributions thus far and look forward
> to his continued involvement.
>
> Congratulations and welcome, Nihal Jain!
>
> Thanks,
> Nick
>

[jira] [Created] (HBASE-27848) Should fast-fail if unmatched column family exists when using ImportTsv

2023-05-05 Thread guluo (Jira) 
guluo created HBASE-27848:
-

 Summary: Should fast-fail if unmatched column family exists when 
using ImportTsv
 Key: HBASE-27848
 URL: https://issues.apache.org/jira/browse/HBASE-27848
 Project: HBase
  Issue Type: Improvement
  Components: mapreduce
Affects Versions: 2.4.13
 Environment: Centos 7

HBase 2.4.13
Reporter: guluo


Executing cmd as following:
{code:java}
//code
hbase org.apache.hadoop.hbase.mapreduce.ImportTsv -Dimporttsv.separator=, 
-Dimporttsv.columns=HBASE_ROW_KEY,temp01_error01:first_name,temp01_error02:last_name
 test_hbase hdfs:///tmp/hbase_data.csv {code}
If We specify a error column family(it does not exists), this operation would 
not fail until MR job is executed

It is better to fast-fail before MR is submitted if we specify a error column 
family



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Move stable pointer to 2.5.x

2023-05-05 Thread Bryan Beaudreault 
+1

On Fri, May 5, 2023 at 9:42 AM Chintaguntla, Rajeshbabu
 wrote:

> +1
>
> Get Outlook for Android
> 
> From: Nick Dimiduk 
> Sent: Friday, May 5, 2023 3:00:19 PM
> To: dev@hbase.apache.org 
> Subject: Re: [DISCUSS] Move stable pointer to 2.5.x
>
> +1
>
> On Fri, 5 May 2023 at 09:13, 张铎(Duo Zhang)  wrote:
>
> > As discussed in the online meeting, and also other places, before EOL
> > 2.4.x, we should first move our stable pointer to 2.5.x.
> >
> > And there are also som2.5.x  usages around the community on large
> clusters
> > which proves that the release can be considered as 'stable'.
> >
> > Let's do a lazy consensus here. If no big concerns within several days, I
> > will open a issue to change the stable pointer to 2.5.x.
> >
> > Thanks.
> >
>

Re: [DISCUSS] Move stable pointer to 2.5.x

2023-05-05 Thread Chintaguntla, Rajeshbabu 
+1

Get Outlook for Android

From: Nick Dimiduk 
Sent: Friday, May 5, 2023 3:00:19 PM
To: dev@hbase.apache.org 
Subject: Re: [DISCUSS] Move stable pointer to 2.5.x

+1

On Fri, 5 May 2023 at 09:13, 张铎(Duo Zhang)  wrote:

> As discussed in the online meeting, and also other places, before EOL
> 2.4.x, we should first move our stable pointer to 2.5.x.
>
> And there are also som2.5.x  usages around the community on large clusters
> which proves that the release can be considered as 'stable'.
>
> Let's do a lazy consensus here. If no big concerns within several days, I
> will open a issue to change the stable pointer to 2.5.x.
>
> Thanks.
>

[jira] [Created] (HBASE-27847) Introduce HBase image

2023-05-05 Thread Nick Dimiduk (Jira) 
Nick Dimiduk created HBASE-27847:


 Summary: Introduce HBase image
 Key: HBASE-27847
 URL: https://issues.apache.org/jira/browse/HBASE-27847
 Project: HBase
  Issue Type: Sub-task
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
 Fix For: HBASE-27827


As with the Hadoop image (HBASE-27846), we need a runtime image for the HBase 
containers, and we need a place to define an API between the runtime image and 
the orchestration layer. HBase project doesn't ship an image yet, so this will 
provide double-duty.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (HBASE-27846) Introduce hadoop image

2023-05-05 Thread Nick Dimiduk (Jira) 
Nick Dimiduk created HBASE-27846:


 Summary: Introduce hadoop image
 Key: HBASE-27846
 URL: https://issues.apache.org/jira/browse/HBASE-27846
 Project: HBase
  Issue Type: Sub-task
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk


The image shipped by upstream requires some tweaks. Extend it to suit our needs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Move stable pointer to 2.5.x

2023-05-05 Thread Nick Dimiduk 
+1

On Fri, 5 May 2023 at 09:13, 张铎(Duo Zhang)  wrote:

> As discussed in the online meeting, and also other places, before EOL
> 2.4.x, we should first move our stable pointer to 2.5.x.
>
> And there are also som2.5.x  usages around the community on large clusters
> which proves that the release can be considered as 'stable'.
>
> Let's do a lazy consensus here. If no big concerns within several days, I
> will open a issue to change the stable pointer to 2.5.x.
>
> Thanks.
>

[jira] [Created] (HBASE-27845) Distinguish the mutate type of rpc error in MetricsConnection

2023-05-05 Thread zhuyaogai (Jira) 
zhuyaogai created HBASE-27845:
-

 Summary: Distinguish the mutate type of rpc error in 
MetricsConnection
 Key: HBASE-27845
 URL: https://issues.apache.org/jira/browse/HBASE-27845
 Project: HBase
  Issue Type: Improvement
Reporter: zhuyaogai


There are four mutate types in HBase, including {_}Append{_}, {_}Delete{_}, 
{_}Increment{_}, and _Put._ However, when rpc error occurs on the client, 
mutate types are not distinguished in MetricsConnection.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[DISCUSS] Move stable pointer to 2.5.x

2023-05-05 Thread Duo Zhang 
As discussed in the online meeting, and also other places, before EOL
2.4.x, we should first move our stable pointer to 2.5.x.

And there are also som2.5.x  usages around the community on large clusters
which proves that the release can be considered as 'stable'.

Let's do a lazy consensus here. If no big concerns within several days, I
will open a issue to change the stable pointer to 2.5.x.

Thanks.