Found the documentation on HBase site:
http://hbase.apache.org/book.html#keysize
On Sun, Jun 14, 2015 at 9:32 PM, anil gupta wrote:
> Hi James,
>
> AFAIK, this trick/practice is being recommended by HBase community. I
> cannot find the doc that says this.
>
> Thanks,
> Anil Gupta
>
> On Sun, Ju
Hi James,
AFAIK, this trick/practice is being recommended by HBase community. I
cannot find the doc that says this.
Thanks,
Anil Gupta
On Sun, Jun 14, 2015 at 7:30 PM, James Taylor
wrote:
> Views won't help you here (and unrelated, but we only support "create view
> select *" but you can alter
Got it. Thanks James, that's what I suspected.
We will wait for the feature :)
Thx,
Yanlin
Sent from my iPhone
> On Jun 14, 2015, at 7:30 PM, James Taylor wrote:
>
> Views won't help you here (and unrelated, but we only support "create view
> select *" but you can alter the view by removin
Views won't help you here (and unrelated, but we only support "create view
select *" but you can alter the view by removing columns after you create
it).
Anil - the space savings Yanlin is looking for is shorter column qualifiers
while still having readable column names.
On Sunday, June 14, 2015,
Hi James,
Sorry, i dont understand the context of "Would be good to quantify the
potential gain with and without FAST_DIFF encoding (the default) and/or
Snappy compression."?
The feature Yanlin is requesting is more for ease of usability/readability.
On Sun, Jun 14, 2015 at 5:59 PM, James Taylor
Thanks James, my team mate will try to create a jira.
BTW, how to use view to archive column name aliasing? What i tried is - create
view my view as select a as appColumn1, b as appColum2 from table , the ddl got
rejected. Did i miss anything?
Thx,
Yanlin
> On Jun 14, 2015, at 5:59 PM, Jam
Good idea. Please file a JIRA. Would be good to quantify the potential gain
with and without FAST_DIFF encoding (the default) and/or Snappy compression.
On Sunday, June 14, 2015, yanlin wang wrote:
> Thanks for the reply Anil.
>
> Is this what you referring:
> create view my view as
> select a a
Thanks for the reply Anil.
Is this what you referring:
create view my view as
select a as appColumn1, b as appColum2 from table ?
By reading the document, seems view will introduce limitations e.g schema
update issue. It would be really good if phoenix put the auto aliasing column
name support
Hi Yanlin,
If you are doing reads. You can use a view.
For writes, i dont think Phoenix provides anything for aliasing column
names. It would be good if we have this feature because using short column
names is a common thing in HBase.
Thanks,
Anil Gupta
On Sun, Jun 14, 2015 at 12:19 PM, yanlin w
Hi,
Usually one method to reduce IO in hbase is to reduce the size of column
qualifier’s length and use a dictionary to map the application column name to
the actual column qualifier. Kiji schema project is doing exactly that. Is
there any column name encoding support in Phoenix? if no, any pla
10 matches
Mail list logo
