#[non_exhaustive]pub struct SchemaInputAttribute {
pub field_name: String,
pub type: SchemaAttributeType,
pub group_name: Option<String>,
pub match_key: Option<String>,
pub sub_type: Option<String>,
pub hashed: Option<bool>,
}
Expand description
A configuration object for defining input data fields in Entity Resolution. The SchemaInputAttribute
specifies how individual fields in your input data should be processed and matched.
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.field_name: String
A string containing the field name.
type: SchemaAttributeType
The type of the attribute, selected from a list of values.
LiveRamp supports: NAME
| NAME_FIRST
| NAME_MIDDLE
| NAME_LAST
| ADDRESS
| ADDRESS_STREET1
| ADDRESS_STREET2
| ADDRESS_STREET3
| ADDRESS_CITY
| ADDRESS_STATE
| ADDRESS_COUNTRY
| ADDRESS_POSTALCODE
| PHONE
| PHONE_NUMBER
| EMAIL_ADDRESS
| UNIQUE_ID
| PROVIDER_ID
TransUnion supports: NAME
| NAME_FIRST
| NAME_LAST
| ADDRESS
| ADDRESS_CITY
| ADDRESS_STATE
| ADDRESS_COUNTRY
| ADDRESS_POSTALCODE
| PHONE_NUMBER
| EMAIL_ADDRESS
| UNIQUE_ID
| IPV4
| IPV6
| MAID
Unified ID 2.0 supports: PHONE_NUMBER
| EMAIL_ADDRESS
| UNIQUE_ID
Normalization is only supported for NAME
, ADDRESS
, PHONE
, and EMAIL_ADDRESS
.
If you want to normalize NAME_FIRST
, NAME_MIDDLE
, and NAME_LAST
, you must group them by assigning them to the NAME
groupName
.
If you want to normalize ADDRESS_STREET1
, ADDRESS_STREET2
, ADDRESS_STREET3
, ADDRESS_CITY
, ADDRESS_STATE
, ADDRESS_COUNTRY
, and ADDRESS_POSTALCODE
, you must group them by assigning them to the ADDRESS
groupName
.
If you want to normalize PHONE_NUMBER
and PHONE_COUNTRYCODE
, you must group them by assigning them to the PHONE
groupName
.
group_name: Option<String>
A string that instructs Entity Resolution to combine several columns into a unified column with the identical attribute type.
For example, when working with columns such as NAME_FIRST
, NAME_MIDDLE
, and NAME_LAST
, assigning them a common groupName
will prompt Entity Resolution to concatenate them into a single value.
match_key: Option<String>
A key that allows grouping of multiple input attributes into a unified matching group.
For example, consider a scenario where the source table contains various addresses, such as business_address
and shipping_address
. By assigning a matchKey
called address
to both attributes, Entity Resolution will match records across these fields to create a consolidated matching group.
If no matchKey
is specified for a column, it won't be utilized for matching purposes but will still be included in the output table.
sub_type: Option<String>
The subtype of the attribute, selected from a list of values.
hashed: Option<bool>
Indicates if the column values are hashed in the schema input.
If the value is set to TRUE
, the column values are hashed.
If the value is set to FALSE
, the column values are cleartext.
Implementations§
Source§impl SchemaInputAttribute
impl SchemaInputAttribute
Sourcepub fn field_name(&self) -> &str
pub fn field_name(&self) -> &str
A string containing the field name.
Sourcepub fn type(&self) -> &SchemaAttributeType
pub fn type(&self) -> &SchemaAttributeType
The type of the attribute, selected from a list of values.
LiveRamp supports: NAME
| NAME_FIRST
| NAME_MIDDLE
| NAME_LAST
| ADDRESS
| ADDRESS_STREET1
| ADDRESS_STREET2
| ADDRESS_STREET3
| ADDRESS_CITY
| ADDRESS_STATE
| ADDRESS_COUNTRY
| ADDRESS_POSTALCODE
| PHONE
| PHONE_NUMBER
| EMAIL_ADDRESS
| UNIQUE_ID
| PROVIDER_ID
TransUnion supports: NAME
| NAME_FIRST
| NAME_LAST
| ADDRESS
| ADDRESS_CITY
| ADDRESS_STATE
| ADDRESS_COUNTRY
| ADDRESS_POSTALCODE
| PHONE_NUMBER
| EMAIL_ADDRESS
| UNIQUE_ID
| IPV4
| IPV6
| MAID
Unified ID 2.0 supports: PHONE_NUMBER
| EMAIL_ADDRESS
| UNIQUE_ID
Normalization is only supported for NAME
, ADDRESS
, PHONE
, and EMAIL_ADDRESS
.
If you want to normalize NAME_FIRST
, NAME_MIDDLE
, and NAME_LAST
, you must group them by assigning them to the NAME
groupName
.
If you want to normalize ADDRESS_STREET1
, ADDRESS_STREET2
, ADDRESS_STREET3
, ADDRESS_CITY
, ADDRESS_STATE
, ADDRESS_COUNTRY
, and ADDRESS_POSTALCODE
, you must group them by assigning them to the ADDRESS
groupName
.
If you want to normalize PHONE_NUMBER
and PHONE_COUNTRYCODE
, you must group them by assigning them to the PHONE
groupName
.
Sourcepub fn group_name(&self) -> Option<&str>
pub fn group_name(&self) -> Option<&str>
A string that instructs Entity Resolution to combine several columns into a unified column with the identical attribute type.
For example, when working with columns such as NAME_FIRST
, NAME_MIDDLE
, and NAME_LAST
, assigning them a common groupName
will prompt Entity Resolution to concatenate them into a single value.
Sourcepub fn match_key(&self) -> Option<&str>
pub fn match_key(&self) -> Option<&str>
A key that allows grouping of multiple input attributes into a unified matching group.
For example, consider a scenario where the source table contains various addresses, such as business_address
and shipping_address
. By assigning a matchKey
called address
to both attributes, Entity Resolution will match records across these fields to create a consolidated matching group.
If no matchKey
is specified for a column, it won't be utilized for matching purposes but will still be included in the output table.
Source§impl SchemaInputAttribute
impl SchemaInputAttribute
Sourcepub fn builder() -> SchemaInputAttributeBuilder
pub fn builder() -> SchemaInputAttributeBuilder
Creates a new builder-style object to manufacture SchemaInputAttribute
.
Trait Implementations§
Source§impl Clone for SchemaInputAttribute
impl Clone for SchemaInputAttribute
Source§fn clone(&self) -> SchemaInputAttribute
fn clone(&self) -> SchemaInputAttribute
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for SchemaInputAttribute
impl Debug for SchemaInputAttribute
Source§impl PartialEq for SchemaInputAttribute
impl PartialEq for SchemaInputAttribute
impl StructuralPartialEq for SchemaInputAttribute
Auto Trait Implementations§
impl Freeze for SchemaInputAttribute
impl RefUnwindSafe for SchemaInputAttribute
impl Send for SchemaInputAttribute
impl Sync for SchemaInputAttribute
impl Unpin for SchemaInputAttribute
impl UnwindSafe for SchemaInputAttribute
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);