You can translate the document:


This document enumerates the proposed naming conventions for all the elements that can be created as part of a Scheduler Server.


Project names must follow the existing naming conventions in the organization.

Data sources

Scheduler data sources are named as follows:

ds_{database name (VDP, JDBC) / name of the file (CSV) / data source name}_{description (Optional)}

  • Examples:
  • ds_denodo_training
  • ds_service_outage
  • ds_webmail


Jobs are elements that can be exposed to final users. They must follow user friendly names according to the naming conventions in the organization.

Scheduler jobs are named as follows:


  • Examples:
  • customerDetails
  • load_incident_by_user

Filter sequences

Filter sequences are named as follows:

fs_{filter sequence identifier}:

  • Examples:
  • fs_content_advanced

Custom Exporters, filters, handlers

Java Objects must use the suffix for the element to create:

  • For custom exporters: xxxxExporter.
  • For custom handlers: xxxxHandler.
  • For custom filters: xxxxFilter.

The name to be displayed in Scheduler must not have the type of the element.

For example, for the GenericXMLExporter, it will be displayed in the Exporters section of Scheduler as “XML”. This is an example of the XML code of the custom element:

<element type="exporter" subType="Xml" class="com.denodo.devkit.exporters.GenericXmlExporter" />

The information provided in the Denodo Knowledge Base is intended to assist our users in advanced uses of Denodo. Please note that the results from the application of processes and configurations detailed in these documents may vary depending on your specific environment. Use them at your own discretion.
For an official guide of supported features, please refer to the User Manuals. For questions on critical systems or complex environments we recommend you to contact your Denodo Customer Success Manager.


Ask a question

You must sign in to ask a question. If you do not have an account, you can register here