Contributions
Re: getFetchSize is not supported
Thanks for your response Richie. [Richie]: This is total guess as I've never used CosmosDB before - but you're getting an issue with the getfetchsize() method immediately once the query executes. [Tyson]: Yes, this is with Microsoft Azure CosmosDB and yes once the query executes, I see this on the Request log "2019-12-17 20:34:08.906 - Error getting response; null" and when i view the Error log, that is where it has the getfetchsize() is not support message is recorded. [Richie]: I have noticed differing behaviour between the QueryBuilder and executing via the SQL query editable field before now - so cant really comment on that - but have you tried executing your query from outside of ReadyAPI! at all? [Tyson]: Yes using the same driver/jar, i was able to connect with DBVisualizer and all the queries that i wanted to execute does get executed successfully with correct results including the simple Select statement. [Richie]: HOWEVER - this is cloud based DB - right? Are you sure there isn't any resource slicing going on? i.e. your SaaS contract might have restrictions on pulling a full tables worth of data (especially if the query you're executing doesn't run any indexes) [Tyson]: Yes this is CloudDB. As an example, I had also tried with an explicit "where condition" in the select statement which should return only 1 result row . This query when tried via ReadyAPI QueryBuilder i.e BuildQuery and also in DBVisualizer works correctly and returns only 1 result row, but if i try the same using the "SQL Query" I get the same getfetchsize() error immediately after the query executes. I have also tried with indexed columns but with the same results.Any other thoughts/ideas? Ideally what i want to accomplish though is once the Test step is executed (SQLQuery or Build Query option whichever one is successful, though currently BuildQuery seems to return the results but not SQLQuery) i want to parse the JSON response of the query and get the needed values. Is there a way to accomplish this from BuildQuery option results so that i can explore that if no solution for SQLQuery option error (My advance apologies if this has to be a separate question, if so please advise and i will follow-through).5 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.8KViews0likes7CommentsgetFetchSize is not supported
I currently have ReadyAPI 3.0.0 and when i run a Test Step that has a Select statement i get an error getFetchSize() is not supported. 1) Firstly i connect successfully to Azure CosmosDB (I have the correct cdataJDBCdrivers, etc) 2) Then in the Test Step=>ConfigureTab=>SQL Query section,I try to run a simple Select statement "Select c.* from <CosmosDBTableName> c " i get theerror getFetchSize() is not supported. Interestingly in the Test Step=>ConfigureTab=>BuildQuery, it shows me the same query and i am able to execute the query and also get the correct results. Any input on how to overcome the issue with getFetchSize() is not supported. Please refer to the Errorlog below Tue Dec 17 15:45:51 PST 2019: ERROR: XcoreXcosmosdbX190X7216.pce: getFetchSize() is not supported. XcoreXcosmosdbX190X7216.pce: getFetchSize() is not supported. at XcoreXcosmosdbX190X7216.vce.getFetchSize(Unknown Source) at com.eviware.soapui.support.xml.XmlUtils.createResultSetElement(XmlUtils.java:1454) at com.eviware.soapui.support.jdbc.JdbcUtils.parseResultSet(JdbcUtils.java:196) at com.eviware.soapui.support.jdbc.JdbcUtils.createResultSetHolder(JdbcUtils.java:171) at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcResponse.<init>(JdbcResponse.java:47) at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.createResponse(JdbcSubmit.java:275) at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.runQuery(JdbcSubmit.java:178) at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.run(JdbcSubmit.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Solved5 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.9KViews0likes9Comments