Scheduler Naming Conventions
Applies to:
Denodo 8.0
,
Denodo 7.0
,
Denodo 6.0
Last modified on: 22 May 2020
Tags:
Best practices
Goal
This document enumerates the proposed naming conventions for all the elements that can be created as part of a Scheduler Server.
Projects
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
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:
{job_identifier}:
- 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" />
Questions
Ask a question
You must sign in to ask a question.
If you do not have an account, you can register here
Featured content
DENODO TRAINING
Ready for more? Great! We offer a comprehensive set of training courses, taught by our technical instructors in small, private groups for getting a full, in-depth guided training in the usage of the Denodo Platform. Check out our training courses.
