Jasper Studio is not parsing my query when using a custom jdbc driver


I am getting the following errors when trying to query Jasper Studio using my custom JDBC driver created by calcite.

Select portfolioCode from Portfolios
Select `portfolioCode` from `Portfolios`
Select `Portfolios`.`portfolioCode` from `Portfolios`

All the above queries do not work. It failed when trying to create a dataset. The metadata is loading correctly, but when I try to generate my query, it failed at "Query execution error"
When I just proceed with the error, there are no columns for me to select to add into the "Table" element.
Attached Screenshot.

1) Is there a log in Jasper Studio where we can see what this error is about? Looking at metadata/.log, there is no error message
2) What could be the problem?

Jaspersoft Studio 6.20.1

zhikai.ng's picture
Joined: Sep 14 2022 - 7:53pm
Last seen: 5 months 2 weeks ago

Thank you for posting to the Jaspersoft Community. Our team of experts has read your question and we are working to get you an answer as quickly as we can. If you have a Jaspersoft Professional Subscription plan, please visit https://support.tibco.com/s/ for direct access to our technical support teams offering guaranteed response times.

arai_4 - 5 months 3 weeks ago

Thank you for your patience, we have not forgotten you. We need a little more time with our team of experts to come up with a solution. We will respond back with an answer as quickly as we can.

arai_4 - 5 months 3 weeks ago

2 Answers:

Please let me know which Database you are using and what is the JDBC driver you are using provided by calcite? 

Did you tried with vendor specific drivers? 

Please refer the below support platform sheet to check supported databases:


To check the error logs:
1. select Help-> Installation Details-> Configuration-> View Error logs.

Please find the attached screenshot.

Image icon screenshot_319.png146.05 KB
akkhedka's picture
Joined: Jun 24 2020 - 11:06pm
Last seen: 1 week 4 days ago

Hi, Thanks for the reply. I realized after more debugging, it is due to the driver issue.

Thanks, I found the log

zhikai.ng's picture
Joined: Sep 14 2022 - 7:53pm
Last seen: 5 months 2 weeks ago