Want to make a new issue then Andrey?  Thanks.  We could knock out
hbase-68 at same time.  When would we do the replacement of code with
actual columnfamily name?  Over on client or on server before result
is sent the client?
St.Ack

On Sun, Jan 9, 2011 at 12:29 PM, Andrey Stepachev <[email protected]> wrote:
> 2011/1/9 Stack <[email protected]>
>
>>
>> To respond to Andrey, you seem to be asking about the old issue
>> HBASE-68.  It hasn't seen much attention of late.  Its more about
>> saving space rather than facilitating rename (though the latter is a
>> legit case).
>>
>
> Thanks. But saving space is not an issue. Really renaming with going
> offline (rename table) or reload data (rename cf) is issue (especially in
> case of live data migration on version upgrade on production cluster).
>
>
>>
>> St.Ack
>>
>>
>> On Sat, Jan 8, 2011 at 12:10 PM, M. C. Srivas <[email protected]> wrote:
>> > In general. there's need for a loose "schema" to allow not only renames
>> of
>> > columns and column-families, but efficient delete of entire columns or
>> CFs.
>> > (eg, mark this C as deleted in the "schema" and remove it during the next
>> > major compaction). But implementing the master-coordination for this (for
>> > instance, all RS's should delete 'atomically') will be interesting ....
>> >
>> >
>> >
>> > On Sat, Jan 8, 2011 at 11:36 AM, Andrey Stepachev <[email protected]>
>> wrote:
>> >
>> >> 2011/1/8 Stack <[email protected]>
>> >>
>> >> >
>> >> >
>> >>
>> >> > Perhaps we should consider
>> >> > detaching CF name from whats stored?
>> >> >
>> >>
>> >> Yes! Are there any jira? I'll vote for it.
>> >>
>> >>
>> >> >
>> >> > St.Ack
>> >> >
>> >>
>> >
>>
>

Reply via email to