phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5306) Misleading statement in document
Date Thu, 30 May 2019 22:23:00 GMT

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

Josh Elser commented on PHOENIX-5306:
-------------------------------------

{quote}how would you suggest to rephrase it, so it is more accurate in your opinion?
{quote}
Yeah, I think blindly removing it isn't great. What about..

"This is important in HBase as there are limits to the number of Regions which HBase can manage.
Limiting the number of tables can help limit the number of Regions in a cluster."

> 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)

Mime
View raw message