[jira] [Updated] (HIVE-11657) HIVE-2573 introduces some issues during metastore init (and CLI init)

2015-08-28 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-11657:

Summary: HIVE-2573 introduces some issues during metastore init (and CLI 
init)  (was: HIVE-2573 introduces some issues)

 HIVE-2573 introduces some issues during metastore init (and CLI init)
 -

 Key: HIVE-11657
 URL: https://issues.apache.org/jira/browse/HIVE-11657
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
Priority: Critical
 Attachments: HIVE-11657.patch


 HIVE-2573 introduced static reload functions call.
 It has a few problems:
 1) When metastore client is initialized using an externally supplied config 
 (i.e. Hive.get(HiveConf)), it still gets called during static init using the 
 main service config. In my case, even though I have uris in the supplied 
 config to connect to remote MS (which eventually happens), the static call 
 creates objectstore, which is undesirable.
 2) It breaks compat - old metastores do not support this call so new clients 
 will fail, and there's no workaround like not using a new feature because the 
 static call is always made



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-11657) HIVE-2573 introduces some issues

2015-08-28 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-11657:

Attachment: HIVE-11657.patch

This changes the reloadFunctions call to be done once globally, but on the 
object, so that it is done after the proper config is set. 

It also improves retry logic to not retry on some non-recoverable errors, like 
a missing method.

[~gopalv] [~ashutoshc] can you take a look

 HIVE-2573 introduces some issues
 

 Key: HIVE-11657
 URL: https://issues.apache.org/jira/browse/HIVE-11657
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Assignee: Sergey Shelukhin
Priority: Critical
 Attachments: HIVE-11657.patch


 HIVE-2573 introduced static reload functions call.
 It has a few problems:
 1) When metastore client is initialized using an externally supplied config 
 (i.e. Hive.get(HiveConf)), it still gets called during static init using the 
 main service config. In my case, even though I have uris in the supplied 
 config to connect to remote MS (which eventually happens), the static call 
 creates objectstore, which is undesirable.
 2) It breaks compat - old metastores do not support this call so new clients 
 will fail, and there's no workaround like not using a new feature because the 
 static call is always made



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-11657) HIVE-2573 introduces some issues

2015-08-26 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-11657:

Description: 
HIVE-2573 introduced static reload functions call.
It has a few problems:
1) When metastore client is initialized using an externally supplied config 
(i.e. Hive.get(HiveConf)), it still gets called during static init using the 
main service config. In my case, even though I have uris in the supplied config 
to connect to remote MS (which eventually happens), the static call creates 
objectstore, which is undesirable.
2) It breaks compat - old metastores do not support this call so new clients 
will fail, and there's no workaround like not using a new feature because the 
static call is always made

  was:
HIVE-2573 introduced static reload functions call.
It has a few problems:
1) When metastore client is initialized using an externally supplied config, it 
still gets called during static init using the main service config. In my case, 
even though I have uris in the supplied config to connect to remote MS (which 
eventually happens), the static call creates objectstore, which is undesirable.
2) It breaks compat - old metastores do not support this call so new clients 
will fail, and there's no workaround like not using a new feature because the 
static call is always made


 HIVE-2573 introduces some issues
 

 Key: HIVE-11657
 URL: https://issues.apache.org/jira/browse/HIVE-11657
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Priority: Critical

 HIVE-2573 introduced static reload functions call.
 It has a few problems:
 1) When metastore client is initialized using an externally supplied config 
 (i.e. Hive.get(HiveConf)), it still gets called during static init using the 
 main service config. In my case, even though I have uris in the supplied 
 config to connect to remote MS (which eventually happens), the static call 
 creates objectstore, which is undesirable.
 2) It breaks compat - old metastores do not support this call so new clients 
 will fail, and there's no workaround like not using a new feature because the 
 static call is always made



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-11657) HIVE-2573 introduces some issues

2015-08-26 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-11657:

Description: 
HIVE-2573 introduced static reload functions call.
It has a few problems:
1) When metastore client is initialized using an externally supplied config, it 
still gets called during static init using the main service config. In my case, 
even though I have uris in the supplied config to connect to remote MS (which 
eventually happens), the static call creates objectstore, which is undesirable.
2) It breaks compat - old metastores do not support this call so new clients 
will fail, and there's no workaround like not using a new feature because the 
static call is always made

  was:
HIVE-2573 introduced static reload functions call.
It has a few problems:
1) When metastore client is initialized using an externally supplied config, it 
still gets called during static init using the main service config. In my case, 
even though I have uris in the supplied config to connect to remote MS (which 
eventually happens), the static call creates objectstore, which is undesirable.
2) It breaks compat - old metastores do not support this call so new clients 
will fail


 HIVE-2573 introduces some issues
 

 Key: HIVE-11657
 URL: https://issues.apache.org/jira/browse/HIVE-11657
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Priority: Critical

 HIVE-2573 introduced static reload functions call.
 It has a few problems:
 1) When metastore client is initialized using an externally supplied config, 
 it still gets called during static init using the main service config. In my 
 case, even though I have uris in the supplied config to connect to remote MS 
 (which eventually happens), the static call creates objectstore, which is 
 undesirable.
 2) It breaks compat - old metastores do not support this call so new clients 
 will fail, and there's no workaround like not using a new feature because the 
 static call is always made



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HIVE-11657) HIVE-2573 introduces some issues

2015-08-26 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-11657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-11657:

Description: 
HIVE-2573 introduced static reload functions call.
It has a few problems:
1) When metastore client is initialized using an externally supplied config, it 
still gets called during static init using the main service config. In my case, 
even though I have uris in the supplied config to connect to remote MS (which 
eventually happens), the static call creates objectstore, which is undesirable.
2) It breaks compat - old metastores do not support this call so new clients 
will fail

  was:
HIVE-2573 introduced static reload functions call.
It has a few problems:
1) When metastore client is initialized using an externally supplied config, it 
still gets called during static init using the main service config. In my case, 
even though I have uris in the supplied config to connect to remote MS, the 
static call creates objectstore, which is undesirable.
2) It breaks compat - old metastores do not support this call so new clients 
will fail


 HIVE-2573 introduces some issues
 

 Key: HIVE-11657
 URL: https://issues.apache.org/jira/browse/HIVE-11657
 Project: Hive
  Issue Type: Bug
Reporter: Sergey Shelukhin
Priority: Critical

 HIVE-2573 introduced static reload functions call.
 It has a few problems:
 1) When metastore client is initialized using an externally supplied config, 
 it still gets called during static init using the main service config. In my 
 case, even though I have uris in the supplied config to connect to remote MS 
 (which eventually happens), the static call creates objectstore, which is 
 undesirable.
 2) It breaks compat - old metastores do not support this call so new clients 
 will fail



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)