Features Deprecated in Denodo Platform¶
Due to the introduction of new features or changes in existing ones, and after careful consideration, we may mark a feature as deprecated.
This page lists the features that are currently deprecated in the Denodo Platform 9, including the Solution Manager.
Consider the following when using features that are deprecated:
Denodo will provide support to customers regarding these features for the full life of version 9.
Denodo will fix bugs detected by customers and address security vulnerabilities for the full life of version 9.
These features may not be available in the next major version of the Denodo Platform but will remain in all the updates of the current version.
We strongly recommend planning to stop using deprecated features.
When we decide to deprecate a feature, we announce it with the release of an update. In that case:
We mention it in the page What Is New in Denodo 9 Update… of the New Features Guide of the new update, in the section Information about Deprecated Features of the page.
We add the feature to this page.
Virtual DataPort¶
Administration Tool¶
Starting with Denodo 9.0, the administration tool is deprecated. Users must transition to Design Studio. The Administration Tool is still maintained (see above the definition of “deprecated”). However, the graphical support for some new features of Virtual DataPort may only be available in Design Studio.
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¶
SQLFRAGMENT Clause¶
Starting with Denodo 6.0, the SQLFRAGMENT
clause of the CREATE WRAPPER JDBC
statement has
been deprecated.
Syntax ALTER TABLE <Base View Name> ADD SEARCHMETHOD¶
Starting with Denodo 6.0, the syntax ALTER TABLE
<base view name> ADD SEARCHMETHOD
is
deprecated.
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 ALTER TABLE
.
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
VIEWPROPERTIES
of theCONTEXT
clause ofSELECT
statements 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 8.0, the parameter
cache_wait_for_load
of theCONTEXT
clause ofSELECT
statements is deprecated. The default behavior is to wait for cache load in views with cache FULL or PARTIAL with explicit loads.
Deprecated Functions¶
Starting with Denodo 7.0, the following functions are deprecated and may be removed in future versions of the Denodo Platform:
CREATETYPEFROMXML: instead of using this function, create an XML data source with a route of type from variable and pass the XML document to this data source.
Command QUERY WRAPPER¶
Starting with Denodo 8.0, the command QUERY WRAPPER, which allows you to query wrappers without creating a base view, is now deprecated.
Data Sources¶
Deprecated JDBC Adapters¶
The following JDBC adapters are deprecated:
Deprecated Database Adapter |
Notes |
---|---|
Apache Spark SQL 1.5 |
There is no longer commercial support for these versions of Apache Spark SQL. |
Apache Spark SQL 1.6 |
|
Apache Spark SQL 2.x |
|
Hive 0.13.0 |
There is no longer commercial support for these versions of Hive. |
Hive 1.1.0 |
|
Hive 1.1.0 for Cloudera |
|
Hive 1.2.1 for Hortonworks |
|
Hive 2.0.0 |
|
Microsoft SQL Server 2000 |
These versions of Microsoft SQL Server reached the end of Extended support several years ago. This applies to the adapters that use the Microsoft driver (MS Driver) and the adapters that use the jTDS adapter. |
Microsoft SQL Server 2005 |
|
Microsoft SQL Server 2008 |
|
Microsoft SQL Server 2008R2 |
|
jTDS adapter for Microsoft SQL Server 2014 |
These adapters are deprecated because the jTDS JDBC driver does not officially support these versions of SQL Server. Instead, use the Microsoft adapter (marked with (MS Driver) in the drop-down Database adapter). |
jTDS adapter for Microsoft SQL Server 2016 |
ODBC Data Sources¶
Starting with Denodo 8.0, creating ODBC data sources in Virtual DataPort is deprecated and by default, disabled. This feature relies on the JDBC-ODBC bridge of Java. Starting with Java 8, Oracle no longer supports the JDBC-ODBC bridge included in the Java Virtual Machine.
If a database provides a JDBC driver, create a JDBC data source instead of an ODBC one. Queries involving a JDBC data source run faster than if they involve an ODBC data source, even if the underlying database is the same.
To enable this, read the section Enabling the Support for ODBC Sources of the Virtual DataPort Administration Guide.
Decrypt Filter¶
Starting with Denodo 7.0, the filter Decrypt (PBE with MD5 and DES) is deprecated. This is the filter you can set in the data sources DF, JSON and XML.
If you can choose how the input file will be encrypted, we recommend using PBE with HMAC-SHA256-512 and AES-256 because it is securer. This is why the filter PBE with MD5 and DES is deprecated.
The file <DENODO_HOME>/tools/db/denodo-crypt-tools/denodo-crypt-tools.zip
includes tools to encrypt and decrypt files. These tools support both encryption algorithms.
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.
COMPACT_HADOOP_CACHE. Use COMPACT_CACHE 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 9 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.
Version Control Systems (VCS)¶
Starting with Denodo 8.0, the Version Control System integration with Subversion and Microsoft Team Foundation Server (TFS) is deprecated. 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:
--property includeEnvSpecificElements
--property includeNonEnvSpecificElements
--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.0, the action
Switch query to plan
of Resource Manager plans is deprecated.
Data Catalog¶
Roles “selfserviceadmin”, “selfserviceexporter”¶
In the next major version of Denodo, the roles “selfserviceadmin” and “selfserviceexporter” will be removed. These roles exist in Denodo 9 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.
Scheduler¶
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.
Solution Manager¶
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).Documentation of session-based authentication (Denodo 7.0).