[
https://issues.apache.org/jira/browse/PHOENIX-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851402#comment-16851402
]
William Shen commented on PHOENIX-5306:
---------------------------------------
[~krishnam] - "This is especially important in HBase, as you cannot
realistically expect to have more than perhaps up to a hundred physical tables
and continue to get reasonable performance from HBase" seems to be an attempt
to explain the meaningfulness of the feature. Instead of just removing it, how
would you suggest to rephrase it, so it is more accurate in your opinion?
> Misleading statement in document
> --------------------------------
>
> Key: PHOENIX-5306
> URL: https://issues.apache.org/jira/browse/PHOENIX-5306
> Project: Phoenix
> Issue Type: Bug
> Reporter: Krishna Maheshwari
> Priority: Minor
>
> [https://svn.apache.org/repos/asf/phoenix/site/source/src/site/markdown/views.md]
> has the following misleading statement as HBase scaling is not limited by
> number of tables but rather number of overall regions.
> "The standard SQL view syntax (with some limitations) is now supported by
> Phoenix to enable multiple virtual tables to all share the same underlying
> physical HBase table. This is especially important in HBase, as you cannot
> realistically expect to have more than perhaps up to a hundred physical
> tables and continue to get reasonable performance from HBase."
> This should be revised to state:
> "The standard SQL view syntax (with some limitations) is now supported by
> Phoenix to enable multiple virtual tables to all share the same underlying
> physical HBase table."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
