Databricks SDK for JavaScript
    Preparing search index...
    interface ListingDetail {
        assets?: AssetType[];
        collectionDateEnd?: bigint;
        collectionDateStart?: bigint;
        collectionGranularity?: DataRefreshInfo;
        cost?: Cost;
        dataSource?: string;
        description?: string;
        documentationLink?: string;
        embeddedNotebookFileInfos?: FileInfo[];
        fileIds?: string[];
        geographicalCoverage?: string;
        license?: string;
        pricingModel?: string;
        privacyPolicyLink?: string;
        size?: number;
        supportLink?: string;
        tags?: ListingTag[];
        termsOfService?: string;
        updateFrequency?: DataRefreshInfo;
    }
    Index

    Properties

    assets?: AssetType[]

    Type of assets included in the listing. eg. GIT_REPO, DATA_TABLE, MODEL, NOTEBOOK

    collectionDateEnd?: bigint

    The ending date timestamp for when the data spans

    collectionDateStart?: bigint

    The starting date timestamp for when the data spans

    collectionGranularity?: DataRefreshInfo

    Smallest unit of time in the dataset

    cost?: Cost

    Whether the dataset is free or paid

    dataSource?: string

    Where/how the data is sourced

    description?: string
    documentationLink?: string
    embeddedNotebookFileInfos?: FileInfo[]
    fileIds?: string[]
    geographicalCoverage?: string

    Which geo region the listing data is collected from

    license?: string

    ID 20, 21 removed don't use License of the data asset - Required for listings with model based assets

    pricingModel?: string

    What the pricing model is (e.g. paid, subscription, paid upfront); should only be present if cost is paid

    privacyPolicyLink?: string
    size?: number

    size of the dataset in GB

    supportLink?: string
    tags?: ListingTag[]

    Listing tags - Simple key value pair to annotate listings. When should I use tags vs dedicated fields? Using tags avoids the need to add new columns in the database for new annotations. However, this should be used sparingly since tags are stored as key value pair. Use tags only:

    1. If the field is optional and won't need to have NOT NULL integrity check
    2. The value is fairly fixed, static and low cardinality (eg. enums).
    3. The value won't be used in filters or joins with other tables.
    termsOfService?: string
    updateFrequency?: DataRefreshInfo

    How often data is updated