#[non_exhaustive]pub struct SnowflakeDestinationUpdate {Show 19 fields
pub account_url: Option<String>,
pub private_key: Option<String>,
pub key_passphrase: Option<String>,
pub user: Option<String>,
pub database: Option<String>,
pub schema: Option<String>,
pub table: Option<String>,
pub snowflake_role_configuration: Option<SnowflakeRoleConfiguration>,
pub data_loading_option: Option<SnowflakeDataLoadingOption>,
pub meta_data_column_name: Option<String>,
pub content_column_name: Option<String>,
pub cloud_watch_logging_options: Option<CloudWatchLoggingOptions>,
pub processing_configuration: Option<ProcessingConfiguration>,
pub role_arn: Option<String>,
pub retry_options: Option<SnowflakeRetryOptions>,
pub s3_backup_mode: Option<SnowflakeS3BackupMode>,
pub s3_update: Option<S3DestinationUpdate>,
pub secrets_manager_configuration: Option<SecretsManagerConfiguration>,
pub buffering_hints: Option<SnowflakeBufferingHints>,
}Expand description
Update to configuration settings
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.account_url: Option<String>URL for accessing your Snowflake account. This URL must include your account identifier. Note that the protocol (https://) and port number are optional.
private_key: Option<String>The private key used to encrypt your Snowflake client. For information, see Using Key Pair Authentication & Key Rotation.
key_passphrase: Option<String>Passphrase to decrypt the private key when the key is encrypted. For information, see Using Key Pair Authentication & Key Rotation.
user: Option<String>User login name for the Snowflake account.
database: Option<String>All data in Snowflake is maintained in databases.
schema: Option<String>Each database consists of one or more schemas, which are logical groupings of database objects, such as tables and views
table: Option<String>All data in Snowflake is stored in database tables, logically structured as collections of columns and rows.
snowflake_role_configuration: Option<SnowflakeRoleConfiguration>Optionally configure a Snowflake role. Otherwise the default user role will be used.
data_loading_option: Option<SnowflakeDataLoadingOption>JSON keys mapped to table column names or choose to split the JSON payload where content is mapped to a record content column and source metadata is mapped to a record metadata column.
meta_data_column_name: Option<String>The name of the record metadata column
content_column_name: Option<String>The name of the content metadata column
cloud_watch_logging_options: Option<CloudWatchLoggingOptions>Describes the Amazon CloudWatch logging options for your Firehose stream.
processing_configuration: Option<ProcessingConfiguration>Describes a data processing configuration.
role_arn: Option<String>The Amazon Resource Name (ARN) of the Snowflake role
retry_options: Option<SnowflakeRetryOptions>Specify how long Firehose retries sending data to the New Relic HTTP endpoint. After sending data, Firehose first waits for an acknowledgment from the HTTP endpoint. If an error occurs or the acknowledgment doesn’t arrive within the acknowledgment timeout period, Firehose starts the retry duration counter. It keeps retrying until the retry duration expires. After that, Firehose considers it a data delivery failure and backs up the data to your Amazon S3 bucket. Every time that Firehose sends data to the HTTP endpoint (either the initial attempt or a retry), it restarts the acknowledgement timeout counter and waits for an acknowledgement from the HTTP endpoint. Even if the retry duration expires, Firehose still waits for the acknowledgment until it receives it or the acknowledgement timeout period is reached. If the acknowledgment times out, Firehose determines whether there's time left in the retry counter. If there is time left, it retries again and repeats the logic until it receives an acknowledgment or determines that the retry time has expired. If you don't want Firehose to retry sending data, set this value to 0.
s3_backup_mode: Option<SnowflakeS3BackupMode>Choose an S3 backup mode. Once you set the mode as AllData, you can not change it to FailedDataOnly.
s3_update: Option<S3DestinationUpdate>Describes an update for a destination in Amazon S3.
secrets_manager_configuration: Option<SecretsManagerConfiguration>Describes the Secrets Manager configuration in Snowflake.
buffering_hints: Option<SnowflakeBufferingHints>Describes the buffering to perform before delivering data to the Snowflake destination.
Implementations§
Source§impl SnowflakeDestinationUpdate
impl SnowflakeDestinationUpdate
Sourcepub fn account_url(&self) -> Option<&str>
pub fn account_url(&self) -> Option<&str>
URL for accessing your Snowflake account. This URL must include your account identifier. Note that the protocol (https://) and port number are optional.
Sourcepub fn private_key(&self) -> Option<&str>
pub fn private_key(&self) -> Option<&str>
The private key used to encrypt your Snowflake client. For information, see Using Key Pair Authentication & Key Rotation.
Sourcepub fn key_passphrase(&self) -> Option<&str>
pub fn key_passphrase(&self) -> Option<&str>
Passphrase to decrypt the private key when the key is encrypted. For information, see Using Key Pair Authentication & Key Rotation.
Sourcepub fn schema(&self) -> Option<&str>
pub fn schema(&self) -> Option<&str>
Each database consists of one or more schemas, which are logical groupings of database objects, such as tables and views
Sourcepub fn table(&self) -> Option<&str>
pub fn table(&self) -> Option<&str>
All data in Snowflake is stored in database tables, logically structured as collections of columns and rows.
Sourcepub fn snowflake_role_configuration(
&self,
) -> Option<&SnowflakeRoleConfiguration>
pub fn snowflake_role_configuration( &self, ) -> Option<&SnowflakeRoleConfiguration>
Optionally configure a Snowflake role. Otherwise the default user role will be used.
Sourcepub fn data_loading_option(&self) -> Option<&SnowflakeDataLoadingOption>
pub fn data_loading_option(&self) -> Option<&SnowflakeDataLoadingOption>
JSON keys mapped to table column names or choose to split the JSON payload where content is mapped to a record content column and source metadata is mapped to a record metadata column.
Sourcepub fn meta_data_column_name(&self) -> Option<&str>
pub fn meta_data_column_name(&self) -> Option<&str>
The name of the record metadata column
Sourcepub fn content_column_name(&self) -> Option<&str>
pub fn content_column_name(&self) -> Option<&str>
The name of the content metadata column
Sourcepub fn cloud_watch_logging_options(&self) -> Option<&CloudWatchLoggingOptions>
pub fn cloud_watch_logging_options(&self) -> Option<&CloudWatchLoggingOptions>
Describes the Amazon CloudWatch logging options for your Firehose stream.
Sourcepub fn processing_configuration(&self) -> Option<&ProcessingConfiguration>
pub fn processing_configuration(&self) -> Option<&ProcessingConfiguration>
Describes a data processing configuration.
Sourcepub fn retry_options(&self) -> Option<&SnowflakeRetryOptions>
pub fn retry_options(&self) -> Option<&SnowflakeRetryOptions>
Specify how long Firehose retries sending data to the New Relic HTTP endpoint. After sending data, Firehose first waits for an acknowledgment from the HTTP endpoint. If an error occurs or the acknowledgment doesn’t arrive within the acknowledgment timeout period, Firehose starts the retry duration counter. It keeps retrying until the retry duration expires. After that, Firehose considers it a data delivery failure and backs up the data to your Amazon S3 bucket. Every time that Firehose sends data to the HTTP endpoint (either the initial attempt or a retry), it restarts the acknowledgement timeout counter and waits for an acknowledgement from the HTTP endpoint. Even if the retry duration expires, Firehose still waits for the acknowledgment until it receives it or the acknowledgement timeout period is reached. If the acknowledgment times out, Firehose determines whether there's time left in the retry counter. If there is time left, it retries again and repeats the logic until it receives an acknowledgment or determines that the retry time has expired. If you don't want Firehose to retry sending data, set this value to 0.
Sourcepub fn s3_backup_mode(&self) -> Option<&SnowflakeS3BackupMode>
pub fn s3_backup_mode(&self) -> Option<&SnowflakeS3BackupMode>
Choose an S3 backup mode. Once you set the mode as AllData, you can not change it to FailedDataOnly.
Sourcepub fn s3_update(&self) -> Option<&S3DestinationUpdate>
pub fn s3_update(&self) -> Option<&S3DestinationUpdate>
Describes an update for a destination in Amazon S3.
Sourcepub fn secrets_manager_configuration(
&self,
) -> Option<&SecretsManagerConfiguration>
pub fn secrets_manager_configuration( &self, ) -> Option<&SecretsManagerConfiguration>
Describes the Secrets Manager configuration in Snowflake.
Sourcepub fn buffering_hints(&self) -> Option<&SnowflakeBufferingHints>
pub fn buffering_hints(&self) -> Option<&SnowflakeBufferingHints>
Describes the buffering to perform before delivering data to the Snowflake destination.
Source§impl SnowflakeDestinationUpdate
impl SnowflakeDestinationUpdate
Sourcepub fn builder() -> SnowflakeDestinationUpdateBuilder
pub fn builder() -> SnowflakeDestinationUpdateBuilder
Creates a new builder-style object to manufacture SnowflakeDestinationUpdate.
Trait Implementations§
Source§impl Clone for SnowflakeDestinationUpdate
impl Clone for SnowflakeDestinationUpdate
Source§fn clone(&self) -> SnowflakeDestinationUpdate
fn clone(&self) -> SnowflakeDestinationUpdate
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Debug for SnowflakeDestinationUpdate
impl Debug for SnowflakeDestinationUpdate
impl StructuralPartialEq for SnowflakeDestinationUpdate
Auto Trait Implementations§
impl Freeze for SnowflakeDestinationUpdate
impl RefUnwindSafe for SnowflakeDestinationUpdate
impl Send for SnowflakeDestinationUpdate
impl Sync for SnowflakeDestinationUpdate
impl Unpin for SnowflakeDestinationUpdate
impl UnwindSafe for SnowflakeDestinationUpdate
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left is true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left(&self) returns true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);