#14220: Default schema selected will be the first schema from the schema list after reconnecting server.

nileshhmali reported 2016-01-21T08:16:13Z · last modified 2016-01-26T19:55:37Z

Default schema selected will be the first schema from the schema list after reconnecting server.

Dev	JennyNishimura
QA	SachinPrakash

Priority	Low
Complexity	Unknown

Component	Q Analyzer
Version	17.0

Product: Aqua Data Studio

Version: 17.0.0-ga-31

Build #: 48298

Build Date: 2016-Jan-20 07:54:23 PM

Operating Environment: Linux (3.19.0-15-generic, amd64) / UTF-8 / en / US / Oracle Corporation 1.8.0_40-b26

Memory: Max=704,643,072; Total=382,205,952; Free=158,202,152; CPUs=8

1)Connect Apache derby-10.11

2)Create schema

CREATE SCHEMA "Test_14144"

3)Right click on created schema "Test_14144" and select Query analyzer option

4)QA window opens with selected schema

5)Go Schema browser tree node.

6)Right click on schema "Test_14144" and select drop schema option.

7)Schema dropped successfully.

8)Go to Query analyzer window(step-04 QA window).

9)Click on reconnect icon.

10)Reconnect window opens.

11)Click on yes button.

12)Change schema failed window opens.

13)click on OK button.

Actual result:

Here,you can see that,default schema selected will be the first schema from the schema list.

Expected result:

It should select "APP" schema as default schema in schema drop-down.

Observation:

1)Execute above scenario,

default schema selected will be the first schema from the schema list.

Execute select * from "person" on QA window.

Here,i have observed that,Schema drop down refreshed and selected 'APP' schema.

2)Broken build info:

Please refer issue #14144

4 attachments

Default _First_Schema.png

2016-01-21T08:16:13Z

363 KB
Hortonworks.png

2016-01-21T09:45:01Z

84 KB
Reopening_for_DB2-LUW.png

2016-01-25T05:33:14Z

436 KB
mapr.png

2016-01-25T08:45:39Z

294 KB

All Comments (7) Change History

nileshhmali 2016-01-21T09:31:36Z · (edited)

Same issue we have observed in Oracle12c,SAP HANA-1.0,DB2-LUW also.

laxdeep(*) 2016-01-21T09:44:43Z

I have executed the above scenario for db Hortonworks 2.3 Hive 1.2.1. It is observed that, after reconnecting the server, database drop down shows first db name but when executing show tables command, it displays the error message "Database does not exist: testingdb". Please refer:( Hortonworks.png)

JennyNishimura 2016-01-21T20:58:51Z

Issue #14144 took care of setting the Database drop-down to the current database context but didn't fix the Schema drop-down. This issue has now fixed the Schema drop-down as well.

nileshhmali 2016-01-25T05:32:45Z

Above scenario is fixed for SAP HANA,Orcale12,Apache derby.

Reopening it for DB2-LUW,please handle below scenario.

Product: Aqua Data Studio

Version: 17.0.0-ga-34

1)Connect DB2-LUW

2)Create schema

CREATE SCHEMA "Test_schema"

3)Right click on created schema "Test_schema" and select Query analyzer option

4)QA window opens with selected schema

5)Go Schema browser tree node.

6)Right click on schema "Test_schema" and select drop schema option.

7)Schema dropped successfully.

8)Go to Query analyzer window(step-04 QA window).

9)Click on reconnect icon.

10)Reconnect window opens.

11)Click on yes button.

Actual result:

Here,you can see that,default schema selected will be the first schema from the schema list.

Expected result:

It should select "DB2INST1" schema as default schema in schema drop-down.

Please refer screenshot Reopening_for_DB2-LUW.png

laxdeep(*) 2016-01-25T08:50:34Z

I executed the above scenario-1 for MapR 4.1.0-Impala. After clicking on 'reconnect' button, it shows Error Message. "Error in getting HiveConnection."

Please refer "mapr.png"

Note:After that if I open 'Query Analyzer' for any database, it opens successfully.

JennyNishimura 2016-01-25T18:23:58Z · (edited)

During Reconnect, we issue SET CURRENT_SCHEMA = "Test_schema". DB2-LUW doesn't return an error even though the schema no longer exists. (Check the SQL Log; the SET CURRENT_SCHEMA command is successful.)

Therefore, we think that the schema context is still Test_schema. Since it doesn't exist in the schema list, the first schema is selected in the schema drop-down.

This problem exists in v16 (and possibly earlier versions) also. It is not caused by the fix for this issue. I've opened issue #14234 to look into fixing this problem in v18.

tariqrahiman 2016-01-26T19:55:37Z

Verified in ADS v17.0.0-ga-38. Will check with Anil on the Hive issue

Search Tips

Aqua Data Studio / nhilam

Default schema selected will be the first schema from the schema list after reconnecting server.

4 attachments

Issue #14220

Completion

1 issue link

Issue #14144

Search Tips

Aqua Data Studio / nhilam

Title

Default schema selected will be the first schema from the schema list after reconnecting server.

4 attachments

Issue #14220

Completion

1 issue link

Issue #14144