We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In version 2.1.1 a NullPointerException happens for the setProperties request of the ALTER VIRTUAL SCHEMA statement:
NullPointerException
setProperties
ALTER VIRTUAL SCHEMA
java.lang.NullPointerException Stack trace: com.exasol.adapter.jdbc.JdbcAdapter.getTableFilter(JdbcAdapter.java:157) com.exasol.adapter.jdbc.JdbcAdapter.setProperties(JdbcAdapter.java:127) com.exasol.adapter.RequestDispatcher.dispatchSetPropertiesRequestToAdapter(RequestDispatcher.java:134) com.exasol.adapter.RequestDispatcher.processRequest(RequestDispatcher.java:75) ...
How to reproduce:
CREATE VIRTUAL SCHEMA VS1 USING ADAPTER.JDBC_ADAPTER WITH CONNECTION_STRING='jdbc:exa:REMOVED' SCHEMA_NAME='NATIVE' IS_LOCAL='True' SQL_DIALECT='EXASOL'; DROP TABLE NATIVE.T_DATETIME; ALTER TABLE NATIVE.T ADD COLUMN D INT; CREATE TABLE NATIVE.T_NEW(A INT); RENAME SCHEMA NATIVE TO NATIVE_RENAMED; ALTER VIRTUAL SCHEMA VS1 SET SCHEMA_NAME='NATIVE_RENAMED' CONNECTION_STRING='jdbc:exa:REMOVED;schema=NATIVE_RENAMED';
The text was updated successfully, but these errors were encountered:
Tested with different versions. The behavior was broken in version 1.16.3: https://github.com/exasol/virtual-schemas/releases/tag/1.16.3
I'm going to investigate the case.
Sorry, something went wrong.
#272: fixed NullPointerException for setProperties request
7a48e94
#272: fixed NullPointerException for setProperties request (#278)
f46e3c9
AnastasiiaSergienko
No branches or pull requests
In version 2.1.1 a
NullPointerException
happens for thesetProperties
request of theALTER VIRTUAL SCHEMA
statement:How to reproduce:
The text was updated successfully, but these errors were encountered: