hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkrishna vasudevan <ramkrishna.s.vasude...@gmail.com>
Subject Re: Encryption of exisiting data in Stripe Compaction
Date Thu, 15 Jun 2017 04:25:59 GMT
Very interesting case. Ya Stripe compaction does not need to under go a
major compaction if it already running under stripe compaction (reading the
docs I get this).
Since you have enable encryption at a later point of time you face this
issue I believe. The naive workaround I can think of is that do a alter
table with default compaction and it will do a major compaction and once
that is done again move back to Stripe compaction?  Will that work?

I would like to hear opinion of others who have experience with Strip


On Wed, Jun 14, 2017 at 10:25 AM, Karthick Ram <karthik.28696@gmail.com>

> We have a table which has time series data with Stripe Compaction enabled.
> After encryption has been enabled for this table the newer entries are
> encrypted and inserted. However to encrypt the existing data in the table,
> a major compaction has to run. Since, stripe compaction doesn't allow a
> major compaction to run, we are unable to encrypt the previous data. Please
> suggest some ways to rectify this problem.
> Regards,
> Karthick R

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message