Hi all Interesting case with Stripe compactions and Encryptions. Does any one has any suggestion for Karthick's case? The initial mail was targetted to issues@ and so forwarding it to dev@ and user@.
Regards Ram ---------- Forwarded message ---------- From: ramkrishna vasudevan <ramkrishna.s.vasude...@gmail.com> Date: Tue, Jun 20, 2017 at 4:51 PM Subject: Re: Encryption of exisiting data in Stripe Compaction To: Karthick Ram <karthik.28...@gmail.com> I am not aware of any other mechanism. I just noticed that you had fwded the message to issues@ and not to dev@ and users@. Let me forward it to those mailing address. Thanks Karthick. Regards Ram On Mon, Jun 19, 2017 at 1:07 PM, Karthick Ram <karthik.28...@gmail.com> wrote: > Hi, > Yes we are doing exactly the same. We altered the table with > exploringcompaction and triggered a major compaction. But when it comes to > key rotation, which we do very often, we have to manually alter the table > and rollback to previous compaction policy. Currently we have a cron job > for this. Is there any other way to automate this? > > Regards > Karthick R > > On Thu, Jun 15, 2017 at 9:55 AM, ramkrishna vasudevan < > ramkrishna.s.vasude...@gmail.com> wrote: > >> Hi >> 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 >> compaction. >> >> Regards >> Ram >> >> On Wed, Jun 14, 2017 at 10:25 AM, Karthick Ram <karthik.28...@gmail.com> >> wrote: >> >>> 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 >>> >> >> >
