[BUG]: Demo notebook "dqx_demo_tool" fails if you use table name in your run_config

[gergo-databricks]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

This line will only work if "run_config.input_location" is a path and will fail if it is a table name.
bronze_df = spark.read.format(run_config.input_format).load(run_config.input_location).limit(1000)

Expected Behavior

Documentation states:
" input_location: s3://iot-ingest/raw # <- Input location for profiling (UC table or cloud path)"
https://databrickslabs.github.io/dqx/docs/guide/#using-cli

Code comment in config.py:
"input_location: str | None = None # input data path or a table"

utils.py / read_input_data() read the input_location correctly, so just the demo that is not correct.

I would expect the demo not to fail if a table name is used in this config field.

Steps To Reproduce

Set input_location to a table full name and run the dqx_demo_tool.py demo notebook on a shared cluster with DBR 15.4.

Cloud

AWS

Operating System

macOS

Relevant log output

Error:
Path must be absolute: my_catalog.my_schema.my_table/_delta_log

JVM stacktrace:
java.lang.IllegalArgumentException
	at com.databricks.common.path.AbstractPath$.fromHadoopPath(AbstractPath.scala:114)
...

[mwojtyczka]

It was a bit intentional to use native spark api in the demo to show that you don't actually need any special functions to interact with dqx. But I agree it would make more sense to use read_input_data function in the tool demo.