-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oracle plugin Taking more time to execute the queries #4
Comments
Hi Surendra, Give me more info. What is the volume of the oracle DB you are trying to How big is the cluster you are using? What is the query you are trying to execute? Regards. 2016-08-04 3:33 GMT-03:00 surendraGaddam99 [email protected]:
Atenciosamente, Marcelo Paes Rech. |
Is there any firewall between the servers(Oracle and Presto)? That is weird, because the plugin just call the Oracle Driver directly. It I will try to make a test here, but if you get some news about it let me Regrards. 2016-08-15 4:29 GMT-03:00 surendraGaddam99 [email protected]:
Atenciosamente, Marcelo Paes Rech. |
Hi Marcelo, There is no firewall present between presto and oracle. My presto sql query : For my case i have 100 tables in the list .So above query trying to get columns from all the tables in the schema and getting struck. Actually it should get columns from only cvl_in_color table. Methods are called as shown below. Thanks |
the question solved ? |
No , issue is not yet resolved . Thanks |
I will try to solve this till 20th September. |
Hi Marcelo, Any updates ? Thanks |
Not yet. I didn't have enough time debug, next tuesday I think will have In the older versions of presto it wasn't an issue. Maybe in the new Sorry for time I am taking to see this, last weeks are being very busy. Regards. Em 21 de set de 2016 11:49 PM, "surendraGaddam99" [email protected]
|
I tried to execute queries using Presto 0.147 version and Presto 0.77 version with Oracle plugin. Thanks |
Hi @surendraGaddam99, I have made debug over Oracle plugin and MySQL Plugin and de behaviour you mentioned about multiple calls to getColumns is the same to both (problably to all JDBC plugins). I think in this case an issue in presto Jdbc Base Plugin is needed. I also made few tests use an Oracle database here and nothing about 44s to select small tables as you can see (even with a lot getColumns calls it took 744ms): Could you give me more details about the issue? To me it seems more like environment than the actually plugin issue. If it is the case, maybe I can help too. Regards. |
Hi Marcelo, As mentioned before it is taking more time in getColumns() method as shown below. So i followed below link to get this resolved. Avoid using getColumns() to determine characteristics about a table. Instead, use a dummy query with getMetadata(). Case 2: GetMetadata Method // prepare dummy query After using this code now query execution taking only 2 to 3 sec . Thanks |
What version of the Oracle Drivers are you using? And what is your Oracle As I said before I did queries the same way you did, it really call Regards. Em 4 de out de 2016 3:00 PM, "surendraGaddam99" [email protected]
|
Oracle DB Version : Release 12.1.0.1.0 One more thing i want to mention here is my oracle db to which i am connected having hundreds of schemas and all of them getting connected once presto server started. Thanks' |
Could you share your oracle-plugin.properties (with the jdbc url, etc)? Another question is have your Oracle user grants to all schemas or just the one you are trying to access? I'm trying to understand what is different to help you or fix the plugin. Regards. |
Hi @surendraGaddam99, in your database there are also synonyms to the tables? I've seen mentions of a performance issue on get columns with synonyms (http://stackoverflow.com/a/2068713/5077154). |
I used this oracle plugin to create oracle connector for presto db. But i am facing performance issues. When i try to execute queries using presto cli 0.147 taking 40 to 45 seconds to display results . Any suggestions to decrease execution time ?
prestodb/presto#5790
Thanks
Surendra
The text was updated successfully, but these errors were encountered: