Marketplace system table reference

Preview

This feature is in Public Preview.

This article provides an overview of how to use system tables to help operationalize your Databricks Marketplace selling process.

Marketplace system tables will all live in the system.marketplace schema. Currently, the schema hosts the listing_access_events table. This table retrieves the consumer info for completed request data or get data events on your listings.

Listing access events schema

This is the schema used in the listing_access_events system table:

Column name

Data type

Description

account_id

string

The account ID that hosts the listing.

metastore_id

string

The metatore ID that hosts the listing.

metastore_cloud

string

The cloud provider of the metastore that hosts the listing.

metastore_region

string

The region of the metastore that hosts the listing.

provider_id

string

The provider profile ID.

provider_name

string

The provider profile name.

listing_id

string

The listing ID.

listing_name

string

The listing name.

consumer_delta_sharing_recipient_name

string

The underlying Delta Sharing recipient name for the consumer. The value is null when the event_type is REQUEST_DATA.

consumer_delta_sharing_recipient_type

string

Whether the consumer is on a Databricks account or not. Values will be either OPEN or DATABRICKS.

consumer_cloud

string

The consumer’s cloud. Nullable if consumer_delta_sharing_recipient_type is OPEN.

consumer_region

string

The consumer’s region. Nullable if consumer_delta_sharing_recipient_type is OPEN.

consumer_metastore_id

string

The consumer’s metastore ID. Nullable if consumer_delta_sharing_recipient_type is OPEN.

consumer_email

string

The consumer’s email address. PII.

consumer_name

string

The consumer’s name. PII.

consumer_company

string

The consumer’s company.

consumer_intended_use

string

The consumer’s intended use of the listing.

consumer_comments

string

Any additional comment the consumer left.

event_type

string

The type of access. The value can be either REQUEST_DATA or GET_DATA.

event_date

date

The UTC date the event happened.

event_time

timestamp

The exact UTC timestamp when the event happened.

Known limitations

  • Listings created in a Google Cloud metastore are not logged in Marketplace system tables.

  • Activity from consumers using Databricks on Google Cloud is not logged in Marketplace system tables.

Example queries

This section includes the following sample queries you can use to gain insight into consumer activity on your listings.

Consumer requests from the last 10 days 

SELECT event_date, provider_name, listing_name, listing_id, consumer_delta_sharing_recipient_name, consumer_cloud, consumer_region, consumer_name, consumer_email, consumer_company
FROM system.marketplace.listing_access_events
WHERE event_type = 'REQUEST_DATA'
AND event_date >= date_add(current_date(), -10)

Top listings by number of requests 

SELECT listing_name, consumer_cloud, count(*) as requestCount
FROM system.marketplace.listing_access_events
GROUP BY listing_name, consumer_cloud
ORDER BY requestCount DESC

View top requesters 

SELECT consumer_name, consumer_email, count(*) as requestCount
FROM system.marketplace.listing_access_events
GROUP BY consumer_name, consumer_email
ORDER BY requestCount DESC

Notebook demo: Enable and analyze the marketplace listings system table

You can use the following notebook to enable and analyze the marketplace listings system table.

Marketplace listings system table demo notebook

Open notebook in new tab