2.2. Resolved Issues

The Admin shell throws an IncompatibleClassChangeError when wrong path to a Groovy script is provided along with load command. This happens because the Admin shell cannot handle nonexistent files. To rectify this issue Groovy has been updated to version 23.6 and jline hjas been updated to version 2.9. As a result, users will no longer encounter this bug.

Solr queries would fail when time, date or timestamp literal were used in where clauses. A software upgraded has rectified this error.

If the usr tried to connect to a Teiid instance secured with Kerberos without valid credentials in the URL, the connection would fail. More support for Kerberos usage has been added in 6.2, so users will no longer experience this problem.

DV-specific artifacts (DashboardDS, teiid-log-ds, security-domains created in installer, modeshape subsystem) were also inserted into the 'default' configuration profile in domain.xml. This was fixed by chanes to the default profile and teiid-extensions.

Users would encounter null-pointer exceptions if they tried to export data from Command Logging as CSV. The Dashboard Builder has been upgraded. As a result, users will no longer encounter this exception.

The README.md files for the Server and Security-oriented quick starts have been improved. They are now more accurate and have been updated to indicate supported dependencies.

If you tried to set up a quick start using the JBOSS EAP Maven plugin, it would not work as the resource adapter was not added. The quick start has been modified as the JBoss Maven plugin is no longer supported.

The capabilities of the Infinispan DSL Cache translator have been improved. It now supports "Not In" and "Not Like".

When a dynamic VDB is deployed, querying http://localhost:8080/sample_1/view/proc1/1 caused a NullPointerException. A fix has been applied so that users will no longer encounter these exceptions.

The Teiid extensions build packaged the database-service jar without its version (database-service.jar). The CLI scripts have been updated so it is now versioned correctly.

The web console is now compatible with the latest version of Red Hat JBoss EAP.

The BufferFrontedFileStoreCache.maxMemoryBlocks was under-estimated. This has now been increased.

The Oracle translator did not support the translation of all patterns from SimpleDateFormat. It has now been updated to support the translation of all patterns.

If the table name was ambiguous, Red Hat JBoss Data Virtualization would return data from the first matching table. This has now been changed so that it throws an exception instead.

If you disabled security on the odata.war by modifying the web.xml file, Odata would thrown an exception. This was because it was trying to use pass-through security. The configuration has now been changed so that you can use the Odata servlet without authentication.

If you used the incorrect login when trying to access the Dashboard, the software would enter an infinite redirect loop. This only occurred if LDAP was used to authenticate, rather than JAAS. This has been rectified so that the user is now logged out of the non-authorized session.

An out-of-memory error occurred if the buffer was set to more than 513 megabytes, neaning that Red Hat JBoss Data Virtualization would not launch. A fix has been applied so that the maximum buffer size can now be set to a figure in excess of 513 megabytes.

Users would encounter errors if selecting RAW(16) columns using Odata.

Strings featuring the WITH clause that were being sent to Oracle were not being translated correctly. This has now been rectified so the WITH clause can now be used.

OData object URIs did not resolve to a usable URL. When accessing a virtual database via Odata with a browser using either via JSON or XML the URI listed in the metadata was not valid. This has now been corrected so that, when Odata is used, the URIs will resolve to the correct URLs.

The installation would fail if the the password was set to 'teiid123$'. The 'use one password for all default passwords' checkbox was enabled. This no longer occurs with later versions of the installer.

There was an extra slash character in one of the default vault-option elements. The installer has now been updated and as a result, this extra slash has been removed.

The org.jboss.security.negotiation module was missing "ibm.jdk" dependency which was needed if Red Hat JBoss Data Virtualization was running on the IBM JDK. The installer has now been changed so that ibm.jdk is a dependency.

Modeshape's backup and restore services has been exposed via REST. Users no longer need to write third-party code using the API. As a result, backups and restores can be performed more easily.

The TargetPanel method loadDefaultDirFromVariables now checks for the INSTALL_PATH system property and -DINSTALL_PATH can now be used to specify a new install path for the automated installation.

Users trying to install using the command-line interface installer on Windows would see messages such as "WARN: can't find jboss-cli.xml. Using default configuration values." To rectify this issue, a new panel action class has been added which sets the correct path to the jboss-cli.xml file. As a result, Windows users will no longer see these warning messages.

The XML and Web Service models were created in the 'web_services' subdirectory, but the XSD model was created in 'web_services/schemas'. It is now created in the correct subdirectory.

When opening a Web Service model editor by double-clicking the model in the model explorer, the input variables section was empty, even when there were variable declarations in the procedure SQL. Trying to add the variables using the Add or Remove variables button resulted in multiple identical declarations in the procedure SQL. This has now been corrected, so the web service input variables are present when the model is opened.

When using the Type Resolver, after clicking "Convert all source SQL symbol datatypes", the changed expression did not appear in the Source SQL Symbol column. This has been resolved so that the column is updated correctly.

When importing flat files, the Teiid Designer plug-in allowed users to put the source and view models in different model project directories, which would not work. The plug-in has now been modified so that it checks for the same directory name, restricting users from using two different ones.

If the user attempted to rename a source model in the Teiid Designer plug-in and the source and view models were in separate directories, the models would break. This was due to a problem with the EMF model load and unload and has now been resolved. As a result, source models can now be renamed without error.

If the user tried to import a flat file via a remote URL, it would freeze on the 'Flat File Delimited Columns Parser Settings' screen. This has now been rectified so that the screen no longer freezes and users can import flat files from remote addresses without issue.

When users added a parameter to Rest connection profile, they could not change type from Query to URI. This has been resolved so the parameter type can now be changed.

The Welcome page would load but did not show any content if the server was run in Domain mode. There is now a new welcome page without console links that loads correctly.

Some dependencies were missing from the Maven settings_offline.xml file meant that JBoss Data Grid quick starts would not build. The version of the file has now been changed to the Red Hat JBoss EAP version, which contains the needed dependencies.

The archetype artifact was missing from the Maven repository. Two missing GAVs have now been added.