Gerenciando o preenchimento automático entre nuvens em Snowflake Data Clean Rooms¶

Account administrator actions¶

To enable Cross-Cloud Auto-Fulfillment for an account using the API, administrators in both the provider and consumer accounts must run the following SQL code using the ACCOUNTADMIN role. You need to run this only once per account.

USE ROLE ACCOUNTADMIN;
-- Optionally check first to see if LAF is enabled on the account.
CALL samooha_by_snowflake_local_db.library.is_laf_enabled_on_account();

-- If LAF is not enabled, enable it.
CALL samooha_by_snowflake_local_db.library.enable_laf_on_account();

Provider and consumer actions¶

Depois que o preenchimento automático entre nuvens for habilitado em uma conta, veja como habilitá-lo ao criar ou instalar uma sala limpa:

1. O provedor publica a sala limpa como de costume chamando provider.create_or_update_cleanroom_listing.

2. O consumidor instala a sala limpa chamando consumer.install_cleanroom. Se o consumidor estiver em uma região de nuvem diferente do provedor, haverá falha em consumer.install_cleanroom com uma mensagem informando que a replicação do preenchimento automático entre nuvens está sendo instalada.

3. O consumidor continua chamando consumer.install_cleanroom até que seja bem-sucedido. A instalação leva vários minutos.

   At this point, the consumer has basic clean room functionality. To support client custom template requests, provider-run analyses, and provider activation, follow this additional step:

4. The provider calls provider.mount_request_logs_for_all_consumers until the procedure reports success. This means that communication from the consumer to the provider is enabled.

Exemplo de código da configuração completa:

1. Provedor: o provedor cria, compartilha e publica uma clean room da maneira padrão.

   USE WAREHOUSE APP_WH;
   USE ROLE SAMOOHA_APP_ROLE;
   
   SET cleanroom_name = 'LAF example';
   SET consumer_locator = '<CONSUMER_LOCATOR>';
   SET consumer_account_name = '<CONSUMER_DATA_SHARING_ACCOUNT_ID>';
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.cleanroom_init($cleanroom_name);
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.set_default_release_directive(
     $cleanroom_name,
     'V1_0', '0');
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.add_consumers(
     $cleanroom_name,
     $consumer_locator,
     $consumer_account_name);
   
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.provider.create_or_update_cleanroom_listing($cleanroom_name);
   

   Copy

2. Consumidor: o consumidor instala a sala limpa.

   USE WAREHOUSE APP_WH;
   USE ROLE SAMOOHA_APP_ROLE;
   
   SET cleanroom_name = 'LAF example';
   SET provider_locator = '<PROVIDER_LOCATOR>';
   
   -- Initial call starts the process and returns a cross-cloud/region replication failure.
   -- Continue to call this procedure until it returns a success message.
   CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.consumer.install_cleanroom(
     $cleanroom_name,
     $provider_locator);
   
   -- Continue with standard clean room configuration and use.
   -- The consumer can run analyses, but client custom templates, provider run, and provider analysis
   -- aren't supported until the provider takes the action shown in the next step.
   ...
   

   Copy

3. Provider: After the consumer installs the clean room, the provider must mount the requests share to enable request-based actions between the provider and consumer. Request-based actions include provider requests to run an analysis and consumer requests to add a template to the clean room.

   -- Call mount_request_logs_for_all_consumers until it reports success.
   provider.mount_request_logs_for_all_consumers($cleanroom_name);
   

   Copy

   A funcionalidade completa do provedor/consumidor agora está disponível.