From issues-return-7253-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Thu May 30 22:23:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id C231F180638 for ; Fri, 31 May 2019 00:23:01 +0200 (CEST) Received: (qmail 47232 invoked by uid 500); 30 May 2019 22:23:01 -0000 Mailing-List: contact issues-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list issues@phoenix.apache.org Received: (qmail 47221 invoked by uid 99); 30 May 2019 22:23:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 May 2019 22:23:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5B443E0A4B for ; Thu, 30 May 2019 22:23:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1652824599 for ; Thu, 30 May 2019 22:23:00 +0000 (UTC) Date: Thu, 30 May 2019 22:23:00 +0000 (UTC) From: "Josh Elser (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-5306) Misleading statement in document MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-5306?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 852411#comment-16852411 ]=20 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 wh= ich HBase can manage. Limiting the number of tables can help limit the numb= er 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/v= iews.md]=C2=A0 has the following misleading statement as HBase scaling is n= ot 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 ta= bles 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)