Re: [DISCUSS] Allow namespace admins to clone snapshots created by them

[Duo Zhang]

+1 on releasing 2.6.0 sooner.

And I think it is time to EOL 2.4.x after we release 2.6.0?

Bryan Beaudreault  于2023年1月3日周二 21:02写道：
>
> I think development is done on TLS. We are just waiting on requested
> testing. Andor was working on that, but I believe he had some stuff come up
> at his work.
>
> I also want to get backups in place, but there is 1 backwards compatibility
> issue to work through. Hoping to have that squared away soon.
>
> On Sat, Dec 31, 2022 at 9:32 PM Andrew Purtell 
> wrote:
>
> > +1
> >
> > If this is needed soon in a release we could start on 2.6.0?
> >
> > (How is TLS RPC coming along? - that would be the big ticket item.)
> >
> > > On Dec 23, 2022, at 7:06 AM, 张铎  wrote:
> > >
> > > This is a behavior change, it makes non admin users can clone snapshot.
> > >
> > > For me I do not think we should include changes like this in a patch
> > > release, unless it is considered as a critical bug which must be
> > > fixed.
> > >
> > > Thanks.
> > >
> > > Szabolcs Bukros  于2022年11月30日周三 00:06写道：
> > >>
> > >> This should not break any existing use case so I see no reason to not
> > add
> > >> this to branch-2.5 and
> > >> branch-2.4.
> > >>
> > >>> On Thu, Nov 24, 2022 at 3:03 AM 张铎(Duo Zhang) 
> > wrote:
> > >>>
> > >>> I'm OK with this change.
> > >>>
> > >>> But maybe we still need to determine which branches we can apply this
> > >>> change to? Is it OK to include this change for branch-2.5 and
> > >>> branch-2.4?
> > >>>
> > >>> Tak Lon (Stephen) Wu  于2022年11月22日周二 06:31写道：
> > 
> >  FYI the PR is https://github.com/apache/hbase/pull/4885
> > 
> > and
> >  https://issues.apache.org/jira/browse/HBASE-27493
> > 
> > .
> > 
> >  the proposal seems to be, should we allow cloning snapshot to any
> >  namespace if they're not the global admin.
> > 
> >  logically, it should be fine because they're the admin for the
> >  namespace, and should be able to do whatever within that namespace.
> > 
> >  Thanks,
> >  Stephen
> > 
> > 
> >  On Mon, Nov 21, 2022 at 11:38 AM Szabolcs Bukros
> >   wrote:
> > >
> > > Hi Everyone,
> > >
> > > Creating a snapshot requires table admin permissions. But cloning it
> > > requires global admin permissions unless the user owns the snapshot
> > and
> > > wants to recreate the original table the snapshot was based on using
> > >>> the
> > > same table name. This puts unnecessary load on the few users having
> > >>> global
> > > admin permissions on the cluster. I would like to relax this rule a
> > >>> bit and
> > > allow the owner of the snapshot to clone it into any namespace where
> > >>> they
> > > have admin permissions regardless of the table name used.
> > >
> > > Please let me know what you think about this proposal. And if you
> > find
> > >>> it
> > > acceptable which branch do you think this could land on.
> > >
> > > Thanks,
> > > Szabolcs Bukros
> > >>>
> >

Spark reading from HBase using hbase-connectors - any benefit from localization?

[Aaron Grubb]

Hello,

I'm completely new to Spark and evaluating setting up a cluster either in YARN 
or standalone. Our idea for the general workflow is create a concatenated 
dataframe using historical pickle/parquet files (whichever is faster) and 
current data stored in HBase. I'm aware of the benefit of short circuit reads 
if the historical files are stored in HDFS but I'm more concerned about 
resource contention between Spark and HBase during data loading. My question 
is, would running Spark on the same nodes provide a benefit when using 
hbase-connectors 
(https://github.com/apache/hbase-connectors/tree/master/spark)? Is there a 
mechanism in the connector to "pass through" a short circuit read to Spark, or 
would data always bounce from HDFS -> RegionServer -> Spark?

Thanks in advance,
Aaron

Re: [DISCUSS] Allow namespace admins to clone snapshots created by them

[Bryan Beaudreault]

I think development is done on TLS. We are just waiting on requested
testing. Andor was working on that, but I believe he had some stuff come up
at his work.

I also want to get backups in place, but there is 1 backwards compatibility
issue to work through. Hoping to have that squared away soon.

On Sat, Dec 31, 2022 at 9:32 PM Andrew Purtell 
wrote:

> +1
>
> If this is needed soon in a release we could start on 2.6.0?
>
> (How is TLS RPC coming along? - that would be the big ticket item.)
>
> > On Dec 23, 2022, at 7:06 AM, 张铎  wrote:
> >
> > This is a behavior change, it makes non admin users can clone snapshot.
> >
> > For me I do not think we should include changes like this in a patch
> > release, unless it is considered as a critical bug which must be
> > fixed.
> >
> > Thanks.
> >
> > Szabolcs Bukros  于2022年11月30日周三 00:06写道：
> >>
> >> This should not break any existing use case so I see no reason to not
> add
> >> this to branch-2.5 and
> >> branch-2.4.
> >>
> >>> On Thu, Nov 24, 2022 at 3:03 AM 张铎(Duo Zhang) 
> wrote:
> >>>
> >>> I'm OK with this change.
> >>>
> >>> But maybe we still need to determine which branches we can apply this
> >>> change to? Is it OK to include this change for branch-2.5 and
> >>> branch-2.4?
> >>>
> >>> Tak Lon (Stephen) Wu  于2022年11月22日周二 06:31写道：
> 
>  FYI the PR is https://github.com/apache/hbase/pull/4885
> 
> and
>  https://issues.apache.org/jira/browse/HBASE-27493
> 
> .
> 
>  the proposal seems to be, should we allow cloning snapshot to any
>  namespace if they're not the global admin.
> 
>  logically, it should be fine because they're the admin for the
>  namespace, and should be able to do whatever within that namespace.
> 
>  Thanks,
>  Stephen
> 
> 
>  On Mon, Nov 21, 2022 at 11:38 AM Szabolcs Bukros
>   wrote:
> >
> > Hi Everyone,
> >
> > Creating a snapshot requires table admin permissions. But cloning it
> > requires global admin permissions unless the user owns the snapshot
> and
> > wants to recreate the original table the snapshot was based on using
> >>> the
> > same table name. This puts unnecessary load on the few users having
> >>> global
> > admin permissions on the cluster. I would like to relax this rule a
> >>> bit and
> > allow the owner of the snapshot to clone it into any namespace where
> >>> they
> > have admin permissions regardless of the table name used.
> >
> > Please let me know what you think about this proposal. And if you
> find
> >>> it
> > acceptable which branch do you think this could land on.
> >
> > Thanks,
> > Szabolcs Bukros
> >>>
>