Configuring an organizational listing¶

Set the Uniform Listing Locator or listing name¶

The Uniform Listing Locator (ULL) is a unique identifier that represents the listing and its data product, treating them as one. The listing name is different from the title of the listing: Multiple listings can have the same title, but each listing must have a unique listing name or ULL. The complete ULL is formed by three elements delimited by the symbol ‘$’. The first element is the provider’s organization name, the second element is the provider profile INTERNAL, and the third element is the listing name. The ULL cannot be changed after the listing is published. Although it has three parts, the ULL is treated as a single name in queries. For example, you can query a table in a listing like this:

SELECT * FROM "ORGDATACLOUD$INTERNAL$MY_LISTING_NAME_123".PUBLIC.TABLE_FROM_LISTING;

When creating a listing, give it a clear, descriptive name. Consumers can find listings faster by name rather than title, and a descriptive name is easier to use in queries.

Set who can access an organizational listing¶

The target audience of your organizational listings is always your internal marketplace. Although you could create a private listing for your own account, it would not be available through your internal marketplace and it would not be an organizational listing.

Despite the restriction of staying internal, you can still control who can access the listing. You can share an organizational listings with specific accounts, with all accounts in all regions, with some accounts in a couple regions, with roles within an account, or with everyone in your organization.

In Snowsight, these settings are combined under the label Who can access. In SQL, you set the organization targets (accounts, roles) and location access regions in the listing manifest YAML.

organization_targets:
   access:
   - all_accounts : true

organization_targets:
access:
   - account: 'Account1'
   - account: 'Account2'

organization_targets:
   access:
      - account: 'Account1'
         roles: [<role1>, <role2>, <role3>]

In a similar way, regions are set up the access regions_attribute:

locations:
access_regions:
   - name: "ALL"

locations:
access_regions:
   - name: "AWS_US_WEST_2"
   - name: "AZURE_CENTRALINDIAUS-EAST"

Set auto-fulfillment options for an organizational listing¶

Organizational listings that have attached data shares and apps both use auto-fulfillment, however they each use different methods. For this reason, the refresh schedules for each are different. For shares, the refresh schedule is set on the database level. For apps, it’s set on the account level.

If you need to use auto-fulfillment, you can set it when your run CREATE ORGANIZATIONAL LISTING OR ALTER LISTING by changing the auto_fulfillment attribute in the listing manifest fields.

auto_fulfillment:
   refresh_type: SUB_DATABASE
   refresh_schedule: '10 MINUTE'