[jira] [Updated] (HBASE-10757) Change HTable class doc so it sends people to HCM getting instances
[ https://issues.apache.org/jira/browse/HBASE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10757: -- Fix Version/s: 2.0.0 Assignee: stack Status: Patch Available (was: Open) Change HTable class doc so it sends people to HCM getting instances --- Key: HBASE-10757 URL: https://issues.apache.org/jira/browse/HBASE-10757 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Priority: Critical Fix For: 2.0.0, 0.99.1 Attachments: 10757.txt The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance. Getting an HTable otherwise also makes for some strange issues: See Occasional GSSException that brings down region server on mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10757) Change HTable class doc so it sends people to HCM getting instances
[ https://issues.apache.org/jira/browse/HBASE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10757: -- Attachment: 10757.txt Purges stale javadoc and points folks instead to new way as described over in ConnectionFactory. Is loud about not creating HTable instances directly. Removes all that 'helpful' stuff about connections being shared. I think this patch is enough to get this blocker closed. Nicks comment no long applies after the extensive Connection and Table refactor. Change HTable class doc so it sends people to HCM getting instances --- Key: HBASE-10757 URL: https://issues.apache.org/jira/browse/HBASE-10757 Project: HBase Issue Type: Bug Reporter: stack Priority: Critical Fix For: 2.0.0, 0.99.1 Attachments: 10757.txt The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance. Getting an HTable otherwise also makes for some strange issues: See Occasional GSSException that brings down region server on mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10757) Change HTable class doc so it sends people to HCM getting instances
[ https://issues.apache.org/jira/browse/HBASE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-10757: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for +1 [~enis] Applied to master and branch-1. On deprecating HTable and HBaseAdmin, if the constructors are shutdown, in essence they are effectively unavailable. Deprecating them might be too radical a step. On other hand, the landscape here is shifting fast and a nice clean API is starting to pop out. How about asking the question again around 0.99.3? The answer may be more plain then? Change HTable class doc so it sends people to HCM getting instances --- Key: HBASE-10757 URL: https://issues.apache.org/jira/browse/HBASE-10757 Project: HBase Issue Type: Bug Reporter: stack Assignee: stack Priority: Critical Fix For: 2.0.0, 0.99.1 Attachments: 10757.txt The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance. Getting an HTable otherwise also makes for some strange issues: See Occasional GSSException that brings down region server on mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10757) Change HTable class doc so it sends people to HCM getting instances
[ https://issues.apache.org/jira/browse/HBASE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10757: -- Fix Version/s: (was: 0.99.0) 0.99.1 Change HTable class doc so it sends people to HCM getting instances --- Key: HBASE-10757 URL: https://issues.apache.org/jira/browse/HBASE-10757 Project: HBase Issue Type: Bug Reporter: stack Priority: Blocker Fix For: 0.99.1 The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance. Getting an HTable otherwise also makes for some strange issues: See Occasional GSSException that brings down region server on mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10757) Change HTable class doc so it sends people to HCM getting instances
[ https://issues.apache.org/jira/browse/HBASE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10757: -- Priority: Critical (was: Blocker) Change HTable class doc so it sends people to HCM getting instances --- Key: HBASE-10757 URL: https://issues.apache.org/jira/browse/HBASE-10757 Project: HBase Issue Type: Bug Reporter: stack Priority: Critical Fix For: 0.99.1 The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance. Getting an HTable otherwise also makes for some strange issues: See Occasional GSSException that brings down region server on mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10757) Change HTable class doc so it sends people to HCM getting instances
[ https://issues.apache.org/jira/browse/HBASE-10757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HBASE-10757: -- Fix Version/s: 0.99.0 Change HTable class doc so it sends people to HCM getting instances --- Key: HBASE-10757 URL: https://issues.apache.org/jira/browse/HBASE-10757 Project: HBase Issue Type: Bug Reporter: stack Priority: Blocker Fix For: 0.99.0 The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance. Getting an HTable otherwise also makes for some strange issues: See Occasional GSSException that brings down region server on mailing list. -- This message was sent by Atlassian JIRA (v6.2#6252)
