Hi Mujtaba, Thank you for your immediate response.
I read the link and the blog. and still cannot conclude the advise for MUTABLE tables :( Invariably most of our tables are MUTABLE, meaning updates *will *occur. So in that case... Should we keep our *table *names short? and Should we keep our *column *names short? Based on the link and the blog - I understand that we can get away with long names for IMMUTABLE tables - (Updates do not occur) please help. thanks, -ash On Tue, May 30, 2017 at 4:16 PM, Mujtaba Chohan <mujt...@apache.org> wrote: > Holds true for Phoenix as well and it provides built-in support for column > mapping so you can still use long column names, see > http://phoenix.apache.org/columnencoding.html. Also see related > performance optimization, SINGLE_CELL_ARRAY_WITH_OFFSETS encoding for > immutable data. > > On Tue, May 30, 2017 at 1:09 PM, Ash N <742...@gmail.com> wrote: > >> Hello All, >> >> it is recommended to keep HBase column family and attribute names short. >> does this recommendation apply to Apache Phoenix as well? >> Keep the table and column names short? >> >> 6.3.2.1. Column Families >> >> Try to keep the ColumnFamily names as small as possible, preferably one >> character (e.g. "d" for data/default). >> >> See Section 9.7.5.4, “KeyValue” >> <http://hbase.apache.org/0.94/book/regions.arch.html#keyvalue> for more >> information on HBase stores data internally to see why this is important. >> 6.3.2.2. Attributes >> >> Although verbose attribute names (e.g., "myVeryImportantAttribute") are >> easier to read, prefer shorter attribute names (e.g., "via") to store in >> HBase. >> >> See Section 9.7.5.4, “KeyValue” >> <http://hbase.apache.org/0.94/book/regions.arch.html#keyvalue> for more >> information on HBase stores data internally to see why this is important. >> >> thanks for your help. >> >> -ash >> >> >> >> >
