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.

VQL Syntax¶

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)
    );

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)
    );

Data Sources¶

Denodo Stored Procedures¶

The following stored procedures included out-of-the box in Virtual DataPort are deprecated:

• CATALOG_ELEMENTS. Use GET_ELEMENTS instead.

• CATALOG_VIEWS. Use GET_VIEWS instead.

• CATALOG_PKS. Use GET_PRIMARY_KEYS instead.

• CATALOG_FKS. Use GET_FOREIGN_KEYS instead.

• SOURCE_CHANGES. Use GET_SOURCE_CHANGES instead.

• GENERATE_STATS. Use GET_STATS_FOR_FIELDS instead.

• GENERATE_STATS_FOR_FIELDS. Use GET_STATS_FOR_FIELDS instead.

• GENERATE_SMART_STATS_FOR_FIELDS. Use GET_STATS_FOR_FIELDS instead.

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.

• WEBCONTAINER_ELEMENTS. Use WEBCONTAINER_ELEMENT_STATUS instead because it provides more information.

• LIST_JDBC_DATASOURCE_TABLES. Use GET_JDBC_DATASOURCE_TABLES instead.

Role JMXAdmin¶

The role 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:

• com.denodo.vdb.engine.customwrapper.CustomWrapperConfiguration.isDelegateCompoundFieldProjections()

• com.denodo.vdb.engine.customwrapper.CustomWrapperConfiguration.setDelegateCompoundFieldProjections(boolean)

• com.denodo.vdb.engine.customwrapper.expression.CustomWrapperFieldExpression.getSubFields()

• com.denodo.vdb.engine.customwrapper.expression.CustomWrapperFieldExpression.hasSubFields()

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>)

• com.denodo.vdb.engine.customwrapper.CustomWrapperResult.addRow(Object[], 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:

  • com.denodo.vdb.engine.customwrapper.expression.CustomWrapperContainsExpression

  • com.denodo.vdb.engine.customwrapper.condition.CustomWrapperCondition.OPERATOR_CONTAINS

  • com.denodo.vdb.engine.customwrapper.expression.CustomWrapperExpression.isContainsExpression()

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¶

• Starting with Denodo 8.0, this is deprecated: creating a SOAP web service that publishes a Java stored procedure or a VQL stored procedure. You can do it with a VQL command or with the Administration Tool (not with Design Studio) but you should not do it. Instead, create a selection view over the procedure and publish this view in the web service. Note: it has never been possible to create REST web services that publish a stored procedure.

• 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.

Widgets¶

Starting with Denodo 7.0, the feature of publishing widgets is deprecated and will not be available in Denodo 9. 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.

Version Control Systems (VCS)¶

Starting with Denodo 8.0, the Version Control System integration with Subversion and Microsoft Team Foundation Server (TFS) is deprecated and it will not be available in Denodo 9. The support for Git, including the support for Git repositories managed by Microsoft Team Foundation Server, is still fully supported.

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:

1. --property includeEnvSpecificElements

2. --property includeNonEnvSpecificElements

3. --dependencies (only available on the “import” script).

Instead of #1 and #2, use --property includeProperties.

The parameter --property cluster of the script “export” is now deprecated.

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.

Resource Manager¶

Starting with Denodo 8.0u20240926, the action Switch query to plan of the Resource Manager plans is deprecated.

Roles “selfserviceadmin”, “selfserviceexporter”¶

In the next major version (Denodo 9), the roles “selfserviceadmin” and “selfserviceexporter” will not exist. 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.

Elasticsearch 5.x and 6.x¶

Support for Elasticsearch versions 5.x and 6.x is deprecated and will not be available in Denodo 9. We recommend transitioning to Elasticsearch 7.x for compatibility and continued support.

Private Scheduler REST API¶

The private Scheduler REST API, which requires login before any request and logout after all them, is deprecated and it should not be used. Instead, use the new public Scheduler REST API.

Elasticsearch 5.x and 6.x¶

Support for Elasticsearch versions 5.x and 6.x is deprecated and will not be available in Denodo 9. We recommend transitioning to Elasticsearch 7.x for compatibility and continued support.

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).