-
Notifications
You must be signed in to change notification settings - Fork 17
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
Not able use with SQL Client like SQLWorkbench - No support for catalog / schema / set Max Rows #2
Comments
Hi and thank you for trying it out. The primary target for us has been non-interactive use, but there's no reason it couldn't work for interactive use eventually. JDBC is huge, and contains a lot of details that are not important for an application, and covering every single one of these has not been a priority. SQLWorkbench will use a couple of features, other tools other features and unless you cover them all there's always something that will break unfortunately. In this case you seem to have run into that Could you clarify what you mean by the list of features? I don't understand what for example "Doesn't support Catalog / Schema" means. |
I belive what ssenthi is referring to is full support for the various metadata APIs in Connection and ResultSet (and more?) |
I think this is an area where we will have to rely on contributions. We will probably not close the holes that appear when using the driver with different tools, and we need help to get them fixed. Some of these will be very easy to fix, but some will be much more complicated. To take one example, |
I looked through the open issues and figured that perhaps we could close #2 with this comment (it's close to a wontfix, but at least it's something).
For what it is worth, I set up an interactive session in DBeaver, and I was able to query just fine using this driver. I deselected all "optional" features in the driver-manager configuration, and if I open e.g. the tables view, it complains about it not being supported, but opening a SQL editor and running statements work just fine.
While I don't know for sure, I would venture a guess that the reason the methods return a However, contrary to your claim, I think the |
Hi,
I was excited to see a new JDBC Driver for Athena and thought of using it for our interactive use.
the key issues are
2019-09-02 14:12:41 INFO Loaded global SSH host configurations from C:\Users\STHSH4.sqlworkbench\wbssh.settings
2019-09-02 14:13:33 INFO Global SSH host configuration file C:\Users\STHSH4.sqlworkbench\wbssh.settings removed.
2019-09-02 14:13:36 WARN The JDBC driver does not support the setMaxRows() function! (Not implemented)
2019-09-02 14:13:37 WARN Error retrieving warnings Not implemented
java.lang.UnsupportedOperationException: Not implemented
at io.burt.athena.AthenaStatement.getWarnings(AthenaStatement.java:281)
at workbench.util.SqlUtil.getWarnings(SqlUtil.java:1651)
at workbench.sql.SqlCommand.appendWarnings(SqlCommand.java:400)
at workbench.sql.commands.SelectCommand.execute(SelectCommand.java:172)
at workbench.sql.StatementRunner.runStatement(StatementRunner.java:552)
at workbench.gui.sql.SqlPanel.displayResult(SqlPanel.java:3468)
at workbench.gui.sql.SqlPanel.runStatement(SqlPanel.java:2199)
at workbench.gui.sql.SqlPanel$16.run(SqlPanel.java:2137)
SELECT count(*) from cmdm_sf_rec_results.account
java.util.concurrent.ExecutionException: software.amazon.awssdk.core.exception.SdkClientException
2019-09-02 14:12:41 INFO Loaded global SSH host configurations from C:\Users\STHSH4.sqlworkbench\wbssh.settings
2019-09-02 14:13:33 INFO Global SSH host configuration file C:\Users\STHSH4.sqlworkbench\wbssh.settings removed.
2019-09-02 14:13:36 WARN The JDBC driver does not support the setMaxRows() function! (Not implemented)
2019-09-02 14:13:37 WARN Error retrieving warnings Not implemented
java.lang.UnsupportedOperationException: Not implemented
at io.burt.athena.AthenaStatement.getWarnings(AthenaStatement.java:281)
at workbench.util.SqlUtil.getWarnings(SqlUtil.java:1651)
at workbench.sql.SqlCommand.appendWarnings(SqlCommand.java:400)
at workbench.sql.commands.SelectCommand.execute(SelectCommand.java:172)
at workbench.sql.StatementRunner.runStatement(StatementRunner.java:552)
at workbench.gui.sql.SqlPanel.displayResult(SqlPanel.java:3468)
at workbench.gui.sql.SqlPanel.runStatement(SqlPanel.java:2199)
at workbench.gui.sql.SqlPanel$16.run(SqlPanel.java:2137)
2019-09-02 14:13:37 ERROR Error executing:
SELECT count(*) from
java.util.concurrent.ExecutionException: software.amazon.awssdk.core.exception.SdkClientException
2019-09-02 14:13:59 WARN The JDBC driver does not support the setMaxRows() function! (Not implemented)
2019-09-02 14:13:59 WARN Error retrieving warnings Not implemented
java.lang.UnsupportedOperationException: Not implemented
at io.burt.athena.AthenaStatement.getWarnings(AthenaStatement.java:281)
at workbench.util.SqlUtil.getWarnings(SqlUtil.java:1651)
at workbench.sql.SqlCommand.appendWarnings(SqlCommand.java:400)
at workbench.sql.commands.SelectCommand.execute(SelectCommand.java:172)
at workbench.sql.StatementRunner.runStatement(StatementRunner.java:552)
at workbench.gui.sql.SqlPanel.displayResult(SqlPanel.java:3468)
at workbench.gui.sql.SqlPanel.runStatement(SqlPanel.java:2199)
at workbench.gui.sql.SqlPanel$16.run(SqlPanel.java:2137)
If the intention is purely for using in java code ( not interactive use) , i understand. I assumed any JDBC (standard) drivers could be used with Interactive tool like SQLWorkbench. Today we use SQLWorkbench for Athena for Adhoc / interactive/ discovery type which is well suited for athena
The text was updated successfully, but these errors were encountered: