[ 
https://issues.apache.org/jira/browse/PHOENIX-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939438#comment-15939438
 ] 

Peter Conrad commented on PHOENIX-3718:
---------------------------------------

I'm looking at this now, it's really great! I have a few questions.

> For more details on the benefits of using column mapping and immutable data 
> encoding, go to this blog.
I don't see a link.

> think about how many columns you expect in a table and its view hierarchy to 
> have in the lifecycle.
I get the part about planning the number of columns ahead of time, but I don't 
know what "its view hierarchy to have in the lifecycle" means.
It seems like the column mapping property is meant to limit the number of 
columns, since if you don't set it the columns are theoretically unlimited. Is 
that right?

It sounds like phoenix.default.column.encoded.bytes.attrib controls the default 
column mapping property for all tables, and COLUMN_ENCODED_BYTES controls the 
column mapping property for one table as you create it. Is that the case? 

Does it make sense to give a sentence declaring what "single cell array with 
offsets" and "one cell per column" mean and how they differ? Is there any 
effect on sharding for one versus the other?

Once I get these answers, would you be okay with me making edits myself and 
attaching a new .md file for you to review?




> Provide user-level documentation for column encoding feature
> ------------------------------------------------------------
>
>                 Key: PHOENIX-3718
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3718
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Samarth Jain
>         Attachments: columnencoding.md
>
>
> Let's create a new page on our site describing column encoding. I think we 
> should keep it at a very high level, but document when the feature should and 
> should not be used.
> A blog with more technical depth on the implementation might be interesting, 
> though. You up for that [~samarthjain]?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to