[
https://issues.apache.org/jira/browse/PHOENIX-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170982#comment-17170982
]
Xinyi Yan commented on PHOENIX-6061:
------------------------------------
cc [~ckulkarni] [~dbwong]
> optimize the estimated mutation size
> -------------------------------------
>
> Key: PHOENIX-6061
> URL: https://issues.apache.org/jira/browse/PHOENIX-6061
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Xinyi Yan
> Priority: Major
>
> The current max mutation size is estimated by jvm level column size plus
> column family size. See
> [https://github.com/apache/phoenix/blob/master/phoenix-core/src/main/java/org/apache/phoenix/schema/PNameImpl.java#L48]
> This is very expansive in terms of space. Most of the use cases are upserting
> to the same table/columns and storing the same column/column family. Think
> about the case where we upsert into 100 rows to the Dummy table(10 columns,
> COL1, COL2,... COL10). Phoenix calculates the estimate 10 columns and column
> family for each row, and this metadata info has to 100 times. We probably
> can do something smarter there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
