The Connect Job is Failing with Schema [[dfs, root]] is not valid

Reported Issue

Connect2 is failing with: java.lang.Exception: VALIDATION ERROR: Schema [[dfs, root]] is not valid with respect to either root schema or current default schema. Current default schema: dfs

  • Due to the error, the Connect job is not running and all data feeds are out of date.
  • From SS&E > Admin > Advanced Administration > External Logging > The Connect2 Application Log file shows an Apache Drill validation error.

oadd.org.apache.drill.common.exceptions.UserRemoteException:

VALIDATION ERROR: Schema [[dfs, root]] is not valid with respect to either root schema or current default schema.

Resolution

In the past, the following steps have resolved this error.

  1. Verify that the Admin password is set to "password never expires" both on the Connect server and the Informer server.
  2. Verify that dfs.root exists as a schema. This can be validated by running the command to "Show Schema" in Apache Drill and validating that the output includes the dfs.root schema or not.
      • apache drill (dfs)> SHOW SCHEMAS;
  3. Check the user assigned to the Connect job following the steps below.
  4. Confirm that Drill is querying from the right directory following the steps below.
  5. Check the Apache Drill Storage Plugin Configuration. If needed, reconfigure the plugin.
      • Storage plugins enable Drill to access data sources.
      • For more information, click here.

How to check the Connect Job User:

From the Windows Start menu on the Connect server, search for the "Task Scheduler" Application.

  1. Highlight the Aviso Connect/Connect2 job.
  2. Check the General tab to view the user that is "running" the task scheduler Aviso Connect job.
  3. If you need to change the user on the scheduled task, right-click on the Connect job and select "Properties". Then, from the General tab, change the user if needed.
  4. We recommend setting the Connect task user account to not expire or changing it to a service account on the Connect server (local machine), and validating the task security options so that this does not change/reoccur.

How to check the Drill Directory:

  1. Make sure the Drill directory is pointing to the same place that the CSV files are being exported to.
      • Confirm that this is the right directory and that the directory path is formatted correctly.
      • If this is a network directory and not a local directory, a symbolic link may be needed.
  2. Access the Drill web ui by going to: http://localhost:8047/ from a web browser on the Connect server.
  3. Under Drill Storage > Enabled Storage Plugins, click the Update button next to dfs.
  4. In the Configuration XML, change the root location to the CSV directory.
      • The default is C:\Aviso\csv, but can be set to something else if CSVs are being exported to a different directory.
      • Define the path relative to the C:\ and use forward slashes ( / ) instead of backslashes.
      • For example C:\Aviso\CSV would be /Aviso/csv.
  1. "root": { "location": "/Aviso/csv", "writable": false, "defaultInputFormat": null, "allowAccessOutsideWorkspace": false }
Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
How to Contact Support
There are many ways to reach out! Click here for our support options.
Watermark Academy
Click to access the Watermark Academy for consultation, training, and implementation companion courses.