HI Sumanta, It's obvious. If it's fixed length, serialized values are stored one by one. If data type has variable length, than a special separator is inserted between values.
Thanks, Sergey On Wed, May 25, 2016 at 4:07 AM, Sumanta Gh <sumanta...@tcs.com> wrote: > Hi, > I found that when a VARCHAR ARRAY is stored in Hbase, lots of extra-bytes > are also stored as opposed to FLOAT ARRAY. In terms of better disk > utilization, I think converting non-searchable columns into an ARRAY is > much more efficient. > > Could you please let me know how ARRAY types are stored in HBase. > > - Sumanta > > > -----Sumanta Gh <sumanta...@tcs.com> wrote: ----- > To: user@phoenix.apache.org > From: Sumanta Gh <sumanta...@tcs.com> > Date: 05/13/2016 04:57PM > Subject: Storage benefits of ARRAY types > > > Hi, > Do we gain any disk utilization benefit while defining columns as an array? > > - Sumanta > > > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > >
