Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

D toc

visual profile can be optionally generated as part of execution of a job. While profiling can extend the time it takes to complete the job, a visual profile can provide key statistical information on the columns of your data and the overall dataset itself. This section provide information on each of the available profilers and how to configure them.


NOTE: To enable use of a profiler, the running environment on which it is hosted must also be enabled. See Running Environment Options.


D s platform
 supports the following options for profiling your data.


Type of ProfilerRequires Hadoop cluster?Supported Running EnvironmentDescription

Scala Spark Profiler


Generates a profile on the

D s server
using the Spark Job Service. Does not require any Spark installation on the cluster.


Tip: This is the best-performing profiler in most use cases.

Photon ProfilerNoPhotonDefault profiler when Photon running environment is enabled, and the Scala Spark Profiler has not been enabled.


Making changes to your profiling type:

  1. Apply the configuration changes listed below.
  2. Save your changes and restart the platform.
  3. Restart your browser and login again.

Run Profiling as a Second Job in Spark

By default, profiling jobs execute on the running environment where the transformation job was executed. You can configure the 

D s server
 (Photon) running environment to execute profiling jobs as a separate job in the Spark running environment. This separation allows users to begin working with the transformed data while waiting for the profiling job to complete. 


  1. D s config
  2. Locate the following property and set its value to true:

    Code Block
    "photon.runProfileWithSpark": false,

  3. Save your changes and restart the platform.

When profiling is selected for jobs executing on the 

D s server
, their jobs are executed on the Spark running environment as a separate job.

Disable Profiling Option

Profiling is invoked at job execution time by the user.  See See Run Job Page.

To disable user choice through the UI, set the following parameter:

Code Block
"profiler.userOption": false,

When the above setting is disabled: 

  • Any available checkbox no longer works. User cannot choose whether to profile or not.
  • Profiles are always executed.

NOTE: This setting does not affect profiling through the APIs. Profiling can always be enabled or disabled for jobs that are executed via API.

To disable user choice through the UI, set the following parameter:

Code Block
"profiler.userOption": false,

NOTE: Profiling can still be enabled for jobs that are executed via the CLI or API.