Features Deprecated for Denodo Platform 8.0¶
Due to the introduction of new features or changes in existing ones, some features of Denodo that are available in previous versions have been deprecated.
This page lists the features that are currently deprecated in the Denodo Platform 8.0, including the Solution Manager.
With the release of an update, more features may be deprecated. In that case, the newly deprecated features will be added to this page.
Consider the following when using features that are deprecated:
Denodo will provide support to customers regarding these features for the full life of version 8.0.
Denodo will fix bugs detected by customers and address security vulnerabilities for the full life of version 8.0.
These features may be removed in the next major version of the Denodo Platform but not in an update of the current version.
We recommend planning to stop using deprecated features.
Data Type “Date”¶
Starting with Denodo 7.0, the data type “date” is deprecated, although is maintained for compatibility reasons. The fields with this data type will behave in the same way as in prior versions 6.0. Instead use the new types: localdate, time, timestamp or timestamptz.
Starting with Denodo 6.0, the
SQLFRAGMENT clause of the
CREATE WRAPPER JDBC statement has
Syntax ALTER TABLE <Base View Name> ADD SEARCHMETHOD¶
Starting with Denodo 6.0, the syntax
ALTER TABLE <base view name>
ADD SEARCHMETHOD is
When creating a base view, define the search methods in the
CREATE TABLE statement instead of executing a
CREATE TABLE and
then, adding the search methods with the statement
This reduces the number of statements Virtual DataPort has to process.
For example, instead of running this:
CREATE TABLE internet_inc I18N us_est ( iinc_id:long, summary:text, ... ... ); ALTER TABLE internet_inc CACHE OFF TIMETOLIVEINCACHE DEFAULT ADD SEARCHMETHOD internet_inc( I18N us_est CONSTRAINTS ( ADD iinc_id (any) OPT ANY ADD summary (any) OPT ANY ... ... ) OUTPUTLIST (iinc_id, specific_field1, specific_field2, summary, taxid, ttime ) WRAPPER (jdbc internet_inc) );
Run the following (i.e. just one command)
CREATE TABLE internet_inc I18N us_est ( iinc_id:long, summary:text, ... ... ) CACHE OFF TIMETOLIVEINCACHE DEFAULT ADD SEARCHMETHOD internet_inc( I18N us_est CONSTRAINTS ( ADD iinc_id (any) OPT ANY ADD summary (any) OPT ANY ... ... ) OUTPUTLIST (iinc_id, specific_field1, specific_field2, summary, taxid, ttime ) WRAPPER (jdbc internet_inc) );
Parameters of the CONTEXT Clause of SELECT Statements¶
Starting with Denodo 5.5, the parameter
SELECTstatements is deprecated.
The only reason to use it is to specify at runtime the value of the parameter “begin delimiter” of a DF data source. Instead, enable the option Start delimiter from variable of the data source.
Starting with Denodo 7.0, the following functions are deprecated and may be removed in future versions of the Denodo Platform:
Deprecated JDBC Adapters¶
The following JDBC adapters are now deprecated:
jTDS adapter for Microsoft SQL Server 2014
jTDS adapter for Microsoft SQL Server 2016
The jTDS JDBC driver does not officially support these versions of SQL Server; we strongly encourage users to use the Microsoft JDBC driver instead, which does provide support for these versions.
Denodo Stored Procedures¶
The following stored procedures included out-of-the box in Virtual DataPort are deprecated:
These procedures have been replaced with new ones because the old ones only return information about the database you are currently connected to. The new ones (“GET_…”) can obtain the same information from any database.
jmxadmin is now deprecated. From now on, you should use the role
monitor_admin. The privileges granted to both roles are the same but the name “monitor_admin” is more appropriate to its capabilities.
If you granted the role “jmxadmin” to other users or roles, you should grant them “monitor_admin” instead.
If you upgraded from Denodo 6.0 or 7.0 following the instructions of this guide, the metadata you exported from 6.0 or 7.0 already uses the role “monitor_admin” instead of “jmxadmin”.
Denodo Stored Procedures API: getNumOfAffectedRows Method¶
Starting with Denodo 6.0, the method
getNumOfAffectedRows() of the stored procedures API has
been deprecated and it may be removed in future major versions of the Denodo Platform. Do not override this method in new stored procedures to avoid that they are incompatible with future major versions.
In Denodo 8.0, the execution engine does not invoke this method; it is only maintained so old stored procedures can be loaded in this version.
Denodo Custom Wrappers API: Deprecated Methods¶
The following methods of the API for custom wrappers have been deprecated. We suggest you remove all the references to these methods and constants from the code of your custom wrappers.
Starting with Denodo 6.0:
In Denodo 8.0, the execution engine does not invoke the first two methods; they are only kept to maintain binary compatibility with old custom wrappers.
Starting with Denodo 7.0:
The constructor CustomWrapperFieldExpression.CustomWrapperFieldExpression(String, List<CustomWrapperFieldExpression>)
You should use method
CustomWrapperResult.addRow(Object)instead because it performs better.
The methods and constants related to the comparison operator
contains. In Denodo 8.0, the execution engine does not invoke these; they are only maintained so old custom wrappers can be loaded in this version. These are:
See more information about this in the section Contains, Containsand, Containsor and Iscontained Operators.
Denodo JDBC Driver¶
Starting with Denodo 7.0, the parameter
wanOptimizedCalls of the JDBC driver has been deprecated.
This parameter is deprecated because in Denodo 7.0 its default value is true and there is no reason to set it to false. In previous versions, the default value of this parameter is false. If true the driver reduces the number of remote calls it sends to the Server. In addition, when the application closes a result set, the driver only sends a cancel request to the Server if there are still pending results. If false, the driver always sends the cancel request.
Denodo Web Services¶
The Denodo Web Services created with Virtual DataPort 4.7 or earlier versions are deprecated. These web services provide SOAP and REST capabilities. They still work, its VQL statements can be loaded into Virtual DataPort 8.0 and can be edited from the administration tool. However, no new web services of this type can be created.
Starting with Denodo 5.0, SOAP web services and REST web services are different elements. The reason is that SOAP web services are operation-oriented and REST web services are resource-oriented.
Starting with Denodo 7.0, the feature of publishing widgets is deprecated. This includes Web Parts for Microsoft SharePoint, Portlets v1.0 (JSR-168) and Portlets 2.0 (JSR-268).
The Administration Tool no longer supports creating them. However, if you have imported them from a previous version, the Administration Tool will open them; they can also be created and managed using VQL statements.
Script Export: Deprecated Parameters¶
Starting with Denodo 5.5, the scripts “export” and “import” of the directory
<DENODO_HOME/bin have several parameters that are deprecated:
Instead, use the parameter
Launching Several Virtual DataPort Instances of the Same Installation¶
Starting with Denodo 7.0, the feature Launching Several Virtual DataPort Instances of the Same Installation is deprecated.
If you are using this feature, configure Virtual DataPort to store the metadata in an external database instead (see Storing the Metadata on an External Database). This allows you to create a cluster of Virtual DataPort servers, in which all the servers share the same external database.
Note that this feature that has been deprecated is not about starting two Virtual DataPort servers from two different installations of the Denodo Platform running on the same computer. Running two Virtual DataPort servers of different installations on the same computer is possible and fully supported if they listen to connections on different ports.
Roles “selfserviceadmin”, “selfserviceexporter”¶
In the next major version of Denodo, the roles “selfserviceadmin” and “selfserviceexporter” will be removed. These roles exist in Denodo 8.0 to keep backward compatibility with Denodo 6.0 but you should not grant them to users anymore. Instead, grant the new roles “data_catalog_admin” and “data_catalog_exporter”, which are equivalent to “selfserviceadmin” and “selfserviceexporter” respectively.
With the release of the previous version of Denodo (v7.0), the “Information Self-Service Tool” was rebranded to “Data Catalog” and so were these two roles.
The module ITPilot is now deprecated. This includes:
The module ITPilot itself.
The data sources of type ITPilot in Virtual DataPort.
In addition, the Scheduler jobs of type ITPilot have been removed.
Consider the following when using an ITPilot component:
Denodo provides assistance to customers regarding any ITPilot component for the full life of version 8.0.
Denodo will fix bugs detected by customers and address security vulnerabilities.
Denodo will not add any major enhancements to ITPilot. However, minor enhancements may be added to the roadmap of version 8.0.
Some or all components of ITPilot may be removed in the next major version of the Denodo Platform but not in an update of version 8.0.
Currently, there are no features of Scheduler that are deprecated.
REST API: Authentication Using Session¶
In the REST API of the Solution Manager, the authentication method based on session (i.e. obtaining a JSESSIONID cookie) is deprecated. We recommend you use stateless authentication instead. That is, each request from the client has to include the credentials. This approach is much simpler and more widely supported than session-based authentication.
Documentation of session-based authentication (Denodo 7.0).
The Denodo4Eclipse plugin is deprecated. Instead, developers should follow the instructions of the article How to debug Denodo custom extensions with Eclipse of the Denodo Knowledge Base.
The main goal of this plugin is to debug the extensions you develop for Denodo. This article explains how to do it without having to use Eclipse nor having to install the plugin. This article is focused on Eclipse but you can also debug your extensions for Denodo using IntelliJ IDEA.